From: Jon Hunter <jonathanh@nvidia.com>
To: Sumit Gupta <sumitg@nvidia.com>, <viresh.kumar@linaro.org>,
<rjw@rjwysocki.net>, <thierry.reding@gmail.com>,
<linux-pm@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <sudeep.holla@arm.com>
Cc: <ksitaraman@nvidia.com>, <bbasu@nvidia.com>
Subject: Re: [Patch 2/2] cpufreq: tegra194: Fix unlisted boot freq warning
Date: Thu, 17 Sep 2020 09:45:03 +0100 [thread overview]
Message-ID: <f387abcc-f68f-37fb-32cb-d8eb9c75b37a@nvidia.com> (raw)
In-Reply-To: <53d4513d-0232-0287-9610-3e9ed8888273@nvidia.com>
On 17/09/2020 09:38, Jon Hunter wrote:
>
> 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@nvidia.com>
> Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
> Tested-by: Jon Hunter <jonathanh@nvidia.com>
>
> Viresh, this is also needed for v5.9.
Adding Sudeep.
Jon
--
nvpublic
next prev parent reply other threads:[~2020-09-17 8:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 17:11 [Patch 0/2] Tegra194 cpufreq driver misc changes Sumit Gupta
2020-09-16 17:11 ` [Patch 1/2] cpufreq: tegra194: get consistent cpuinfo_cur_freq Sumit Gupta
2020-09-17 8:36 ` Jon Hunter
2020-09-17 8:44 ` Jon Hunter
2020-09-23 8:34 ` Jon Hunter
2020-10-05 4:34 ` Viresh Kumar
2020-10-05 9:12 ` Jon Hunter
2020-09-24 8:56 ` Thierry Reding
2020-10-05 4:46 ` Viresh Kumar
2020-10-05 18:40 ` Sumit Gupta
2020-09-16 17:11 ` [Patch 2/2] cpufreq: tegra194: Fix unlisted boot freq warning Sumit Gupta
2020-09-17 8:38 ` Jon Hunter
2020-09-17 8:45 ` Jon Hunter [this message]
2020-09-24 8:56 ` Thierry Reding
2020-10-05 4:54 ` Viresh Kumar
2020-10-05 18:54 ` Sumit Gupta
2020-10-06 5:38 ` Viresh Kumar
2020-10-08 11:11 ` Sumit Gupta
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=f387abcc-f68f-37fb-32cb-d8eb9c75b37a@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=bbasu@nvidia.com \
--cc=ksitaraman@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sudeep.holla@arm.com \
--cc=sumitg@nvidia.com \
--cc=thierry.reding@gmail.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).