MIPI CSI2 TP2854 2lane x 2channel DUAL but does not work on Jetson Orin Nano

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin Nano
1

Hi

I did overlay dts file and driver in the nvidia-oot dir.
tp2854 addr is 0x44. and the other is 0x47.
csi0 to tp2854 0x44 mipi0
csi2 to tp2854 0x44 mipi1
csi3 to tp2854 0x47 mipi0
csi4 to tp2854 0x47 mipi1

I checked…
$ ll /dev/ | grep video
rw-rw----+ 1 root video 81, 0 6월 27 20:44 video0
crw-rw----+ 1 root video 81, 6 6월 27 20:44 video1
crw-rw----+ 1 root video 81, 8 6월 27 20:44 video2
crw-rw----+ 1 root video 81, 10 6월 27 20:44 video3

$ $ ll /sys/firmware/devicetree/base/bus@0/i2c@c240000
total 0
drwxr-xr-x 9 root root 0 6월 27 20:52 ./
drwxr-xr-x 122 root root 0 6월 27 20:52 ../
drwxr-xr-x 4 root root 0 6월 27 20:52 ‘nc_tp2854_a@44’/
drwxr-xr-x 4 root root 0 6월 27 20:52 ‘nc_tp2854_b@45’/
drwxr-xr-x 4 root root 0 6월 27 20:52 ‘nc_tp2854_c@46’/
drwxr-xr-x 4 root root 0 6월 27 20:52 ‘nc_tp2854_d@47’/

but…
Not work when I ran v4l2-ctl

$ v4l2-ctl -d /dev/video0 --verbose --set-fmt-video=width=1280,height=720 --stream-mmap --stream-count=10
VIDIOC_QUERYCAP: ok
VIDIOC_G_FMT: ok
VIDIOC_S_FMT: ok
Format Video Capture:
Width/Height : 1280/720
Pixel Format : ‘UYVY’ (UYVY 4:2:2)
Field : None
Bytes per Line : 2560
Size Image : 1843200
Colorspace : sRGB
Transfer Function : Default (maps to sRGB)
YCbCr/HSV Encoding: Default (maps to ITU-R 601)
Quantization : Default (maps to Limited Range)
Flags :
VIDIOC_REQBUFS returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_STREAMON returned 0 (Success)
cap dqbuf: 0 seq: 0 bytesused: 1843200 ts: 0.000000 (error, ts-monotonic, ts-src-eof)
cap dqbuf: 1 seq: 1 bytesused: 1843200 ts: 0.000000 (error, ts-monotonic, ts-src-eof)
cap dqbuf: 2 seq: 2 bytesused: 1843200 ts: 0.000000 (error, ts-monotonic, ts-src-eof)
cap dqbuf: 3 seq: 3 bytesused: 1843200 ts: 0.000000 (error, ts-monotonic, ts-src-eof)
[ 627.414267] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[ 627.414287] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[ 627.415452] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
tegra234-p3767-camera-p3768-tp2854-dual.txt (15.9 KB)

[ 629.942019] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[ 629.942039] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[ 629.943302] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel

I attached overlay dts file changed to txt file I made.
please, check it and give me some advices..

thank you

3

hello sw0128,

please note that, on Orin Nano, CSI0 D1 and CSI1 D0 P/N will always been swizzled for P/N.
please use device tree property, lane_polarity to configure a polarity swap on any lane.

