From: Sudeep Holla <sudeep.holla@arm.com>
To: Sibi Sankar <quic_sibis@quicinc.com>
Cc: Dietmar Eggemann <dietmar.eggemann@arm.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
cristian.marussi@arm.com, Sudeep Holla <sudeep.holla@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, 31 Jan 2024 16:12:11 +0000 [thread overview]
Message-ID: <20240131161211.v3rhwidmdalfdvz7@bogus> (raw)
In-Reply-To: <e968092a-dc2b-4351-9489-acf874bbc7b6@arm.com>
On Wed, Jan 31, 2024 at 04:07:48PM +0100, Dietmar Eggemann wrote:
[...]
>
> root@juno:/sys/devices/system/cpu/cpufreq# cat boost policy*/boost
> 1
> 0
> 0
OK I admit, I wasn't aware of this per policy boost flag.
It must be enabled by default if it has any effect. Otherwise
it breaks the existing behaviour on all the SCMI based platforms.
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-01-31 16:12 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 [this message]
2024-02-13 8:35 ` Sibi Sankar
2024-02-15 14:57 ` Dietmar Eggemann
2024-02-27 18:44 ` 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=20240131161211.v3rhwidmdalfdvz7@bogus \
--to=sudeep.holla@arm.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=quic_sibis@quicinc.com \
--cc=rafael@kernel.org \
--cc=sboyd@kernel.org \
--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