Hi Laurent, First, regarding the inheritance of subdev controls: I found it annoying as well that there is no way to do this. If you have a simple video pipeline, then having to create subdev nodes just to set a few controls is unnecessary complex. I've been thinking of adding a flag to the control handler that, when set, will 'import' the private controls. The bridge driver is the one that sets this as that is the only one that knows whether or not it is in fact a simple pipeline. Secondly, I'd love to add MC support to qv4l2. But I'm waiting for you to merge the MC library into v4l-utils.git. It's basically the reason why I haven't looked at this at all. Regards, Hans On 01/22/2014 11:55 PM, Laurent Pinchart wrote: > Hi Hans and Detlev, > > While reviewed driver code that models the hardware using the media > controller, I noticed a patch that enabled subdev controls inheritance for the > video nodes. While this is useful for fixed devices, the complexity, > genericity and flexibility of the hardware at hand makes this undesirable, > given that we can't guarantee that a control won't be instantiated more than > once in the pipeline. > > I've thus asked what triggered the need for controls inheritance, and found > out that the developers wanted to use qv4l2 as a demo application > (congratulations to Hans for such a useful application :-)). As qv4l2 doesn't > support subdevices, accessing controls required inheriting them on video > nodes. > > There's an existing GUI test application for media controller-based devices > called mci (https://gitorious.org/mci) but it hasn't been maintained for quite > some time, and isn't as feature-complete as qv4l2. I was thus wondering > whether it would make sense to add explicit media controller support to qv4l2, > or whether the two applications should remain separate (in the later case some > code could probably still be shared). > > Any opinion and/or desire to work on this ? > -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