besides..
it looks you’re using four 2-lane cameras on CSI-A, CSI-B, CSI-C, CSI-D.
however, the DT property, tegra_sinterface looks incorrect.
for instance,

					nc_tp2854_b@45 {						
						mode0 { // tp2854_MODE_1280X720
							tegra_sinterface = "serial_c";   <== it should be "serial_b;"
							...
						ports {
							port@0 {
								nc_tp2854_out1: endpoint {
									port-index = <1>;
									bus-width = <2>;

please double check your device tree and update them accordingly.

4

Thank you for your reply.

I show you our connection csi line to tp2854.
ACAM1 IN and ACAM2 IN are from tp2854 the first.
ACAM3 IN and ACAM4 IN are from tp2854 the other.

JetsonOrinNano_TP2854
JetsonOrinNano_TP2854461×651 39.4 KB

As you see, I skip csi1_xx.
and I didn’t connect csi lane to be swizzled.
Could you check it again? please…

5

hello sw0128,

please check Orin Nano Series Design Guide for [Chapter 10. MIPI CSI Video Input].
the data-lane polarity swap is on module side.

you’ll also need to revise the CSI/VI port bindings since you’ve skip CSI-1
for example, these two were incorrect.

			tegra-capture-vi  {
					vi_port1: port@1 {
						nc_tp2854_vi_in1: endpoint {
							port-index = <1>;

					channel@1 {
						nc_tp2854_csi_in1: endpoint {
							port-index = <1>;
6

Thank you for your great support.

I’ll do it and inform you of the result.

7

Hi.

I modify custom board and dts file.
I use the only CSI0. others are cut with tp2854 by removing resistor.
and I set lane_polarity = “2”;

As you see below picture in TP2854 part, I removed damping resistor except for CSI0.

the_only_CSI0
the_only_CSI0808×1150 123 KB

and I attach overlay dts file for the only CSI0 channel 1.
tegra234-p3767-camera-p3768-tp2854-dual.txt (5.0 KB)

also, I checked debug messages during run “v4l2-ctl -d /dev/video0 --verbose --set-fmt-video=width=1280,height=720 --stream-mmap --stream-count=10”

team3@team3-desktop:~$ v4l2-ctl -d /dev/video0 --verbose --set-fmt-video=width=1280,height=720 --stream-mmap --stream-count=10
VIDIOC_QUERYCAP: ok:
VIDIOC_G_FMT: ok
VIDIOC_S_FMT: ok
Format Video Capture:
Width/Height : 1280/720
Pixel Format : ‘UYVY’ (UYVY 4:2:2)
Field : None
Bytes per Line : 2560
Size Image : 1843200
Colorspace : sRGB
Transfer Function : Default (maps to sRGB)
YCbCr/HSV Encoding: Default (maps to ITU-R 601)
Quantization : Default (maps to Limited Range)
Flags :
VIDIOC_REQBUFS returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_STREAMON returned 0 (Success)
cap dqbuf: 0 seq: 0 bytesused: 1843200 ts: 0.000000 (error, ts-monotonic, ts-src-eof)
cap dqbuf: 0 seq: 0 bytesused: 1843200 ts: 0.000000 (error, ts-monotonic, ts-src-eof)
cap dqbuf: 1 seq: 1 bytesused: 1843200 ts: 0.000000 (error, ts-monotonic, ts-src-eof)
cap dqbuf: 2 seq: 2 bytesused: 1843200 ts: 0.000000 (error, ts-monotonic, ts-src-eof)
cap dqbuf: 3 seq: 3 bytesused: 1843200 ts: 0.000000 (error, ts-monotonic, ts-src-eof)
[ 1954.765068] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[ 1954.765099] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[ 1954.766369] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel

root@team3-desktop:/home/team3# cat /sys/kernel/debug/tracing/trace

tracer: nop

entries-in-buffer/entries-written: 1026/1026 #P:6

_-------=> irqs-off

/ _------=> need-resched

| / _-----=> need-resched-lazy

|| / _----=> hardirq/softirq

||| / _—=> preempt-depth

|||| / _–=> preempt-lazy-depth

||||| / _-=> migrate-disable

|||||| / delay

TASK-PID CPU# ||||||| TIMESTAMP FUNCTION

| | | ||||||| | |

 kworker/2:0-26      [002] .......   591.836270: rtcpu_string: tstamp:19704135142 id:0x04010000 str:"VM0 deactivating."
 kworker/2:2-313     [002] .......   621.211356: rtcpu_string: tstamp:20620427106 id:0x04010000 str:"VM0 activating."
 kworker/2:2-313     [002] .......   621.211363: rtcpu_vinotify_event: tstamp:20621136410 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:659859159136 data:0x799d580010000000
 kworker/2:2-313     [002] .......   621.211364: rtcpu_vinotify_event: tstamp:20621136674 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:659859231840 data:0x0000000031000001
 kworker/2:2-313     [002] .......   621.211364: rtcpu_vinotify_event: tstamp:20621136967 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:659859253504 data:0x0000000007020001
 kworker/2:2-313     [002] .......   621.211365: rtcpu_vinotify_event: tstamp:20621137219 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:659859321024 data:0x799d550010000000
 kworker/2:2-313     [002] .......   621.211365: rtcpu_vinotify_event: tstamp:20621137502 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:659859363776 data:0x0000000031000002
 kworker/2:2-313     [002] .......   621.211367: rtcpu_nvcsi_intr: tstamp:20621443152 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x10000000
 kworker/2:2-313     [002] .......   621.323357: rtcpu_nvcsi_intr: tstamp:20624053516 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x10000000
 kworker/2:2-313     [002] .......   621.379349: rtcpu_nvcsi_intr: tstamp:20627271049 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x10000000
 kworker/2:2-313     [002] .......   621.435354: rtcpu_nvcsi_intr: tstamp:20627895354 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x10000000
 kworker/2:2-313     [002] .......   621.491355: rtcpu_nvcsi_intr: tstamp:20629376410 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x10000000
 kworker/2:2-313     [002] .......   621.491357: rtcpu_nvcsi_intr: tstamp:20629410008 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x10000000
 kworker/2:2-313     [002] .......   621.491357: rtcpu_nvcsi_intr: tstamp:20629507438 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x10000000
8

hello sw0128,

it’s reported DPHY CIL lane align error.
please refer to TRM for NVCSI_PHY_0_CILA_INTR_0_STATUS_CILA_0 for more details.

9

Thank you for your reply.

I’ve been working with Jeton Orin Nano 8GB Product type.
I searched “NVCSI_PHY_0_CILA_INTR_0_STATUS_CILA_0” in file - Orin-TRM_DP10508002_v1.2p.pdf but I can’t.
but
I find it in file - Xavier_TRM_DP09253002_v1.4p.pdf
Is this same?

and I got inform from registers - “28 0x0 intr_dphy_cil_lane_align_err_a”
Should I check it in h/w?

10

hello sw0128,

yes, please check the sensor hardware side for the cil_lane_align issue.

11

Thank you for your very much reply.

The member of H/W parts checked a custom board. and He find the short power of AVDD in TP2854. After modification, checked trace.

tracer: nop

entries-in-buffer/entries-written: 82/82 #P:6

_-------=> irqs-off

/ _------=> need-resched

| / _-----=> need-resched-lazy

|| / _----=> hardirq/softirq

||| / _—=> preempt-depth

|||| / _–=> preempt-lazy-depth

||||| / _-=> migrate-disable

|||||| / delay

TASK-PID CPU# ||||||| TIMESTAMP FUNCTION

| | | ||||||| | |

 kworker/1:4-488     [001] .......   196.589778: rtcpu_vinotify_event: tstamp:7341162510 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:234908891968 data:0x799d580010000000
 kworker/1:4-488     [001] .......   196.589782: rtcpu_vinotify_event: tstamp:7341162768 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:234908934048 data:0x0000000031000001
 kworker/1:4-488     [001] .......   196.589783: rtcpu_vinotify_event: tstamp:7341163081 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:234908955712 data:0x0000000007020001
 kworker/1:4-488     [001] .......   196.589784: rtcpu_vinotify_event: tstamp:7341163331 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:234909159584 data:0x799d550010000000
 kworker/1:4-488     [001] .......   196.589784: rtcpu_vinotify_event: tstamp:7341163615 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:234909202304 data:0x0000000031000002
 kworker/1:4-488     [001] .......   199.173758: rtcpu_vinotify_event: tstamp:7420916475 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:237468747712 data:0x799d580010000000
 kworker/1:4-488     [001] .......   199.173763: rtcpu_vinotify_event: tstamp:7420916769 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:237468789824 data:0x0000000031000001
 kworker/1:4-488     [001] .......   199.173764: rtcpu_vinotify_event: tstamp:7420919871 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:237468811488 data:0x0000000007020001
 kworker/1:4-488     [001] .......   199.173765: rtcpu_vinotify_event: tstamp:7420920163 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:237469015360 data:0x799d550010000000
 kworker/1:4-488     [001] .......   199.173766: rtcpu_vinotify_event: tstamp:7420920413 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:237469058080 data:0x0000000031000002
 kworker/1:4-488     [001] .......   206.741667: rtcpu_string: tstamp:7656840617 id:0x04010000 str:"VM0 deactivating."
 kworker/1:4-488     [001] .......   210.681656: rtcpu_string: tstamp:7780036544 id:0x04010000 str:"VM0 activating."
 kworker/1:4-488     [001] .......   210.681664: rtcpu_vinotify_event: tstamp:7780772862 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:248967941856 data:0x799d580010000000
 kworker/1:4-488     [001] .......   210.681664: rtcpu_vinotify_event: tstamp:7780773126 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:248967998784 data:0x0000000031000001
 kworker/1:4-488     [001] .......   210.681665: rtcpu_vinotify_event: tstamp:7780773423 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:248968016960 data:0x799d550010000000
 kworker/1:4-488     [001] .......   210.681665: rtcpu_vinotify_event: tstamp:7780773675 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:248968037280 data:0x0000000007020001
 kworker/1:4-488     [001] .......   210.681666: rtcpu_vinotify_event: tstamp:7780773965 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:248968082720 data:0x0000000031000002
 kworker/1:4-488     [001] .......   213.257627: rtcpu_vinotify_event: tstamp:7861068576 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:251549014560 data:0x799d580010000000
 kworker/1:4-488     [001] .......   213.257631: rtcpu_vinotify_event: tstamp:7861068872 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:251549056608 data:0x0000000031000001
 kworker/1:4-488     [001] .......   213.257632: rtcpu_vinotify_event: tstamp:7861069127 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:251549078272 data:0x0000000007020001
 kworker/1:4-488     [001] .......   213.257633: rtcpu_vinotify_event: tstamp:7861069420 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:251549246784 data:0x799d550010000000
 kworker/1:4-488     [001] .......   213.257634: rtcpu_vinotify_event: tstamp:7861069673 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:251549289472 data:0x0000000031000002
 kworker/1:4-488     [001] .......   215.833607: rtcpu_vinotify_event: tstamp:7941364699 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:254108581152 data:0x799d580010000000
 kworker/1:4-488     [001] .......   215.833611: rtcpu_vinotify_event: tstamp:7941364960 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:254108623232 data:0x0000000031000001
 kworker/1:4-488     [001] .......   215.833612: rtcpu_vinotify_event: tstamp:7941365255 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:254108644896 data:0x0000000007020001
12

hello sw0128,

it looks there’s no validate frames has received by VI engine,
here must be one pair of CHANSEL_PXL_SOF/CHANSEL_PXL_EOF to indicate a frame has detected by VI engine.
afterwards, it’s ATOMP_FRAME_DONE to indicate it’s complete writing a frame to memory.
let me give you an example,

rtcpu_vinotify_event: tstamp:4058867917 cch:-1 vi:0 tag:CSIMUX_STREAM channel:0x00 frame:0 vi_tstamp:129874754944 data:0x0000000000000001
rtcpu_vinotify_event: tstamp:4059206674 cch:0 vi:0 tag:ATOMP_FS channel:0x00 frame:1 vi_tstamp:129891804896 data:0x0000000800000000
rtcpu_vinotify_event: tstamp:4059206818 cch:0 vi:0 tag:CHANSEL_PXL_SOF channel:0x23 frame:1 vi_tstamp:129891808928 data:0x0000000000000001
rtcpu_vinotify_event: tstamp:4059206976 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:1 vi_tstamp:129891815424 data:0x0000000008020001
rtcpu_vinotify_error: tstamp:4060164160 cch:0 vi:0 tag:CSIMUX_FRAME channel:0x00 frame:1 vi_tstamp:129925171392 data:0x00000000000000a0
rtcpu_vinotify_event: tstamp:4060166846 cch:0 vi:0 tag:CHANSEL_PXL_EOF channel:0x23 frame:1 vi_tstamp:129923836800 data:0x0000000004370002
rtcpu_vinotify_event: tstamp:4060167015 cch:0 vi:0 tag:ATOMP_FRAME_DONE channel:0x23 frame:1 vi_tstamp:129923837312 data:0x0000000000000000
13

Finally, I got it!!!
I set some parameter(pix_clk_hz, max_lane_speed, …) in overlay dts file again.
camera display works.

Thank you so much.

$ cat /sys/kernel/debug/tracing/trace
kworker/5:0-41 [005] … 83.921035: rtcpu_string: tstamp:3823522950 id:0x04010000 str:“VM0 deactivating.”
kworker/5:2-148 [005] … 137.004781: rtcpu_string: tstamp:5482531971 id:0x04010000 str:“VM0 activating.”
kworker/5:2-148 [005] … 137.004789: rtcpu_vinotify_event: tstamp:5483214395 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:175446463104 data:0x799d580010000000
kworker/5:2-148 [005] … 137.004790: rtcpu_vinotify_event: tstamp:5483214655 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:175446472832 data:0x0000000031000001
kworker/5:2-148 [005] … 137.004791: rtcpu_vinotify_event: tstamp:5483214948 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:175446477344 data:0x0000000007020001
kworker/5:2-148 [005] … 137.004791: rtcpu_vinotify_event: tstamp:5483215258 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:175446578080 data:0x799d550010000000
kworker/5:2-148 [005] … 137.004792: rtcpu_vinotify_event: tstamp:5483215542 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:175446588576 data:0x0000000031000002
kworker/5:2-148 [005] … 137.004793: rtcpu_vinotify_event: tstamp:5483215791 cch:0 vi:0 tag:FS channel:0x00 frame:15 vi_tstamp:175451382912 data:0x0000000f00000010
kworker/5:2-148 [005] … 137.004793: rtcpu_vinotify_event: tstamp:5483216087 cch:0 vi:0 tag:ATOMP_FS channel:0x00 frame:15 vi_tstamp:175451382976 data:0x0000000800000000
kworker/5:2-148 [005] … 137.004794: rtcpu_vinotify_event: tstamp:5483216336 cch:0 vi:0 tag:CHANSEL_PXL_SOF channel:0x23 frame:15 vi_tstamp:175451427424 data:0x0000000000000001
kworker/5:2-148 [005] … 137.004794: rtcpu_vinotify_event: tstamp:5483216625 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:15 vi_tstamp:175451437184 data:0x0000000008020001
kworker/5:2-148 [005] … 137.060765: rtcpu_vinotify_event: tstamp:5483866554 cch:0 vi:0 tag:CHANSEL_PXL_EOF channel:0x23 frame:15 vi_tstamp:175483399328 data:0x0000000002cf0002
kworker/5:2-148 [005] … 137.060766: rtcpu_vinotify_event: tstamp:5483866841 cch:0 vi:0 tag:FE channel:0x00 frame:15 vi_tstamp:175483400128 data:0x0000000f00000020
kworker/5:2-148 [005] … 137.060767: rtcpu_vinotify_event: tstamp:5483867103 cch:0 vi:0 tag:ATOMP_FE channel:0x00 frame:15 vi_tstamp:175483400224 data:0x0000000800000000
kworker/5:2-148 [005] … 137.060768: rtcpu_vinotify_event: tstamp:5483867391 cch:0 vi:0 tag:ATOMP_FRAME_DONE channel:0x23 frame:15 vi_tstamp:175483400544 data:0x0000000000000000
kworker/5:2-148 [005] … 137.060768: rtcpu_vinotify_event: tstamp:5483867640 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:15 vi_tstamp:175483452480 data:0x0000000002020001
kworker/5:2-148 [005] … 137.060769: rtcpu_vinotify_event: tstamp:5483867919 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:15 vi_tstamp:175483467968 data:0x000000000a020001
kworker/5:2-148 [005] … 137.060770: rtcpu_vinotify_event: tstamp:5483868169 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:15 vi_tstamp:175483472896 data:0x0000000000020001
kworker/5:2-148 [005] … 137.060770: rtcpu_vinotify_event: tstamp:5484353767 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:175483523872 data:0x0000000007020002
kworker/5:2-148 [005] … 137.060771: rtcpu_vinotify_event: tstamp:5484354021 cch:0 vi:0 tag:FS channel:0x00 frame:1 vi_tstamp:175484715456 data:0x0000000100000010
kworker/5:2-148 [005] … 137.060772: rtcpu_vinotify_event: tstamp:5484354322 cch:0 vi:0 tag:ATOMP_FS channel:0x00 frame:1 vi_tstamp:175484715520 data:0x0000000800000000

15

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.