On 06/29/18 09:06, Hans Verkuil wrote:
> On 06/28/2018 09:29 PM, Ezequiel Garcia wrote:
<snip>
>> Compliance test for device /dev/video2:
>>
>> Driver Info:
>> Driver name : vim2m
>> Card type : vim2m
>> Bus info : platform:vim2m
>> Driver version : 4.18.0
>> Capabilities : 0x84208000
>> Video Memory-to-Memory
>> Streaming
>> Extended Pix Format
>> Device Capabilities
>> Device Caps : 0x04208000
>> Video Memory-to-Memory
>> Streaming
>> Extended Pix Format
>> Media Driver Info:
>> Driver name : vim2m
>> Model : vim2m
>> Serial :
>> Bus info :
>> Media version : 4.18.0
>> Hardware revision: 0x00000000 (0)
>> Driver version : 4.18.0
>> Interface Info:
>> ID : 0x0300000c
>> Type : V4L Video
>> Entity Info:
>> ID : 0x00000001 (1)
>> Name : source
>> Function : V4L2 I/O
>> Pad 0x01000002 : Source
>> Link 0x02000008: to remote pad 0x1000005 of entity 'proc':
>> Data, Enabled, Immutable
>
> Hmm, this doesn't show the sink entity associated with this interface.
>
> It's a v4l2-compliance bug, but I need to think a bit more on how to
> fix this.
Some background: until now an interface was linked to one entity only.
But m2m devices now have two entities linked to the same interface.
So the v4l2-compliance code that outputs this text only sees one entity.
The code needs to be rewritten to be smarter about this.
Something for the (near) future.
Regards,
Hans
