[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZyH9HvKmYjlJC8_x@pluto>
Date: Wed, 30 Oct 2024 09:32:14 +0000
From: Cristian Marussi <cristian.marussi@....com>
To: Sibi Sankar <quic_sibis@...cinc.com>
Cc: sudeep.holla@....com, cristian.marussi@....com, rafael@...nel.org,
viresh.kumar@...aro.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 V5 1/1] cpufreq: scmi: Register for limit change
notifications
On Tue, Jun 04, 2024 at 12:56:54AM +0530, Sibi Sankar wrote:
> Register for limit change notifications if supported and use the throttled
> frequency from the notification to apply HW pressure.
>
This sort of got lost in mbox...apologies.
As discussed offlist, the issue with cpufreq and multiple SCMI instances
remains BUT it will be solved later on with a different approach, so
as of now this LGTM.
Reviewed-by: Cristian Marussi <cristian.marussi@....com>
Thanks,
Cristian
P.S.: have you got any chance to try the hack/experimental patch I CCed
you to address the multi/instance cpufreq issues ? (just to understand
if it is a viable option...)
Powered by blists - more mailing lists