From: Manivannan Sadhasivam <mani@kernel.org>
To: Douglas Anderson <dianders@chromium.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
swboyd@chromium.org, mka@chromium.org,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Sasha Levin <sashal@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH] cpufreq: qcom-hw: Fix cpufreq_driver->get() for non-LMH systems
Date: Sat, 4 Feb 2023 20:28:34 +0530 [thread overview]
Message-ID: <20230204145834.GA45501@thinkpad> (raw)
In-Reply-To: <20230202140005.1.I4b30aaa027c73372ec4068cc0f0dc665af8b938d@changeid>
On Thu, Feb 02, 2023 at 02:00:23PM -0800, Douglas Anderson wrote:
> On a sc7180-based Chromebook, when I go to
> /sys/devices/system/cpu/cpu0/cpufreq I can see:
>
> cpuinfo_cur_freq:2995200
> cpuinfo_max_freq:1804800
> scaling_available_frequencies:300000 576000 ... 1708800 1804800
> scaling_cur_freq:1804800
> scaling_max_freq:1804800
>
> As you can see the `cpuinfo_cur_freq` is bogus. It turns out that this
> bogus info started showing up as of commit 205f5e984d30 ("cpufreq:
> qcom-hw: Fix the frequency returned by cpufreq_driver->get()"). That
> commit seems to assume that everyone is on the LMH bandwagon, but
> sc7180 isn't.
>
Ah, missed that part.
> Let's go back to the old code in the case where LMH isn't used.
>
Thanks for fixing!
> Fixes: 205f5e984d30 ("cpufreq: qcom-hw: Fix the frequency returned by cpufreq_driver->get()")
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Manivannan Sadhasivam <mani@kernel.org>
Thanks,
Mani
> ---
>
> drivers/cpufreq/qcom-cpufreq-hw.c | 24 +++++++++++++-----------
> 1 file changed, 13 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/cpufreq/qcom-cpufreq-hw.c b/drivers/cpufreq/qcom-cpufreq-hw.c
> index 9505a812d6a1..957cf6bb8c05 100644
> --- a/drivers/cpufreq/qcom-cpufreq-hw.c
> +++ b/drivers/cpufreq/qcom-cpufreq-hw.c
> @@ -143,40 +143,42 @@ static unsigned long qcom_lmh_get_throttle_freq(struct qcom_cpufreq_data *data)
> return lval * xo_rate;
> }
>
> -/* Get the current frequency of the CPU (after throttling) */
> -static unsigned int qcom_cpufreq_hw_get(unsigned int cpu)
> +/* Get the frequency requested by the cpufreq core for the CPU */
> +static unsigned int qcom_cpufreq_get_freq(unsigned int cpu)
> {
> struct qcom_cpufreq_data *data;
> + const struct qcom_cpufreq_soc_data *soc_data;
> struct cpufreq_policy *policy;
> + unsigned int index;
>
> policy = cpufreq_cpu_get_raw(cpu);
> if (!policy)
> return 0;
>
> data = policy->driver_data;
> + soc_data = qcom_cpufreq.soc_data;
>
> - return qcom_lmh_get_throttle_freq(data) / HZ_PER_KHZ;
> + index = readl_relaxed(data->base + soc_data->reg_perf_state);
> + index = min(index, LUT_MAX_ENTRIES - 1);
> +
> + return policy->freq_table[index].frequency;
> }
>
> -/* Get the frequency requested by the cpufreq core for the CPU */
> -static unsigned int qcom_cpufreq_get_freq(unsigned int cpu)
> +static unsigned int qcom_cpufreq_hw_get(unsigned int cpu)
> {
> struct qcom_cpufreq_data *data;
> - const struct qcom_cpufreq_soc_data *soc_data;
> struct cpufreq_policy *policy;
> - unsigned int index;
>
> policy = cpufreq_cpu_get_raw(cpu);
> if (!policy)
> return 0;
>
> data = policy->driver_data;
> - soc_data = qcom_cpufreq.soc_data;
>
> - index = readl_relaxed(data->base + soc_data->reg_perf_state);
> - index = min(index, LUT_MAX_ENTRIES - 1);
> + if (data->throttle_irq >= 0)
> + return qcom_lmh_get_throttle_freq(data) / HZ_PER_KHZ;
>
> - return policy->freq_table[index].frequency;
> + return qcom_cpufreq_get_freq(cpu);
> }
>
> static unsigned int qcom_cpufreq_hw_fast_switch(struct cpufreq_policy *policy,
> --
> 2.39.1.519.gcb327c4b5f-goog
>
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2023-02-04 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 22:00 [PATCH] cpufreq: qcom-hw: Fix cpufreq_driver->get() for non-LMH systems Douglas Anderson
2023-02-02 22:35 ` Konrad Dybcio
2023-02-02 22:45 ` Konrad Dybcio
2023-02-02 23:38 ` Konrad Dybcio
2023-02-04 14:58 ` Manivannan Sadhasivam [this message]
2023-02-06 4:10 ` Viresh Kumar
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=20230204145834.GA45501@thinkpad \
--to=mani@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=dianders@chromium.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mka@chromium.org \
--cc=rafael@kernel.org \
--cc=sashal@kernel.org \
--cc=swboyd@chromium.org \
--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).