From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>,
Sudeep Holla <sudeep.holla@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
Ionela Voinescu <ionela.voinescu@arm.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH V6 3/4] arch_topology: Export arch_freq_scale and helpers
Date: Wed, 10 Mar 2021 10:53:25 +0530 [thread overview]
Message-ID: <1b5c83549720da480b1e23e542f44b1edb2e4157.1615351622.git.viresh.kumar@linaro.org> (raw)
In-Reply-To: <cover.1615351622.git.viresh.kumar@linaro.org>
It is possible now for other parts of the kernel to provide their own
implementation of sched_freq_tick() and they can very well be modules
themselves (like CPPC cpufreq driver, which is going to use these in a
later commit).
Export arch_freq_scale and topology_{set|clear}_scale_freq_source().
Reviewed-by: Ionela Voinescu <ionela.voinescu@arm.com>
Tested-by: Ionela Voinescu <ionela.voinescu@arm.com>
Tested-by: Vincent Guittot <vincent.guittot@linaro.org>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
---
drivers/base/arch_topology.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/base/arch_topology.c b/drivers/base/arch_topology.c
index ebcd2ea3091f..995e52b9eca4 100644
--- a/drivers/base/arch_topology.c
+++ b/drivers/base/arch_topology.c
@@ -78,6 +78,7 @@ void topology_set_scale_freq_source(struct scale_freq_data *data,
update_scale_freq_invariant(true);
}
+EXPORT_SYMBOL_GPL(topology_set_scale_freq_source);
void topology_clear_scale_freq_source(enum scale_freq_source source,
const struct cpumask *cpus)
@@ -96,6 +97,7 @@ void topology_clear_scale_freq_source(enum scale_freq_source source,
update_scale_freq_invariant(false);
}
+EXPORT_SYMBOL_GPL(topology_clear_scale_freq_source);
void topology_scale_freq_tick(void)
{
@@ -106,6 +108,7 @@ void topology_scale_freq_tick(void)
}
DEFINE_PER_CPU(unsigned long, arch_freq_scale) = SCHED_CAPACITY_SCALE;
+EXPORT_SYMBOL_GPL(arch_freq_scale);
void topology_set_freq_scale(const struct cpumask *cpus, unsigned long cur_freq,
unsigned long max_freq)
--
2.25.0.rc1.19.g042ed3e048af
next prev parent reply other threads:[~2021-03-10 5:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 5:23 [PATCH V6 0/4] cpufreq: cppc: Add support for frequency invariance Viresh Kumar
2021-03-10 5:23 ` [PATCH V6 1/4] arch_topology: Rename freq_scale as arch_freq_scale Viresh Kumar
2021-04-19 12:33 ` Will Deacon
2021-03-10 5:23 ` [PATCH V6 2/4] arch_topology: Allow multiple entities to provide sched_freq_tick() callback Viresh Kumar
2021-03-10 5:23 ` Viresh Kumar [this message]
2021-03-12 5:05 ` [PATCH V6 3/4] arch_topology: Export arch_freq_scale and helpers Viresh Kumar
2021-03-10 5:23 ` [PATCH V6 4/4] cpufreq: CPPC: Add support for frequency invariance Viresh Kumar
2021-03-19 16:20 ` Rafael J. Wysocki
2021-03-22 3:24 ` Viresh Kumar
2021-06-09 15:46 ` [PATCH V6 0/4] cpufreq: cppc: " Qian Cai
2021-06-10 3:07 ` Qian Cai
2021-06-10 8:25 ` Viresh Kumar
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=1b5c83549720da480b1e23e542f44b1edb2e4157.1615351622.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=ionela.voinescu@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@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).