From: Sibi Sankar <quic_sibis@quicinc.com>
To: <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>, <sboyd@kernel.org>
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>,
<nm@ti.com>, Sibi Sankar <quic_sibis@quicinc.com>
Subject: [PATCH V3 0/2] cpufreq: scmi: Add boost frequency support
Date: Fri, 8 Mar 2024 16:14:08 +0530 [thread overview]
Message-ID: <20240308104410.385631-1-quic_sibis@quicinc.com> (raw)
This series adds provision to mark dynamic opps as boost capable and adds
boost frequency support to the scmi cpufreq driver.
V3:
* Don't set per-policy boost flags from the cpufreq driver. [Viresh]
* Drop patch 1 since Viresh already pulled it in.
* Drop depends on bug link. [Viresh]
V2:
* Document boost flag. [Lukasz]
* Remove sustained_freq check. [Pierre]
* simplify sustained_freq_khz calculation. [Sudeep]
* fix default per-policy state. [Dietmar]
* fix typo in commit message in patch 3.
Sibi Sankar (2):
firmware: arm_scmi: Add support for marking certain frequencies as
boost
cpufreq: scmi: Enable boost support
drivers/cpufreq/scmi-cpufreq.c | 20 +++++++++++++++++++-
drivers/firmware/arm_scmi/perf.c | 8 +++++++-
2 files changed, 26 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2024-03-08 10:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 10:44 Sibi Sankar [this message]
2024-03-08 10:44 ` [PATCH V3 1/2] firmware: arm_scmi: Add support for marking certain frequencies as boost Sibi Sankar
2024-03-08 13:59 ` Sudeep Holla
2024-03-11 5:35 ` Dhruva Gole
2024-03-11 5:49 ` Viresh Kumar
2024-03-08 10:44 ` [PATCH V3 2/2] cpufreq: scmi: Enable boost support Sibi Sankar
2024-03-08 14:06 ` Sudeep Holla
2024-03-11 4:55 ` Viresh Kumar
2024-03-11 9:04 ` Sudeep Holla
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=20240308104410.385631-1-quic_sibis@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;
as well as URLs for NNTP newsgroup(s).