On 02-02-23, 14:00, 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.
>
> Let's go back to the old code in the case where LMH isn't used.
>
> Fixes: 205f5e984d30 ("cpufreq: qcom-hw: Fix the frequency returned by cpufreq_driver->get()")
This is incorrect.
Fixes: c72cf0cb1d77 ("cpufreq: qcom-hw: Fix the frequency returned by cpufreq_driver->get()")
Applied. Thanks.
--
viresh
