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>,
<sumitg@nvidia.com>, <amiettinen@nvidia.com>
Subject: [Patch v3 0/2] Improvements to the Tegra CPUFREQ driver
Date: Wed, 4 Oct 2023 19:35:35 +0530 [thread overview]
Message-ID: <20231004140537.1954-1-sumitg@nvidia.com> (raw)
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.
---
v1[2] -> v3:
- Patch 1: used sizeof(*data->cpu_data) in devm_kcalloc().
v1[1] -> v2:
- Patch 1: added new patch.
- Patch 2: changed subject and patch order.
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(-)
[2] https://lore.kernel.org/lkml/20230901164113.29139-1-sumitg@nvidia.com/
[1] https://lore.kernel.org/lkml/20230901152046.25662-1-sumitg@nvidia.com/
--
2.17.1
next reply other threads:[~2023-10-04 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 14:05 Sumit Gupta [this message]
2023-10-04 14:05 ` [Patch v3 1/2] cpufreq: tegra194: save CPU data to avoid repeated SMP calls Sumit Gupta
2023-10-04 14:05 ` [Patch v3 2/2] cpufreq: tegra194: use refclk delta based loop instead of udelay Sumit Gupta
2023-10-09 11:36 ` [Patch v3 0/2] Improvements to the Tegra CPUFREQ driver Sumit Gupta
2023-10-10 5:37 ` Viresh Kumar
2023-10-10 5:43 ` 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=20231004140537.1954-1-sumitg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.