On 11/11/2018 09:28 PM, Pavel Machek wrote: > Hi! > >> Em Wed, 31 Oct 2018 11:05:09 -0700 >> Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> escreveu: >> >>> On Tue, Oct 30, 2018 at 6:53 AM Mauro Carvalho Chehab >>> <mchehab+samsung@xxxxxxxxxx> wrote: >>>> >>>> For a new media API: the request API >>> >>> Ugh. I don't know how much being in staging matters - if people start >>> using it, they start using it. >>> >>> "Staging" does not mean "regressions don't matter". >> >> Yes, I know. >> >> This shouldn't affect normal cameras and generic V4L2 apps, as this >> is for very advanced use cases. So, we hope that people won't start >> using it for a while. >> >> The main interested party on this is Google CromeOS. We're working >> together with them in order to do upstream first. They are well aware >> that the API may change. So, I don't expect any complaints from their >> side if the API would require further changes. > > You may want to simply disable it in Kconfig... ChromeOS people can > enable it easily, and if it never worked in the mainline, you get some > wiggle room :-). > Pavel > For the record: there are no known issues with the Request API. The only outstanding issue is with a control introduced in the staging cedrus driver which will have to change since the method used to refer to MPEG reference frames is wrong. We're working on that and should have this fixed soon (patches have been posted and I'm waiting for test feedback). This control has nothing to do with the Request API, so I see no reason to put the Request API under a config option. Drivers needs to explicit enable support for the Request API anyway, so all existing drivers will return an error if userspace attempts to use this API. Regards, Hans
