Hi everybody,
On a imx6qp custom board with a ov564x-style camera capture application, on csi0 port, 8 bits:
With linux 4.1.15, no trouble, capture works fine.
With linux 5.4.47, no mean to start the capture. Trace as below:
WARNING in file stream/source/stream.c at line 257: 'FD CAPTURE V4L2: VIDIOC_DQBUF FAILED'[ 31.860269] In MVC:mxc_v4l_ioctl
[ 31.863591] In MVC: mxc_v4l_do_ioctl c0445611
[ 31.868005] case VIDIOC_DQBUF
[ 31.871245] --------------------------------------------------------ue
[ 31.871247] In MVC:mxc_v4l_dqueue
[ 39.524186] VGEN2: disabling
[ 39.527755] VGEN3: disabling
[ 42.084136] ERROR: v4l2 capture: mxc_v4l_dqueue timeout enc_counter 0
WARNING in file stream/source/stream.c at line 257: 'FD CAPTURE V4L2: VIDIOC_DQBUF FAILED'
[ 42.099377] In MVC:mxc_v4l_ioctl
[ 42.102838] In MVC: mxc_v4l_do_ioctl c0445611
[ 42.107239] case VIDIOC_DQBUF
......
Between both versions, camera driver, dts and user software are the same. Moreover, camera driver directly pokes value into imx registers (CSI_SENS_CONF, CSI_SENS_FRM_SIZE, CSI_FRM_SIZE, CSI_CONF). Normally, it is enough to capure with csi port. As linux version is only the difference, i guess it is related with. But where ? What variation can induce capture port failure ?
Brgds,
Christophe
Is it possible that parallel csi capture be broken in 5.4 with IMX6QP. Both 5.4.47 and 5.4.70 have same behaviour. I can see v4l2 core is very different with 4.1.15 version.
I thought my csi troubles were maybe due to a bad pad muxing of pixclk for instance, but even with inner csi test generator the results are the same. I can see in this attempt that capture starts with a few callback "csi_enc_callback" and then stops after the first QBUF. Comparing with the same example on 4.1.15, callbacks goe on...
Hi Joanxie,
And so, do you have ideas about that ?
did you use nxp pre-built images? could you share the 5.4.47 dts file with me? and after board boot up, what do you get when you use the command "v4l2-ctl --list-device"?
I have tested 5.4.47 on my imx6qp board with PARALLEL camera(ov5640) successfully, I used mxc_v4l2_overlay.out to test, my command is "./mxc_v4l2_overlay.out -iw 1280 -ih 720 -it 0 -il 0 -ow 1280 -oh 720 -ot 40 -ol 40 -r 0 -t 50 -d 1 -fg -fr 30" maybe you can refer to this
it seems that you use the third party company board and SW, I don't know what capture test you operate, if your software has unit test, I suggest that you can use unit test to test