Skip to content

Csi 11.0 docs #231

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 3, 2025
Merged

Csi 11.0 docs #231

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
73ffcf8
fix: Kernel: CSI: Remove docs for hacky PM
Rishikesh-D Apr 1, 2025
caab06f
feat(linux): CSI: Add docs for 4x OV5640 mosaic on AM62P
Rishikesh-D Apr 1, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
91 changes: 25 additions & 66 deletions source/linux/Foundational_Components/Kernel/Kernel_Drivers/Camera/CSI2RX.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -379,6 +379,29 @@ Enabling camera sensors

$ gst-launch-1.0 libcamerasrc ! video/x-raw, width=1024, height=768, format=UYVY ! autovideosink

.. ifconfig:: CONFIG_part_variant in ('AM62PX')

You can also run mosaic camera to display stream from 4 OV5640 connected to the SK-AM62P using V3Link fusion mini board.

.. note::

Arm neon accelerated TI elements for video mosaicing and color format conversion namely ``timosaic`` and ``ticolorconvert`` are not present in AM62P SDK 11.00.
To run the below pipeline, AM62P SDK 10.01 should be used with the SDK 11.00 kernel installed from `here <https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?h=ti-linux-6.12.y>`__.

.. code-block:: console

$ gst-launch-1.0 \
v4l2src device=/dev/video-ov5640-cam0 ! video/x-raw, width=640,height=480, format=YUY2 ! ticolorconvert ! queue ! mosaic.sink_0 \
v4l2src device=/dev/video-ov5640-cam1 ! video/x-raw, width=640,height=480, format=YUY2 ! ticolorconvert ! queue ! mosaic.sink_1 \
v4l2src device=/dev/video-ov5640-cam2 ! video/x-raw, width=640,height=480, format=YUY2 ! ticolorconvert ! queue ! mosaic.sink_2 \
v4l2src device=/dev/video-ov5640-cam3 ! video/x-raw, width=640,height=480, format=YUY2 ! ticolorconvert ! queue ! mosaic.sink_3 \
timosaic name=mosaic \
sink_0::startx=300 sink_0::starty=0 sink_0::width=640 sink_0::height=480 \
sink_1::startx=980 sink_1::starty=0 sink_1::width=640 sink_1::height=480 \
sink_2::startx=300 sink_2::starty=500 sink_2::width=640 sink_2::height=480 \
sink_3::startx=980 sink_3::starty=500 sink_3::width=640 sink_3::height=480 ! \
video/x-raw, width=1920, height=1080, format=NV12 ! queue ! kmssink driver-name=tidss sync=false force-modesetting=true

Suspend to RAM
==============

Expand All @@ -398,72 +421,8 @@ Enabling camera sensors

.. attention::

Only TEVI OV5640 module is known to work reliably when system is
suspended with capture running. And that too, with the below patch
applied to prevent races between different camera pipeline devices on
system resume. This is due to V4L2 framework's async notifier
limitations, which currently does not support sending notifications
between subdevice drivers on wakeup from suspend state.


The Technexion TEVI-OV5640 module supports this, but it may fail to set the
sensor registers in time when built as a module. You can fix this by making
it a part of the kernel image:

.. code-block:: diff

diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index bb3cd088db44..2262f23cd9ab 100644
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@ -805,7 +805,7 @@ CONFIG_RC_DEVICES=y
CONFIG_IR_GPIO_CIR=m
CONFIG_IR_MESON=m
CONFIG_IR_SUNXI=m
-CONFIG_MEDIA_SUPPORT=m
+CONFIG_MEDIA_SUPPORT=y
CONFIG_MEDIA_CAMERA_SUPPORT=y
CONFIG_MEDIA_ANALOG_TV_SUPPORT=y
CONFIG_MEDIA_DIGITAL_TV_SUPPORT=y
@@ -817,7 +817,7 @@ CONFIG_USB_VIDEO_CLASS=m
CONFIG_V4L_PLATFORM_DRIVERS=y
CONFIG_SDR_PLATFORM_DRIVERS=y
CONFIG_V4L_MEM2MEM_DRIVERS=y
-CONFIG_VIDEO_CADENCE_CSI2RX=m
+CONFIG_VIDEO_CADENCE_CSI2RX=y
CONFIG_VIDEO_WAVE_VPU=m
CONFIG_VIDEO_IMG_VXE_ENC=m
CONFIG_VIDEO_E5010_JPEG_ENC=m
@@ -842,13 +842,13 @@ CONFIG_VIDEO_SAMSUNG_EXYNOS_GSC=m
CONFIG_VIDEO_SAMSUNG_S5P_JPEG=m
CONFIG_VIDEO_SAMSUNG_S5P_MFC=m
CONFIG_VIDEO_SUN6I_CSI=m
-CONFIG_VIDEO_TI_J721E_CSI2RX=m
+CONFIG_VIDEO_TI_J721E_CSI2RX=y
CONFIG_VIDEO_HANTRO=m
CONFIG_VIDEO_IMX219=m
CONFIG_VIDEO_IMX390=m
CONFIG_VIDEO_IMX412=m
CONFIG_VIDEO_OV2312=m
-CONFIG_VIDEO_OV5640=m
+CONFIG_VIDEO_OV5640=y
CONFIG_VIDEO_OV5645=m
CONFIG_VIDEO_OX05B1S=m
CONFIG_VIDEO_DS90UB953=m
@@ -1459,8 +1459,8 @@ CONFIG_PHY_XGENE=y
CONFIG_PHY_CAN_TRANSCEIVER=m
CONFIG_PHY_SUN4I_USB=y
CONFIG_PHY_CADENCE_TORRENT=y
-CONFIG_PHY_CADENCE_DPHY=m
-CONFIG_PHY_CADENCE_DPHY_RX=m
+CONFIG_PHY_CADENCE_DPHY=y
+CONFIG_PHY_CADENCE_DPHY_RX=y
CONFIG_PHY_CADENCE_SIERRA=y
CONFIG_PHY_MIXEL_MIPI_DPHY=m
CONFIG_PHY_FSL_IMX8M_PCIE=y

To re-build the kernel with above changes you can refer to the
:ref:`Users Guide <users-guide-kernel-config>`.
Only TEVI OV5640 and IMX219 are known to work reliably when system is suspended with capture running.


.. ifconfig:: CONFIG_part_variant in ('AM62X')

Expand Down