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 ? -- Regards, Laurent Pinchart -- 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
