[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20221114065143.73gbfzfoihwobzjz@vireshk-i7>
Date: Mon, 14 Nov 2022 12:21:43 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
Cc: Sudeep Holla <sudeep.holla@....com>,
Manivannan Sadhasivam <mani@...nel.org>, andersson@...nel.org,
krzysztof.kozlowski+dt@...aro.org, rafael@...nel.org,
robh+dt@...nel.org, johan@...nel.org, devicetree@...r.kernel.org,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-pm@...r.kernel.org
Subject: Re: [PATCH v5 3/3] cpufreq: qcom-hw: Add CPU clock provider support
On 14-11-22, 11:55, Manivannan Sadhasivam wrote:
> On Mon, Nov 14, 2022 at 08:46:58AM +0530, Viresh Kumar wrote:
> > On 09-11-22, 16:47, Sudeep Holla wrote:
> > > Is the cpufreq_get() API expected
> > > to return something close to what was set or is it expected to return the
> > > real set h/w value if and when possible.
> >
> > The real frequency the hardware is running at.
> >
>
> Oh... In that case, qcom-cpufreq-hw driver is not returning the real frequency
> but instead whatever set by the cpufreq core previously using target_index().
>
> Should I fix it too in the next version of this series?
Yes.
--
viresh
Powered by blists - more mailing lists