Hello Sakari, Thanks a lot for your comments. On Wed, 2020-02-26 at 17:53 +0200, Sakari Ailus wrote: > Hi Ezequiel, > > On Fri, Jan 24, 2020 at 05:35:43PM -0300, Ezequiel Garcia wrote: > > Currently, v4l2_pipeline_pm_use() prototype is: > > > > int v4l2_pipeline_pm_use(struct media_entity *entity, int use) > > > > Where the 'use' argument shall only be set to '1' for enable/power-on, > > or to '0' for disable/power-off. The integer return is specified > > as only meaningful when 'use' is set to '1'. > > > > Let's enforce this semantic by splitting the function in two: > > v4l2_pipeline_pm_get and v4l2_pipeline_pm_put. This is done > > for several reasons. > > > > It makes the API easier to use (or harder to misuse). > > It removes the constraint on the values the 'use' argument > > shall take. Also, it removes the need to constraint > > the return value, by making v4l2_pipeline_pm_put void return. > > > > And last, it's more consistent with other kernel APIs, such > > as the runtime pm APIs, which makes the code more symmetric. > > Indeed. These functions only exist because not all sensor etc. drivers have > been converted to runtime PM yet. New drivers no longer implement s_power > callbacks. > > I don't object the patch as such, but I think you could also add a note > that relying on the s_power callback is deprecated. This probably should be > a separate patch. > Hans picked this patch, sending a pull request yesterday which includes it. Since you know this API better than me, I thikn it would be best if you take care of sending a patch for it. In particular, I'd like to know as reference, if any changes are needed RKISP1 and sensors such as IMX219 in order to avoid relying in the deprecated API. Moreover, is there any way we can add some build time or run time warning, to avoid developers from using an API that is deprecated? Thanks! Ezequiel
