[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20241119072759.oi75cdqrw4vl4fsc@vireshk-i7>
Date: Tue, 19 Nov 2024 12:57:59 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Sibi Sankar <quic_sibis@...cinc.com>
Cc: sudeep.holla@....com, cristian.marussi@....com, rafael@...nel.org,
morten.rasmussen@....com, dietmar.eggemann@....com,
lukasz.luba@....com, pierre.gondois@....com,
vincent.guittot@...aro.org, linux-arm-kernel@...ts.infradead.org,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
quic_mdtipton@...cinc.com, linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH V8 1/1] cpufreq: scmi: Register for limit change
notifications
On 14-11-24, 07:59, Sibi Sankar wrote:
> Register for limit change notifications if supported and use the throttled
> frequency from the notification to apply HW pressure.
>
> Signed-off-by: Sibi Sankar <quic_sibis@...cinc.com>
> Tested-by: Mike Tipton <quic_mdtipton@...cinc.com>
> Reviewed-by: Cristian Marussi <cristian.marussi@....com>
> Reviewed-by: Lukasz Luba <lukasz.luba@....com>
> ---
>
> v8:
> * Drop patch 1 since it was picked up by Viresh
> * Leave policy->max update to the cpufreq_qos notifier [Vincent]
> * We sanitized the range_max from V3 since we dealt with
> policy->max, now we can drop the check and policy member
> from scmi_data.
>
> drivers/cpufreq/scmi-cpufreq.c | 45 ++++++++++++++++++++++++++++++++++
> 1 file changed, 45 insertions(+)
Applied. Thanks.
--
viresh
Powered by blists - more mailing lists