From: Sibi Sankar <quic_sibis@quicinc.com>
To: Dietmar Eggemann <dietmar.eggemann@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: <cristian.marussi@arm.com>, <rafael@kernel.org>,
<morten.rasmussen@arm.com>, <lukasz.luba@arm.com>,
<sboyd@kernel.org>, <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>,
<nm@ti.com>
Subject: Re: [PATCH 0/3] cpufreq: scmi: Add boost frequency support
Date: Wed, 28 Feb 2024 00:14:57 +0530 [thread overview]
Message-ID: <642ac3e4-d083-43fd-c0db-24e2bc4cb6a9@quicinc.com> (raw)
In-Reply-To: <265e5f2c-9b45-420f-89b1-44369aeb8418@arm.com>
On 2/15/24 20:27, Dietmar Eggemann wrote:
> On 13/02/2024 08:35, Sibi Sankar wrote:
>>
>>
>> On 1/31/24 20:37, Dietmar Eggemann wrote:
>>> On 23/01/2024 11:15, Sudeep Holla wrote:
>>>> On Tue, Jan 23, 2024 at 11:38:27AM +0530, Viresh Kumar wrote:
>>>>> On 17-01-24, 16:34, Sibi Sankar wrote:
>
> [...]
>
[...]
>>> BTW, what's the use case you have in mind for this feature? Is it to cap
>>> high OPPs for CPUs in a certain CPUfreq policy?
>>
>> Yeah, that's exactly the use case for X1E. Boost frequencies defined in
>> the SoC are achievable by only one CPU in a cluster i.e. either the
>> other CPUs in the same cluster should be in low power mode or offline.
>> So it's mostly for book keeping i.e. we wouldn't to intimate incorrectly
>> that the CPUs are running at max possible frequency when it's actually
>> running at a lower frequency.
>
> I see.
>
> What about the issue with the settings of the global and the per-policy
> 'boost' file?
>
> On my Juno-r0 the initial boost values are:
>
> (1) Initial setting:
>
> root@juno:/sys/devices/system/cpu/cpufreq# cat boost policy*/boost
> 1
> 0
> 0
>
> Should they not all be 1 ?
>
>
> (2) Disabling system-wide boost
>
> root@juno:/sys/devices/system/cpu/cpufreq# echo 0 > boost
>
> Here I see 'cpufreq_pressure > 0' for all CPUs.
>
>
> (3) Enabling system-wide boost
>
> root@juno:/sys/devices/system/cpu/cpufreq# echo 1 > boost
>
> And here 'cpufreq_pressure == 0' for all CPUs.
>
>
> (4) Disabling boost for policy0.
>
> root@juno:/sys/devices/system/cpu/cpufreq# echo 0 > policy0/boost
>
> root@juno:/sys/devices/system/cpu/cpufreq# cat boost policy*/boost
> 1
> 0
> 1
>
> Here nothing happened. But I was expecting to see 'cpufreq_pressure > 0'
> for CPUs of policy0:
>
https://patchwork.kernel.org/project/linux-arm-msm/cover/20240227165309.620422-1-quic_sibis@quicinc.com/
Finally got some time to fix this, I've posted out the fix and re-spun
the series as well. This should fix the default values of per-policy
boost flags as well.
-Sibi
> root@juno:/sys/devices/system/cpu/cpufreq# cat policy0/affected_cpus
> 0 3 4 5
prev parent reply other threads:[~2024-02-27 18:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 11:04 [PATCH 0/3] cpufreq: scmi: Add boost frequency support Sibi Sankar
2024-01-17 11:04 ` [PATCH 1/3] OPP: Extend dev_pm_opp_data with turbo support Sibi Sankar
2024-02-26 16:29 ` Lukasz Luba
2024-01-17 11:04 ` [PATCH 2/3] firmware: arm_scmi: Add support for marking certain frequencies as boost Sibi Sankar
2024-01-31 11:25 ` Sudeep Holla
2024-02-13 8:30 ` Sibi Sankar
2024-01-31 14:29 ` Pierre Gondois
2024-01-31 16:08 ` Sudeep Holla
2024-02-13 8:03 ` Sibi Sankar
2024-01-17 11:04 ` [PATCH 3/3] cpufreq: scmi: Enable boost support Sibi Sankar
2024-01-23 6:08 ` [PATCH 0/3] cpufreq: scmi: Add boost frequency support Viresh Kumar
2024-01-23 8:49 ` Cristian Marussi
2024-01-23 10:15 ` Sudeep Holla
2024-01-31 15:07 ` Dietmar Eggemann
2024-01-31 16:12 ` Sudeep Holla
2024-02-13 8:35 ` Sibi Sankar
2024-02-15 14:57 ` Dietmar Eggemann
2024-02-27 18:44 ` Sibi Sankar [this message]
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=642ac3e4-d083-43fd-c0db-24e2bc4cb6a9@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=nm@ti.com \
--cc=quic_mdtipton@quicinc.com \
--cc=rafael@kernel.org \
--cc=sboyd@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