On Tue, Feb 14, 2023 at 11:25:20AM +0100, Frieder Schrempf wrote: > Hi Sakari, > > On 09.02.23 23:16, Sakari Ailus wrote: > > Just add some debug prints for V4L2 async sub-device matching process. These > > might come useful in figuring out why things don't work as expected. > > > > Signed-off-by: Sakari Ailus <sakari.ailus@xxxxxxxxxxxxxxx> > > --- > > Frieder, > > > > Can you try this? It prints what is being matched with what. Perhaps this > > could be merged in a bit more refined form if it proves useful. > > > > Not tested in any way. > > > > Thanks for the patch! > > I fixed a few issues (see below) and gave this patch a try. Though in my > case it doesn't seem to help much as the problem is somewhere before the > matching actually happens. The only output from this patch I get is: > > [ 1.536479] imx219 1-0010: trying to complete > [ 1.540856] imx219 1-0010: V4L2 device not available Yeah, the problem, as I understand, is a driver bug combined with a DTS bug... oh well. So not a V4L2 async problem at all. :-) -- Sakari Ailus
