Hi Todor, everyone, On Monday, November 20, 2017 11:59 AM, Daniel Mack wrote: > On Monday, November 20, 2017 09:32 AM, Todor Tomov wrote: >> It is not a missing feature, it is more of a missing userspace implementation. >> When working with a media oriented device driver, the userspace has to >> config the media pipeline too and if controls are exposed by the subdev nodes, >> the userspace has to configure them on the subdev nodes. >> >> As there weren't a lot of media oriented drivers there is no generic >> implementation/support for this in the userspace (at least I'm not aware of >> any). There have been discussions about adding such functionality in libv4l >> so that applications which do not support media configuration can still >> use these drivers. I'm not sure if decision for this was taken or not or >> is it just that there was noone to actually do the work. Probably Laurent, >> Mauro or Hans know more about what were the plans for this. > > Hmm, that's not good. > > Considering the use-case in our application, the pipeline is set up once > and considered more or less static, and then applications such as the > Chrome browsers make use of the high-level VFE interface. If there are > no controls exposed on that interface, they are not available to the > application. Patching all userspace applications is an uphill battle > that can't be won I'm afraid. > > Is there any good reason not to expose the sensor controls on the VFE? I > guess it would be easy to do, right? Do you see an alternative to implementing the above in order to support existing v4l-enabled applications? Thanks, Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
