From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Alyssa Rosenzweig <alyssa@rosenzweig.io>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Cristian Marussi <cristian.marussi@arm.com>,
"Gautham R. Shenoy" <gautham.shenoy@amd.com>,
Hector Martin <marcan@marcan.st>,
Huacai Chen <chenhuacai@kernel.org>,
Huang Rui <ray.huang@amd.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Naveen N Rao <naveen@kernel.org>,
Nicholas Piggin <npiggin@gmail.com>,
Perry Yuan <perry.yuan@amd.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Sven Peter <sven@svenpeter.dev>,
Viresh Kumar <viresh.kumar@linaro.org>,
WANG Xuerui <kernel@xen0n.name>
Cc: linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
Lifeng Zheng <zhenglifeng1@huawei.com>,
arm-scmi@vger.kernel.org, asahi@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, loongarch@lists.linux.dev
Subject: [PATCH 00/15] cpufreq: simplify boost handling
Date: Fri, 24 Jan 2025 14:28:04 +0530 [thread overview]
Message-ID: <cover.1737707712.git.viresh.kumar@linaro.org> (raw)
Hello,
The boost feature can be controlled at two levels currently, driver
level (applies to all policies) and per-policy.
Currently most of the drivers enables driver level boost support from the
per-policy ->init() callback, which isn't really efficient as that gets called
for each policy and then there is online/offline path too where this gets done
unnecessarily.
Also it is possible to have a scenario where not all cpufreq policies support
boost frequencies. And letting sysfs (or other parts of the kernel) enable boost
feature for that policy isn't correct.
Simplify and cleanup handling of boost to solve these issues.
Pushed here:
git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm.git cpufreq/boost
Rebased over few dependencies from PM tree, will push to the arm-cpufreq tree
after merge window is closed.
Viresh Kumar (15):
cpufreq: staticize cpufreq_boost_trigger_state()
cpufreq: Export cpufreq_boost_set_sw()
cpufreq: Introduce policy->boost_supported flag
cpufreq: acpi: Set policy->boost_supported
cpufreq: amd: Set policy->boost_supported
cpufreq: cppc: Set policy->boost_supported
cpufreq: Restrict enabling boost on policies with no boost frequencies
cpufreq: apple: Set .set_boost directly
cpufreq: loongson: Set .set_boost directly
cpufreq: powernv: Set .set_boost directly
cpufreq: scmi: Set .set_boost directly
cpufreq: dt: Set .set_boost directly
cpufreq: qcom: Set .set_boost directly
cpufreq: staticize policy_has_boost_freq()
cpufreq: Remove cpufreq_enable_boost_support()
drivers/cpufreq/acpi-cpufreq.c | 3 +++
drivers/cpufreq/amd-pstate.c | 4 ++--
drivers/cpufreq/apple-soc-cpufreq.c | 10 +---------
drivers/cpufreq/cppc_cpufreq.c | 9 +--------
drivers/cpufreq/cpufreq-dt.c | 14 +-------------
drivers/cpufreq/cpufreq.c | 30 ++++++++++++-----------------
drivers/cpufreq/freq_table.c | 7 +++++--
drivers/cpufreq/loongson3_cpufreq.c | 10 +---------
drivers/cpufreq/powernv-cpufreq.c | 5 +----
drivers/cpufreq/qcom-cpufreq-hw.c | 7 +------
drivers/cpufreq/scmi-cpufreq.c | 11 +----------
include/linux/cpufreq.h | 20 ++++++-------------
12 files changed, 35 insertions(+), 95 deletions(-)
--
2.31.1.272.g89b43f80a514
next reply other threads:[~2025-01-24 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 8:58 Viresh Kumar [this message]
2025-01-24 8:58 ` [PATCH 10/15] cpufreq: powernv: Set .set_boost directly Viresh Kumar
2025-01-24 11:05 ` [PATCH 00/15] cpufreq: simplify boost handling Rafael J. Wysocki
2025-01-27 3:32 ` Viresh Kumar
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=cover.1737707712.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=alyssa@rosenzweig.io \
--cc=arm-scmi@vger.kernel.org \
--cc=asahi@lists.linux.dev \
--cc=chenhuacai@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=cristian.marussi@arm.com \
--cc=gautham.shenoy@amd.com \
--cc=kernel@xen0n.name \
--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=linuxppc-dev@lists.ozlabs.org \
--cc=loongarch@lists.linux.dev \
--cc=maddy@linux.ibm.com \
--cc=marcan@marcan.st \
--cc=mario.limonciello@amd.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.com \
--cc=perry.yuan@amd.com \
--cc=rafael@kernel.org \
--cc=ray.huang@amd.com \
--cc=sudeep.holla@arm.com \
--cc=sven@svenpeter.dev \
--cc=vincent.guittot@linaro.org \
--cc=zhenglifeng1@huawei.com \
/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).