fix(linux): Split CSI2RX documentation into platform-specific files#645
fix(linux): Split CSI2RX documentation into platform-specific files#645Rishikesh-D wants to merge 1 commit intoTexasInstruments:masterfrom
Conversation
Rishikesh-D
requested review from
StaticRocket,
VeeruPrudhvi,
cshilwant,
gehariprasath,
jeevantelukula,
praneethbajjuri and
uditkumarti
as code owners
github-actions
Bot
assigned
devarsht,
gehariprasath,
praneethbajjuri,
r-vignesh and
uditkumarti
|
New issues found with check_toc_txt.py: |
|
You split everything up into nice logical sections, why would you want to merge it all back to a single page for the reader anyway? |
Rishikesh-D
force-pushed
the
csi_per_platform
branch
from
21e3823 to
5fe2b10
Compare
|
Refactored further to parse per platform file. Now each platform has its own .rst file and the |
|
@Yemike-Abhilash-Chandra , please review w.r.t Jacinto platforms and let me know if any changes are required. |
uditkumarti
left a comment
uditkumarti
left a comment
There was a problem hiding this comment.
1/ Instead latest SDK, use exact SDK version through out series
2/ j742s2 can be merged into j784s4.rst
| ====================== | ||
|
|
||
| The following combinations of sensors are tested in the latest sdk. | ||
|
|
There was a problem hiding this comment.
use SDK version instead of latest
There was a problem hiding this comment.
@uditkumarti , This is present in all the CSI_*.rst files.
Different platforms have different latest SDK releases. For example, the "latest" public release for AM62A is 11.01, and for AM62P it’s 12.00. I’m unsure whether to use the "latest" public SDK version available for each specific platform, or to use 12.00 across all the platforms.
There was a problem hiding this comment.
Sorry latest has no meaning
There was a problem hiding this comment.
Hi @uditkumarti , thank you for the review, I discussed with @jeevantelukula and @cshilwant , currently we don't have a variable / placeholder which will get populated with the release version in the final .html file.
So, I have mentioned the release version in the respective per platform CSI rst files directly, Please let me know if you have a different approach you'd prefer.
Thanks
Refactor the CSI documentation to have a per platform file. This improves the maintainability and organization by separating platform-specific content from common documentation The monolithic CSI2RX.rst file has been split into: - CSI2RX_common.rst: Shared introduction, architecture, driver details, and usage instructions - CSI2RX_AM62X.rst: AM62X-specific testing details and sensor information - CSI2RX_AM62PX.rst: AM62PX-specific content including V3Link support and mosaic pipelines - CSI2RX_AM62AX.rst: AM62AX-specific FPDLink camera support and ISP pipelines - CSI2RX_J721E.rst: J721E platform-specific details - CSI2RX_J721S2.rst: J721S2 platform-specific details - CSI2RX_J722S.rst: J722S platform-specific details - CSI2RX_J784S4.rst: J784S4 platform-specific details Signed-off-by: Rishikesh Donadkar <r-donadkar@ti.com>
Rishikesh-D
force-pushed
the
csi_per_platform
branch
from
5fe2b10 to
f7f7b8f
Compare
7 participants
Refactor the CSI documentation to have a per platform file. This improves the maintainability and organization by separating platform-specific content from common documentation
The monolithic CSI2RX.rst file has been split into:
Testing: A diff comparison of these files before and after refactoring showed no differences.