[Adding Nicolas] On Mon, Apr 6, 2020 at 3:50 PM Steve Longerbeam <slongerbeam@xxxxxxxxx> wrote: > > Ok, so now I connected the ov5640 module as per your suggestion and > > this is what I get with a clean 5.6.2: > > > > [ 6.618296] imx-media: ov5640 1-003c:0 -> imx6-mipi-csi2:0 > > [ 6.644522] imx-media: Registered ipu_ic_pp csc/scaler as /dev/video8 > > This shows that imx-media completed probe (v4l2 core called its probe > complete callback). Yes, correct: /dev/video8 is the mem2mem device. > > However, the v4l2video8convert Gstreamer element is not detected: > > > > # gst-inspect-1.0 | grep convert > > video4linux2: v4l2convert: V4L2 Video Converter > > audioconvert: audioconvert: Audio converter > > > > If I do the kernel hack I mentioned previously then I can get v4l2video8convert: > > > > --- a/drivers/media/v4l2-core/v4l2-async.c > > +++ b/drivers/media/v4l2-core/v4l2-async.c > > @@ -213,10 +213,6 @@ v4l2_async_notifier_try_complete(struct > > v4l2_async_notifier *notifier) > > if (!notifier->v4l2_dev) > > return 0; > > > > - /* Is everything ready? */ > > - if (!v4l2_async_notifier_can_complete(notifier)) > > - return 0; > > - > > return v4l2_async_notifier_call_complete(notifier); > > That's very odd, because v4l2_async_notifier_call_complete() was > definitely called on the imx-media root notifier from above. Yes, I agree. > Is there is another v4l2 driver that is not completing? Yes, there are some that do not complete, but the mem2mem is getting probed. Maybe a Gstreamer issue? Nicolas, I am using Gstreamer 1.16.2 on i.MX6 and cannot get the v4l2video8convert to show up. The mem2mem appears at /dev/video8 and it corresponds to i.MX6 ipu_ic_pp csc/scaler. Any suggestions? Thanks
