From: Beata Michalska <beata.michalska@arm.com>
To: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
sumitg@nvidia.com
Cc: sudeep.holla@arm.covm, will@kernel.org, catalin.marinas@arm.com,
viresh.kumar@linaro.org, rafael@kernel.org,
ionela.voinescu@arm.com, yang@os.amperecomputing.com,
linux-tegra@vger.kernel.org
Subject: [PATCH v2 0/2] Add support for AArch64 AMUv1-based arch_freq_get_on_cpu
Date: Mon, 27 Nov 2023 16:08:36 +0000 [thread overview]
Message-ID: <20231127160838.1403404-1-beata.michalska@arm.com> (raw)
Introducing AArch64 specific version of arch_freq_get_on_cpu, cashing on
existing implementation for FIE and AMUv1 support.
Additionally wiring it up with cpufreq_verify_current_freq to hopefully
eliminate issues when cpufreq_driver->get() returns frequency that is not
entirely aligned.
The changes have been rather lightly (due to some limitations) tested on
an FVP model.
v2:
- Splitting the patches
- Adding comment for full dyntick mode
- Plugging arch_freq_get_on_cpu into cpufreq_verify_current_freq instead
of in show_cpuinfo_cur_freq to allow the framework to stay more in sync
with potential freq changes
[1]
https://lore.kernel.org/lkml/20230606155754.245998-1-beata.michalska@arm.com/
Beata Michalska (1):
arm64: Provide an AMU-based version of arch_freq_get_on_cpu
Sumit Gupta (1):
cpufreq: Wire-up arch-flavored freq info into
cpufreq_verify_current_freq
arch/arm64/kernel/topology.c | 39 ++++++++++++++++++++++++++++++++++++
drivers/cpufreq/cpufreq.c | 3 ++-
2 files changed, 41 insertions(+), 1 deletion(-)
--
2.25.1
next reply other threads:[~2023-11-27 16:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 16:08 Beata Michalska [this message]
2023-11-27 16:08 ` [PATCH v2 1/2] arm64: Provide an AMU-based version of arch_freq_get_on_cpu Beata Michalska
2023-11-28 15:13 ` Ionela Voinescu
2024-02-02 9:20 ` Beata Michalska
2024-02-22 19:55 ` Vanshidhar Konda
2023-11-27 16:08 ` [PATCH v2 2/2] cpufreq: Wire-up arch-flavored freq info into cpufreq_verify_current_freq Beata Michalska
2023-11-28 14:01 ` Ionela Voinescu
2023-12-01 13:02 ` Sumit Gupta
2023-12-05 11:05 ` Ionela Voinescu
2023-12-06 13:28 ` Sumit Gupta
2023-12-07 9:22 ` Ionela Voinescu
2023-12-08 15:34 ` Sumit Gupta
2024-02-02 9:14 ` Beata Michalska
2023-12-06 20:41 ` Rafael J. Wysocki
2024-02-02 9:05 ` Beata Michalska
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=20231127160838.1403404-1-beata.michalska@arm.com \
--to=beata.michalska@arm.com \
--cc=catalin.marinas@arm.com \
--cc=ionela.voinescu@arm.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=rafael@kernel.org \
--cc=sudeep.holla@arm.covm \
--cc=sumitg@nvidia.com \
--cc=viresh.kumar@linaro.org \
--cc=will@kernel.org \
--cc=yang@os.amperecomputing.com \
/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