From: Sibi Sankar <quic_sibis@quicinc.com>
To: Trilok Soni <quic_tsoni@quicinc.com>, <sudeep.holla@arm.com>,
<cristian.marussi@arm.com>, <rafael@kernel.org>,
<viresh.kumar@linaro.org>, <morten.rasmussen@arm.com>,
<dietmar.eggemann@arm.com>, <lukasz.luba@arm.com>,
<pierre.gondois@arm.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<quic_mdtipton@quicinc.com>, <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH V3 1/2] cpufreq: Export cpufreq_update_pressure
Date: Wed, 28 Feb 2024 10:46:19 +0530 [thread overview]
Message-ID: <377c1b4f-9357-112c-009c-fd6a757665b9@quicinc.com> (raw)
In-Reply-To: <2b68e15b-71ce-cf3b-a42d-e3e18aeb5ef2@quicinc.com>
On 2/28/24 01:02, Trilok Soni wrote:
> On 2/27/2024 10:16 AM, Sibi Sankar wrote:
>> The SCMI cpufreq driver doesn't require any additional signal
>> smoothing provided by arch_update_hw_pressure interface, export
>> cpufreq_update_pressure so that it can be called upon directly
>> instead.
>>
>> Suggested-by: Lukasz Luba <lukasz.luba@arm.com>
>> Signed-off-by: Sibi Sankar <quic_sibis@quicinc.com>
>> ---
>> drivers/cpufreq/cpufreq.c | 3 ++-
>> include/linux/cpufreq.h | 2 ++
>> 2 files changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
>> index 76002aa3d12d..bdec2dfd77eb 100644
>> --- a/drivers/cpufreq/cpufreq.c
>> +++ b/drivers/cpufreq/cpufreq.c
>> @@ -2573,7 +2573,7 @@ DEFINE_PER_CPU(unsigned long, cpufreq_pressure);
>> *
>> * Update the value of cpufreq pressure for all @cpus in the policy.
>> */
>> -static void cpufreq_update_pressure(struct cpufreq_policy *policy)
>> +void cpufreq_update_pressure(struct cpufreq_policy *policy)
>> {
>> unsigned long max_capacity, capped_freq, pressure;
>> u32 max_freq;
>> @@ -2598,6 +2598,7 @@ static void cpufreq_update_pressure(struct cpufreq_policy *policy)
>> for_each_cpu(cpu, policy->related_cpus)
>> WRITE_ONCE(per_cpu(cpufreq_pressure, cpu), pressure);
>> }
>> +EXPORT_SYMBOL(cpufreq_update_pressure);
>
> EXPORT_SYMBOL_GPL please. Other symbols in this file are _GPL as well.
Hey Trilok,
Thanks for catching this. Will fix it in the re-spin.
-Sibi
>
>>
>> /**
>> * cpufreq_set_policy - Modify cpufreq policy parameters.
>> diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
>> index 414bfc976b30..957bf8e4ca0d 100644
>> --- a/include/linux/cpufreq.h
>> +++ b/include/linux/cpufreq.h
>> @@ -241,6 +241,7 @@ struct kobject *get_governor_parent_kobj(struct cpufreq_policy *policy);
>> void cpufreq_enable_fast_switch(struct cpufreq_policy *policy);
>> void cpufreq_disable_fast_switch(struct cpufreq_policy *policy);
>> bool has_target_index(void);
>> +void cpufreq_update_pressure(struct cpufreq_policy *policy);
>>
>> DECLARE_PER_CPU(unsigned long, cpufreq_pressure);
>> static inline unsigned long cpufreq_get_pressure(int cpu)
>> @@ -270,6 +271,7 @@ static inline bool cpufreq_supports_freq_invariance(void)
>> }
>> static inline void disable_cpufreq(void) { }
>> static inline void cpufreq_update_limits(unsigned int cpu) { }
>> +static inline void cpufreq_update_pressure(struct cpufreq_policy *policy) { }
>> static inline unsigned long cpufreq_get_pressure(int cpu)
>> {
>> return 0;
next prev parent reply other threads:[~2024-02-28 5:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 18:16 [PATCH V3 0/2] firmware: arm_scmi: Register and handle limits change notification Sibi Sankar
2024-02-27 18:16 ` [PATCH V3 1/2] cpufreq: Export cpufreq_update_pressure Sibi Sankar
2024-02-27 19:32 ` Trilok Soni
2024-02-28 5:16 ` Sibi Sankar [this message]
2024-02-27 18:16 ` [PATCH V3 2/2] cpufreq: scmi: Register for limit change notifications Sibi Sankar
2024-02-28 13:24 ` Lukasz Luba
2024-02-28 17:00 ` Sibi Sankar
2024-02-29 9:59 ` Lukasz Luba
2024-02-29 10:22 ` Lukasz Luba
2024-02-29 11:28 ` Cristian Marussi
2024-02-29 11:45 ` Lukasz Luba
2024-02-29 12:11 ` Cristian Marussi
2024-02-29 14:15 ` Lukasz Luba
2024-03-01 5:31 ` Sibi Sankar
2024-03-22 10:45 ` Lukasz Luba
2024-03-26 5:25 ` Sibi Sankar
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=377c1b4f-9357-112c-009c-fd6a757665b9@quicinc.com \
--to=quic_sibis@quicinc.com \
--cc=cristian.marussi@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=morten.rasmussen@arm.com \
--cc=pierre.gondois@arm.com \
--cc=quic_mdtipton@quicinc.com \
--cc=quic_tsoni@quicinc.com \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.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®