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 entities and pads needed, > and links them. > > The second commit uses this API to support the vim2m driver. > > The series applies cleanly on v4.18-rc1. > > Topology (media-ctl -p output) > ============================== > > media-ctl -p > Media controller API version 4.17.0 > > Media device information > ------------------------ > driver vim2m > model vim2m > serial > bus info > hw revision 0x0 > driver version 4.17.0 > > Device topology > - entity 1: source (1 pad, 1 link) > type Node subtype V4L flags 0 > pad0: Source > -> "proc":1 [ENABLED,IMMUTABLE] > > - entity 3: proc (2 pads, 2 links) > type Node subtype Unknown flags 0 > pad0: Sink > -> "sink":0 [ENABLED,IMMUTABLE] > pad1: Source > <- "source":0 [ENABLED,IMMUTABLE] > > - entity 6: sink (1 pad, 1 link) > type Node subtype V4L flags 0 > pad0: Sink > <- "proc":0 [ENABLED,IMMUTABLE] > > Compliance output > ================= > > v4l2-compliance -m /dev/media0 -v > v4l2-compliance SHA: e2038ec6451293787b929338c2a671c732b8693d, 64 bits This is an old version of v4l2-compliance. Can you update it to the latest version and run this again? Thank you! Hans
