How can the mipi lane rate of Orin NX support 2.4Gbps

[norman_xu]

Hello,

We are developing GMSL camera driver on Orin NX， and encountered the following problems，please help to troubleshoot.

1. If two 8M cameras are connected to the same mipi csi (4 lanes), the deserializer is configured with mipi lane rate of 2.0 Gbps, and the camera can output images normally.
2. If two 8M cameras and one 2M camera are connected to the same mipi csi (4 lanes), the deserializer is configured with mipi lane rate of 2.4 Gbps, and the camera cannot output images.

Execute the following command to increase the rate

    echo 1 > /sys/kernel/debug/bpmp/debug/clk/vi/mrq_rate_locked
    echo 1 > /sys/kernel/debug/bpmp/debug/clk/isp/mrq_rate_locked
    echo 1 > /sys/kernel/debug/bpmp/debug/clk/nvcsi/mrq_rate_locked
    echo 1 > /sys/kernel/debug/bpmp/debug/clk/emc/mrq_rate_locked
    cat /sys/kernel/debug/bpmp/debug/clk/vi/max_rate |tee /sys/kernel/debug/bpmp/debug/clk/vi/rate
    cat /sys/kernel/debug/bpmp/debug/clk/isp/max_rate | tee  /sys/kernel/debug/bpmp/debug/clk/isp/rate
    cat /sys/kernel/debug/bpmp/debug/clk/nvcsi/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/nvcsi/rate
    cat /sys/kernel/debug/bpmp/debug/clk/emc/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/emc/rate

The trace log error is as follows：

     kworker/0:2-96      [000] ....  1208.560859: rtcpu_nvcsi_intr: tstamp:38329997936 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x10000000
     kworker/0:2-96      [000] ....  1208.560859: rtcpu_nvcsi_intr: tstamp:38329997936 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000044
     kworker/0:2-96      [000] ....  1208.560859: rtcpu_nvcsi_intr: tstamp:38329998428 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x10000000
     kworker/0:2-96      [000] ....  1208.560860: rtcpu_nvcsi_intr: tstamp:38329998762 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x10000000
     kworker/0:2-96      [000] ....  1208.560860: rtcpu_nvcsi_intr: tstamp:38329998762 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000040
     kworker/0:2-96      [000] ....  1208.560860: rtcpu_nvcsi_intr: tstamp:38329999255 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x10000000
     kworker/0:2-96      [000] ....  1208.560860: rtcpu_nvcsi_intr: tstamp:38329999588 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x10000000
     kworker/0:2-96      [000] ....  1208.560861: rtcpu_nvcsi_intr: tstamp:38329999588 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000040
     kworker/0:2-96      [000] ....  1208.560861: rtcpu_nvcsi_intr: tstamp:38330000080 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x10000000
     kworker/0:2-96      [000] ....  1208.560861: rtcpu_nvcsi_intr: tstamp:38330000414 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x10000000
     kworker/0:2-96      [000] ....  1208.560861: rtcpu_nvcsi_intr: tstamp:38330000414 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000040
     kworker/0:2-96      [000] ....  1208.560861: rtcpu_nvcsi_intr: tstamp:38330000910 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x10000000
     kworker/0:2-96      [000] ....  1208.560862: rtcpu_nvcsi_intr: tstamp:38330001244 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x10000000
     kworker/0:2-96      [000] ....  1208.560862: rtcpu_nvcsi_intr: tstamp:38330001244 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000044
     kworker/0:2-96      [000] ....  1208.560862: rtcpu_nvcsi_intr: tstamp:38330001738 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x10000000
     kworker/0:2-96      [000] ....  1208.560862: rtcpu_nvcsi_intr: tstamp:38330002074 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x10000000
     kworker/0:2-96      [000] ....  1208.560862: rtcpu_nvcsi_intr: tstamp:38330002074 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000040
     kworker/0:2-96      [000] ....  1208.560862: rtcpu_nvcsi_intr: tstamp:38330002564 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x10000000
     kworker/0:2-96      [000] ....  1208.560863: rtcpu_nvcsi_intr: tstamp:38330002897 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x10000000
     kworker/0:2-96      [000] ....  1208.560863: rtcpu_nvcsi_intr: tstamp:38330002897 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000044

[carolyuu]

Hi,

For the camera basic functionality first needs to check the device and driver configuration.
You can reference to below program guide for the detailed information of device tree and driver implementation.
https://docs.nvidia.com/jetson/archives/r36.3/DeveloperGuide/SD/CameraDevelopment/SensorSoftwareDriverProgramming.html?highlight=programing#sensor-software-driver-programming

Please refer to Applications Using V4L2 IOCTL Directly by using V4L2 IOCTL to verify basic camera functionality.
https://docs.nvidia.com/jetson/archives/r36.3/DeveloperGuide/SD/CameraDevelopment/SensorSoftwareDriverProgramming.html?highlight=programing#to-run-a-v4l2-ctl-test

Once confirm the configure and still failed below link help to get log and some information and some tips for debug.
https://elinux.org/Jetson/l4t/Camera_BringUp#Steps_to_enable_more_debug_messages

Thanks!

[ShaneCCC]

It’s could be the MIPI timing issue. Please confirm the timing.

@norman_xu

PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000044

[norman_xu]

Hi ShaneCCC,
You are right, it’s a hardware issue, thanks.