[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53d4513d-0232-0287-9610-3e9ed8888273@nvidia.com>
Date: Thu, 17 Sep 2020 09:38:22 +0100
From: Jon Hunter <jonathanh@...dia.com>
To: Sumit Gupta <sumitg@...dia.com>, <viresh.kumar@...aro.org>,
<rjw@...ysocki.net>, <thierry.reding@...il.com>,
<linux-pm@...r.kernel.org>, <linux-tegra@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>
CC: <ksitaraman@...dia.com>, <bbasu@...dia.com>
Subject: Re: [Patch 2/2] cpufreq: tegra194: Fix unlisted boot freq warning
On 16/09/2020 18:11, Sumit Gupta wrote:
> Warning coming during boot because the boot freq set by bootloader
> gets filtered out due to big freq steps while creating freq_table.
> Fixing this by setting closest ndiv value from freq_table.
> Warning:
> cpufreq: cpufreq_online: CPU0: Running at unlisted freq
> cpufreq: cpufreq_online: CPU0: Unlisted initial frequency changed
>
> Also, added change in init to wait till current frequency becomes
> equal or near to the previously requested frequency. This is done
> because it takes some time to restore the previous frequency while
> turning-on non-boot cores during exit from SC7(Suspend-to-RAM).
Same here ...
Fixes: df320f89359c ("cpufreq: Add Tegra194 cpufreq driver")
>
> Signed-off-by: Sumit Gupta <sumitg@...dia.com>
Reviewed-by: Jon Hunter <jonathanh@...dia.com>
Tested-by: Jon Hunter <jonathanh@...dia.com>
Viresh, this is also needed for v5.9.
Thanks
Jon
--
nvpublic
Powered by blists - more mailing lists