From: Sumit Gupta <sumitg@nvidia.com>
To: <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>, <jonathanh@nvidia.com>, <bbasu@nvidia.com>,
<amiettinen@nvidia.com>, Sumit Gupta <sumitg@nvidia.com>
Subject: Re: [Patch v2 0/2] Improvements to the Tegra CPUFREQ driver
Date: Tue, 19 Sep 2023 16:58:07 +0530 [thread overview]
Message-ID: <961ffcb4-a9c6-2916-7b90-4a38b0ad465c@nvidia.com> (raw)
In-Reply-To: <20230901164113.29139-1-sumitg@nvidia.com>
Gentle Ping.
Thank you,
Sumit Gupta
On 01/09/23 22:11, Sumit Gupta wrote:
> This patch set adds below improvements to the Tegra194 CPUFREQ driver.
> They are applicable to all the Tegra SoC's supported by the driver.
>
> 1) Patch 1: Avoid making SMP call on every frequency request to reduce
> the time for frequency set and get calls.
>
> 2) Patch 2: Use reference clock count based loop instead of udelay()
> to improve the accuracy of re-generated CPU frequency.
>
> The patches are not related but have minor conflict. So, need to be
> applied in order of patch numbers. If 'Patch 2' is to be applied first
> then will rebase that and send separately.
>
> Sumit Gupta (2):
> cpufreq: tegra194: save CPU data to avoid repeated SMP calls
> cpufreq: tegra194: use refclk delta based loop instead of udelay
>
> drivers/cpufreq/tegra194-cpufreq.c | 151 ++++++++++++++++++++---------
> 1 file changed, 106 insertions(+), 45 deletions(-)
>
prev parent reply other threads:[~2023-09-19 11:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 16:41 Sumit Gupta
2023-09-01 16:41 ` [Patch v2 1/2] cpufreq: tegra194: save CPU data to avoid repeated SMP calls Sumit Gupta
2023-09-01 17:58 ` Jon Hunter
2023-09-01 19:51 ` Sumit Gupta
2023-09-28 7:05 ` Viresh Kumar
2023-09-29 14:17 ` Sumit Gupta
2023-10-03 5:00 ` Viresh Kumar
2023-10-04 14:11 ` Sumit Gupta
2023-09-01 16:41 ` [Patch v2 2/2] cpufreq: tegra194: use refclk delta based loop instead of udelay Sumit Gupta
2023-09-01 17:59 ` Jon Hunter
2023-09-01 19:53 ` Sumit Gupta
2023-09-19 11:28 ` 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=961ffcb4-a9c6-2916-7b90-4a38b0ad465c@nvidia.com \
--to=sumitg@nvidia.com \
--cc=amiettinen@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
all inboxes | Powered by JetHome®