Re: [PATCH v3 0/2] Memory-to-memory media controller topology

2018-06-29 Thread Hans Verkuil
On 06/29/18 09:06, Hans Verkuil wrote: > On 06/28/2018 09:29 PM, Ezequiel Garcia wrote: >> Compliance test for device /dev/video2: >> >> Driver Info: >> Driver name : vim2m >> Card type: vim2m >> Bus info : platform:vim2m >> Driver version : 4.18.0 >>

Re: [PATCH v3 0/2] Memory-to-memory media controller topology

2018-06-29 Thread Hans Verkuil
On 06/28/2018 09:29 PM, Ezequiel Garcia wrote: > Hi Hans, > > On Thu, 2018-06-28 at 11:19 +0200, Hans Verkuil wrote: >> On 06/27/18 22:35, Ezequiel Garcia wrote: >>> As discussed on IRC, memory-to-memory need to be modeled >>> properly in order to be supported by the media controller >>> framework

Re: [PATCH v3 0/2] Memory-to-memory media controller topology

2018-06-28 Thread Ezequiel Garcia
Hi Hans, On Thu, 2018-06-28 at 11:19 +0200, Hans Verkuil wrote: > On 06/27/18 22:35, Ezequiel Garcia wrote: > > As discussed on IRC, memory-to-memory need to be modeled > > properly in order to be supported by the media controller > > framework, and thus to support the Request API. > > > > First

Re: [PATCH v3 0/2] Memory-to-memory media controller topology

2018-06-28 Thread Hans Verkuil
On 06/27/18 22:35, Ezequiel Garcia wrote: > As discussed on IRC, memory-to-memory need to be modeled > properly in order to be supported by the media controller > framework, and thus to support the Request API. > > First commit introduces a register/unregister API, > that creates/destroys all the

[PATCH v3 0/2] Memory-to-memory media controller topology

2018-06-27 Thread Ezequiel Garcia
As discussed on IRC, memory-to-memory need to be modeled properly in order to be supported by the media controller framework, and thus to support the Request API. First commit introduces a register/unregister API, that creates/destroys all the entities and pads needed, and links them. The second