Skip to content

fix(linux): Split CSI2RX documentation into platform-specific files#645

Open
Rishikesh-D wants to merge 1 commit intoTexasInstruments:masterfrom
Rishikesh-D:csi_per_platform
Open

fix(linux): Split CSI2RX documentation into platform-specific files#645
Rishikesh-D wants to merge 1 commit intoTexasInstruments:masterfrom
Rishikesh-D:csi_per_platform

Conversation

@Rishikesh-D
Copy link
Copy Markdown
Contributor

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

Testing: A diff comparison of these files before and after refactoring showed no differences.

./build/processor-sdk-linux-AM62AX/esd/docs/11_01_07_05/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/CSI2RX.html
./build/processor-sdk-linux-J742S2/esd/docs/11_02/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/CSI2RX.html
./build/processor-sdk-linux-J721S2/esd/docs/11_02/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/CSI2RX.html
./build/processor-sdk-linux-J784S4/esd/docs/11_02/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/CSI2RX.html
./build/processor-sdk-linux-AM62X/esd/docs/11_02_08_02/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/CSI2RX.html
./build/processor-sdk-linux-J722S/esd/docs/11_02/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/CSI2RX.html
./build/processor-sdk-linux-J721E/esd/docs/11_02/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/CSI2RX.html
./build/processor-sdk-linux-AM62PX/esd/docs/11_02_08_02/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/CSI2RX.html

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>
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 1, 2026

New issues found with check_toc_txt.py:

WARNING:root:File not in any toc: source/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/CSI2RX_AM62X.rst
WARNING:root:File not in any toc: source/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/CSI2RX_J722S.rst
WARNING:root:File not in any toc: source/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/CSI2RX_J721E.rst
WARNING:root:File not in any toc: source/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/CSI2RX_J721S2.rst
WARNING:root:File not in any toc: source/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/CSI2RX_AM62AX.rst
WARNING:root:File not in any toc: source/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/CSI2RX_J784S4.rst
WARNING:root:File not in any toc: source/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/CSI2RX_AM62PX.rst
WARNING:root:File not in any toc: source/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/CSI2RX_common.rst

Comment on lines 3 to +5
.. ifconfig:: CONFIG_part_variant in ('AM62X')

CSI2RX testing details
======================

Following sensors have been tested with the latest SDK.

.. csv-table:: Sensor
:header: "Sensor","Media Bus Format","Video Format","Resolution"

"IMX219 RPi Camera","MEDIA_BUS_FMT_SRGGB8_1X8","V4L2_PIX_FMT_SRGGB8","1920x1080"
"OV5640 MIPI CSI Camera","MEDIA_BUS_FMT_YUYV8_1X16","V4L2_PIX_FMT_YUYV","640x480"

.. include:: CSI2RX_AM62X.rst
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@StaticRocket , are you concerned about the section headings getting evaluated in the first processing pass and getting registered globally which will create conflicts in the ref engine?

Copy link
Copy Markdown
Contributor Author

@Rishikesh-D Rishikesh-D Apr 9, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see such thing happening, as a diff comparison of the output before and after this refactoring shows exact same results. Please let me know if I am missing something.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, the diff wouldn't change because it was incorrect to begin with. If you pay attention to the permalinks between different DEVFAMILY types you'll see the issue. You should have also explicitly seen the following warning hinting at this behavior:

source/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/CSI2RX_AM62PX.rst:1: WARNING: Duplicate explicit target name: "enabling-camera-sensors". [docutils]

@StaticRocket
Copy link
Copy Markdown
Member

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?

@StaticRocket
Copy link
Copy Markdown
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants