[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABymUCO4Gb-vALx=qa1q=QNfTJWoqNpT2r3J_xHxhGk7FZE0nQ@mail.gmail.com>
Date: Mon, 6 Mar 2023 18:48:09 +0800
From: Jun Nie <jun.nie@...aro.org>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: cw00.choi@...sung.com, Nishanth Menon <nm@...com>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Stephen Boyd <sboyd@...nel.org>,
Viresh Kumar <vireshk@...nel.org>, linux-pm@...r.kernel.org,
Vincent Guittot <vincent.guittot@...aro.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] OPP: Simplify set_required_opp handling
Viresh Kumar <viresh.kumar@...aro.org> 于2023年2月27日周一 17:29写道:
>
> On 27-02-23, 17:21, Jun Nie wrote:
> > Sorry for not expressing it accurately. I should say devfreq devices
> > pointers, just
> > devfreq_virt_devs vs genpd_virt_devs. Then you know why I add devfreq-devs
> > dts nodes below.
>
> Won't something like dev_pm_opp_set_clkname() would be enough here too ? We
> already do this kind of work for clks and regulators.
Thanks! It is a possible solution. I will try to spare time on this as
higher priority tasks
are on my list.
>
> Having power domain specific information within CPU nodes isn't a requirement of
> the OPP core, but the general requirement of genpd core instead.
>
> --
> viresh
Powered by blists - more mailing lists