From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Manivannan Sadhasivam <mani@kernel.org>,
andersson@kernel.org, krzysztof.kozlowski+dt@linaro.org,
rafael@kernel.org, robh+dt@kernel.org, johan@kernel.org,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v5 3/3] cpufreq: qcom-hw: Add CPU clock provider support
Date: Mon, 14 Nov 2022 11:55:10 +0530 [thread overview]
Message-ID: <20221114062510.GB3869@thinkpad> (raw)
In-Reply-To: <20221114031658.pnbf7uiqqgiq3uk7@vireshk-i7>
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?
Thanks,
Mani
> --
> viresh
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2022-11-14 6:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 15:40 [PATCH v5 0/3] qcom-cpufreq-hw: Add CPU clock provider support Manivannan Sadhasivam
2022-11-08 15:40 ` [PATCH v5 1/3] dt-bindings: cpufreq: cpufreq-qcom-hw: Add cpufreq clock provider Manivannan Sadhasivam
2022-11-08 15:40 ` [PATCH v5 2/3] arm64: dts: qcom: sm8450: Supply clock from cpufreq node to CPUs Manivannan Sadhasivam
2022-11-08 15:40 ` [PATCH v5 3/3] cpufreq: qcom-hw: Add CPU clock provider support Manivannan Sadhasivam
2022-11-08 15:57 ` Sudeep Holla
2022-11-09 7:49 ` Manivannan Sadhasivam
2022-11-09 11:08 ` Sudeep Holla
2022-11-09 12:35 ` Manivannan Sadhasivam
2022-11-09 16:47 ` Sudeep Holla
2022-11-14 3:16 ` Viresh Kumar
2022-11-14 6:25 ` Manivannan Sadhasivam [this message]
2022-11-14 6:51 ` Viresh Kumar
2022-11-08 18:27 ` Matthias Kaehlcke
2022-11-09 7:55 ` Manivannan Sadhasivam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221114062510.GB3869@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johan@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mani@kernel.org \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).