From: Sumit Gupta <sumitg@nvidia.com>
To: Jon Hunter <jonathanh@nvidia.com>, <rafael@kernel.org>,
<viresh.kumar@linaro.org>, <linux-pm@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <treding@nvidia.com>, <bbasu@nvidia.com>
Subject: Re: [Patch] driver: cpufreq: use refclk delta based loop instead of udelay
Date: Fri, 1 Sep 2023 22:19:46 +0530 [thread overview]
Message-ID: <f0059dd9-e258-80e9-bc4d-c8ee0c72a754@nvidia.com> (raw)
In-Reply-To: <c2bc6447-d8de-4f0f-d735-df377ab40f1c@nvidia.com>
On 01/09/23 21:28, Jon Hunter wrote:
>
>
> On 01/09/2023 16:20, Sumit Gupta wrote:
>> Use reference clock count based loop instead of "udelay()" for
>> sampling of counters to improve the accuracy of re-generated CPU
>> frequency. "udelay()" internally calls "WFE" which stops the
>> counters and results in bigger delta between the last set freq
>> and the re-generated value from counters. The counter sampling
>> window used in loop is the minimum number of reference clock
>> cycles which is known to give a stable value of CPU frequency.
>> The change also helps to reduce the sampling window from "500us"
>> to "<50us".
>>
>> Suggested-by: Antti Miettinen <amiettinen@nvidia.com>
>> Signed-off-by: Sumit Gupta <sumitg@nvidia.com>
>
>
> Please can you correct the subject and drop the 'driver:'.
>
> Jon
>
Corrected subject and added another patch in v2 at [1].
[1] https://lore.kernel.org/lkml/20230901164113.29139-1-sumitg@nvidia.com/
Thank you,
Sumit Gupta
prev parent reply other threads:[~2023-09-01 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 15:20 Sumit Gupta
2023-09-01 15:58 ` Jon Hunter
2023-09-01 16:49 ` Sumit Gupta [this message]
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=f0059dd9-e258-80e9-bc4d-c8ee0c72a754@nvidia.com \
--to=sumitg@nvidia.com \
--cc=bbasu@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=treding@nvidia.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
Powered by JetHome