Hi Sebastian, On 20/01/2021 19:30, Sebastian Fricke wrote: > Hello Hans, > > On 20.01.2021 11:16, Hans Verkuil wrote: >> On 19/01/2021 20:16, Sebastian Fricke wrote: >> >> <snip> >> >>> I gathered all the information you require within this paste-bin: >>> https://paste.debian.net/1181807/ >> >> Hmm, the problem is that v4l2-compliance can't find the media controller >> that the subdev is part of. >> >> What is the output of: >> >> ls -l /sys/class/video4linux/v4l-subdev3 >> >> There should be a 'device' link listed. >> >> Please also show the output of: >> >> ls -l /sys/class/video4linux/v4l-subdev3/device/ >> >> If I compare this with the vimc test driver (using v4l-subdev0) there is a >> media0 directory in /sys/class/video4linux/v4l-subdev0/device/ which is >> the media controller that the subdev is associated with. > > There is no `media0` folder for the ov13850 subdevice :/ I have captured > the output for all of the subdevices as comparision. > > https://paste.debian.net/1181951/ I figured out why this no longer works and I proposed a better mechanism: https://patchwork.linuxtv.org/project/linux-media/cover/20210201093659.2945449-1-hverkuil-cisco@xxxxxxxxx/ Regards, Hans
