On Thu, Dec 14, 2017 at 02:49:11PM -0200, Mauro Carvalho Chehab wrote: > Em Mon, 20 Nov 2017 11:59:59 +0100 > Daniel Mack <daniel@xxxxxxxxxx> escreveu: > > > Hi Todor, > > > > Thanks for following up! > > > > On Monday, November 20, 2017 09:32 AM, Todor Tomov wrote: > > > On 15.11.2017 21:31, Daniel Mack wrote: > > >> Todor et all, > > >> > > >> Any hint on how to tackle this? > > >> > > >> I can contribute patches, but I'd like to understand what the idea is. > > >> > > >> > > >> Thanks, > > >> Daniel > > >> > > >> > > >> On Thursday, October 26, 2017 06:11 PM, Daniel Mack wrote: > > >>> Hi Todor, > > >>> > > >>> When using the camss driver trough one of its /dev/videoX device nodes, > > >>> applications are currently unable to see the video controls the camera > > >>> sensor exposes. > > >>> > > >>> Same goes for other ioctls such as VIDIOC_ENUM_FMT, so the only valid > > >>> resolution setting for applications to use is the one that was > > >>> previously set through the media controller layer. Applications usually > > >>> query the available formats and then pick one using the standard V4L2 > > >>> APIs, and many can't easily be forced to use a specific one. > > >>> > > >>> If I'm getting this right, could you explain what's the rationale here? > > >>> Is that simply a missing feature or was that approach chosen on purpose? > > >>> > > > > > > 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? > > Sorry for a late answer. I'm usually very busy on 4Q, but this year, it > was atypical. > > A little historic is needed in order to answer this question. > Up to very recently, V4L2 drivers that are media-controller centric, > e. g. whose sub-devices are controlled directly by subdev devnodes, > were used only on specialized hardware, with special V4L2 applications > designed for them. In other words, it was designed to be used by generic > applications (although we always wanted a solution for it), and this > was never a real problem so far. > > However, with the advent of cheap SoC hardware with complex media > processors on it, the scenario changed recently, and we need some > discussions upstream about the best way to solve it. > > The original idea, back when the media controller was introduced, > were to add support at libv4l. But this never happened, and it turns > to be a way more complex than originally foreseen. > > As you're pointing, on such scenarios, one alternative is to expose subdev > controls also to the /dev/video devnode that is controlling the pipeline > streaming. However, depending on the pipeline, this may not be possible, > as the same control could be implemented on more than on block inside > the pipeline. When such case happens, the proper solution is to pinpoint > what sub-device will handle the control via the subdev API. > > However, on several scenarios (like, for instance, a RPi3 with > a single camera sensor), the pipeline is simple enough to either > avoid such conflicts, or to have an obvious subdevice that would > be handling such control. > > From my PoV, on cases like RPi3, the best is to just implement control > propagation inside the pipelines. However, other media core developers > think otherwise. > > If you can provide us a broader view about what are the issues that > you're facing, what's your use case scenario and what are the pipelines, > this could be valuable for us to improve our discussions about the > best way to solve it. > > Please notice, however, that this is not the best time for taking > such discussions, as several core developers will be taking > vacations those days. I marked the patch obsoleted for now --- the controls available are dependent on the pipeline and the pipeline may change, leading the handler pointing to a different device's control handler. I certainly have no problems in doing this in principle, but it cannot currently be done safely nor correctly in the kernel in many cases. As the controls available in the video node, in general case, would comprise of controls from several different devices, and thus several different control handlers, there may well be duplicates and in this case the kernel would have no clue what to do in such a case. In user space you can have policies that could be applied in such a case; the kernel just provides an interface to the hardware, effectively. Regarding this topic --- there's work beginning towards supporting complex cameras in Linux and this particular matter belongs to the same problem area. -- Kind regards, Sakari Ailus e-mail: sakari.ailus@xxxxxx
