[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201028144628.qm2t2hbzmouqkciy@vireshk-i7>
Date: Wed, 28 Oct 2020 20:16:28 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Frank Lee <tiny.windzz@...il.com>
Cc: Frank Lee <frank@...winnertech.com>,
Rob Clark <robdclark@...il.com>, Sean Paul <sean@...rly.run>,
airlied@...ux.ie, daniel@...ll.ch,
Viresh Kumar <vireshk@...nel.org>, Nishanth Menon <nm@...com>,
Stephen Boyd <sboyd@...nel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>, jcrouse@...eaurora.org,
eric@...olt.net, kholk11@...il.com, emil.velikov@...labora.com,
gustavoars@...nel.org, linux-arm-msm@...r.kernel.org,
dri-devel@...ts.freedesktop.org, freedreno@...ts.freedesktop.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux PM <linux-pm@...r.kernel.org>
Subject: Re: [PATCH 2/3] opp: Add devres wrapper for dev_pm_opp_set_prop_name
On 28-10-20, 19:02, Frank Lee wrote:
> On Wed, Oct 28, 2020 at 6:29 PM Viresh Kumar <viresh.kumar@...aro.org> wrote:
> >
> > On 12-10-20, 21:55, Frank Lee wrote:
> > > From: Yangtao Li <tiny.windzz@...il.com>
> > >
> > > Add devres wrapper for dev_pm_opp_set_prop_name() to simplify driver
> > > code.
> > >
> > > Signed-off-by: Yangtao Li <tiny.windzz@...il.com>
> > > Signed-off-by: Yangtao Li <frank@...winnertech.com>
> > > ---
> > > drivers/opp/core.c | 39 +++++++++++++++++++++++++++++++++++++++
> > > include/linux/pm_opp.h | 6 ++++++
> > > 2 files changed, 45 insertions(+)
> >
> > On a second thought I am looking at dropping this one as you haven't
> > added any users yet and I am afraid it will stay unused.
>
> Now it looks like that dev_pm_opp_set_prop_name() is used relatively less.
> Maybe we can wait until a caller, and then pick up the patch.
I am even wondering if we should be adding any of the devm_* helpers
for now to be honest. Even for the other one we have only one user.
Them major user of the OPP core is the CPU subsystem and it is never
going to use these devm_* helpers as the CPU device doesn't get bound
to a driver, it is rather a fake platform device which gets the
cpufreq drivers probed. So the only users of these devm_* helpers is
going to be non-CPU devices. Considering that we have only one user
right now, it may be better to just fix it instead of adding any of
the devm_* helpers.
--
viresh
Powered by blists - more mailing lists