vi got error when capturing YUV CSI video

dear,

Our hardware connection:

  TP2850->720p 2lane YUV CSI -> CSI A -> Port 0 

Measure signal:

  signal all  ok

capture cmd:

v4l2-ctl -d /dev/video0 --set-fmt-video=width=1280,height=720,pixelformat=UYVY --stream-mmap --stream-count=10 --set-ctrl bypass_mode=0 --stream-to=/tmp/stream.yuv &
^C
root@cidi-desktop:/home/cidi# cat /sys/kernel/debug/tracing/trace
# tracer: nop
#
# entries-in-buffer/entries-written: 30131/30131   #P:4
#
#                              _-----=> irqs-off
#                             / _----=> need-resched
#                            | / _---=> hardirq/softirq
#                            || / _--=> preempt-depth
#                            ||| /     delay
#           TASK-PID   CPU#  ||||    TIMESTAMP  FUNCTION
#              | |       |   ||||       |         |
     kworker/0:5-5960  [000] ....    45.039108: rtcpu_nvcsi_intr: tstamp:1602914389 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x0e000042
     kworker/0:5-5960  [000] ....    45.039116: rtcpu_nvcsi_intr: tstamp:1602914389 class:CORRECTABLE_ERR type:PHY_INTR phy:0 cil:0 st:0 vc:0 status:0x00000e42
     kworker/0:5-5960  [000] ....    45.039119: rtcpu_nvcsi_intr: tstamp:1602933838 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x00000042
     kworker/0:5-5960  [000] ....    45.039120: rtcpu_nvcsi_intr: tstamp:1602933838 class:CORRECTABLE_ERR type:PHY_INTR phy:0 cil:0 st:0 vc:0 status:0x00000042
     kworker/0:5-5960  [000] ....    45.039159: rtcpu_nvcsi_intr: tstamp:1602965783 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x10000044
     kworker/0:5-5960  [000] ....    45.039161: rtcpu_nvcsi_intr: tstamp:1602965783 class:CORRECTABLE_ERR type:PHY_INTR phy:0 cil:0 st:0 vc:0 status:0x00001044
     kworker/0:5-5960  [000] ....    45.039163: rtcpu_nvcsi_intr: tstamp:1602971343 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x00000044
     kworker/0:5-5960  [000] ....    45.039164: rtcpu_nvcsi_intr: tstamp:1602971343 class:CORRECTABLE_ERR type:PHY_INTR phy:0 cil:0 st:0 vc:0 status:0x00000044
     kworker/0:5-5960  [000] ....    45.039166: rtcpu_nvcsi_intr: tstamp:1602978283 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x00000044
     kworker/0:5-5960  [000] ....    45.039168: rtcpu_nvcsi_intr: tstamp:1602978283 class:CORRECTABLE_ERR type:PHY_INTR phy:0 cil:0 st:0 vc:0 status:0x00000044
     kworker/0:5-5960  [000] ....    45.039170: rtcpu_nvcsi_intr: tstamp:1602979669 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x00000042
     kworker/0:5-5960  [000] ....    45.039172: rtcpu_nvcsi_intr: tstamp:1602979669 class:CORRECTABLE_ERR type:PHY_INTR phy:0 cil:0 st:0 vc:0 status:0x00000042
     kworker/0:5-5960  [000] ....    45.039174: rtcpu_nvcsi_intr: tstamp:1603029695 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x10000044
     kworker/0:5-5960  [000] ....    45.039183: rtcpu_nvcsi_intr: tstamp:1603029695 class:CORRECTABLE_ERR type:PHY_INTR phy:0 cil:0 st:0 vc:0 status:0x00001044
     kworker/0:5-5960  [000] ....    45.039185: rtcpu_nvcsi_intr: tstamp:1603078270 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x0e000042
     kworker/0:5-5960  [000] ....    45.039187: rtcpu_nvcsi_intr: tstamp:1603078270 class:CORRECTABLE_ERR type:PHY_INTR phy:0 cil:0 st:0 vc:0 status:0x00000e42
     kworker/0:5-5960  [000] ....    45.039188: rtcpu_nvcsi_intr: tstamp:1603131059 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x00000044
     kworker/0:5-5960  [000] ....    45.039190: rtcpu_nvcsi_intr: tstamp:1603131059 class:CORRECTABLE_ERR type:PHY_INTR phy:0 cil:0 st:0 vc:0 status:0x00000044
     kworker/0:5-5960  [000] ....    45.039192: rtcpu_nvcsi_intr: tstamp:1603167164 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x00000042
     kworker/0:5-5960  [000] ....    45.039194: rtcpu_nvcsi_intr: tstamp:1603167164 class:CORRECTABLE_ERR type:PHY_INTR phy:0 cil:0 st:0 vc:0 status:0x00000042
     kworker/0:5-5960  [000] ....    45.039195: rtcpu_nvcsi_intr: tstamp:1603187995 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x00000042
     kworker/0:5-5960  [000] ....    45.039197: rtcpu_nvcsi_intr: tstamp:1603187995 class:CORRECTABLE_ERR type:PH

Any suggestions ?

Have refer to SerDes Pixel Clock session, and review your serdes_pix_clk_hz device tree settings.

https://docs.nvidia.com/jetson/archives/l4t-archived/l4t-322/index.html#page/Tegra%2520Linux%2520Driver%2520Package%2520Development%2520Guide%2Fcamera_sensor_prog.html%23wwpID0E0TZ0HA

dear ShaneCCC,

My CSI input does not have serializer/deserializer,

do also need to configure SerDes Pixel Clock??

You still can try to add if bandwidth cause the problem.

dear ShaneCCC,

How much should I set the SerDes Pixel Clock?

My pix_clk_hz =1650x750x30 *2 =74250000

Must it be greater than pix_clk_hz ??

You can try 2 or 3 times of 74250000 or even more bigger.

dear ShaneCCC,

     thanks,  i have a try