From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Naveen N Rao <naveen@kernel.org>
Cc: linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH V1.1 20/33] cpufreq: powernv: Stop setting common freq attributes
Date: Mon, 3 Feb 2025 15:23:32 +0530 [thread overview]
Message-ID: <fa304da30d5f10e7ff069d72fb3aff2741630ca4.1738576306.git.viresh.kumar@linaro.org> (raw)
In-Reply-To: <1f5393d54b2c04206afefd521ebdf3fc03004a11.1737631669.git.viresh.kumar@linaro.org>
The cpufreq core handles this now, the driver can skip setting it.
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Acked-by: Rafael J. Wysocki <rafael@kernel.org>
---
V1.1:
- Drop runtime updates to freq attr.
drivers/cpufreq/powernv-cpufreq.c | 6 ------
1 file changed, 6 deletions(-)
diff --git a/drivers/cpufreq/powernv-cpufreq.c b/drivers/cpufreq/powernv-cpufreq.c
index ae79d909943b..0631284c4cfb 100644
--- a/drivers/cpufreq/powernv-cpufreq.c
+++ b/drivers/cpufreq/powernv-cpufreq.c
@@ -386,12 +386,8 @@ static ssize_t cpuinfo_nominal_freq_show(struct cpufreq_policy *policy,
static struct freq_attr cpufreq_freq_attr_cpuinfo_nominal_freq =
__ATTR_RO(cpuinfo_nominal_freq);
-#define SCALING_BOOST_FREQS_ATTR_INDEX 2
-
static struct freq_attr *powernv_cpu_freq_attr[] = {
- &cpufreq_freq_attr_scaling_available_freqs,
&cpufreq_freq_attr_cpuinfo_nominal_freq,
- &cpufreq_freq_attr_scaling_boost_freqs,
NULL,
};
@@ -1129,8 +1125,6 @@ static int __init powernv_cpufreq_init(void)
if (powernv_pstate_info.wof_enabled)
powernv_cpufreq_driver.boost_enabled = true;
- else
- powernv_cpu_freq_attr[SCALING_BOOST_FREQS_ATTR_INDEX] = NULL;
rc = cpufreq_register_driver(&powernv_cpufreq_driver);
if (rc) {
--
2.31.1.272.g89b43f80a514
next prev parent reply other threads:[~2025-02-03 9:53 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 11:35 [PATCH 00/33] cpufreq: manage common sysfs attributes from core Viresh Kumar
2025-01-23 11:35 ` [PATCH 01/33] cpufreq: Always create freq-table related sysfs file Viresh Kumar
2025-01-23 19:39 ` Rafael J. Wysocki
2025-01-23 11:35 ` [PATCH 02/33] cpufreq: dt: Stop setting cpufreq_driver->attr field Viresh Kumar
2025-01-23 11:35 ` [PATCH 03/33] cpufreq: acpi: Stop setting common freq attributes Viresh Kumar
2025-01-23 11:35 ` [PATCH 04/33] cpufreq: apple: Stop setting cpufreq_driver->attr field Viresh Kumar
2025-01-23 11:35 ` [PATCH 05/33] cpufreq: bmips: " Viresh Kumar
2025-01-23 20:27 ` Florian Fainelli
2025-01-23 11:35 ` [PATCH 06/33] cpufreq: brcmstb: Stop setting common freq attributes Viresh Kumar
2025-01-23 20:27 ` Florian Fainelli
2025-01-23 11:35 ` [PATCH 07/33] cpufreq: davinci: Stop setting cpufreq_driver->attr field Viresh Kumar
2025-01-23 11:35 ` [PATCH 08/33] cpufreq: e_powersaver: " Viresh Kumar
2025-01-23 11:35 ` [PATCH 09/33] cpufreq: elanfreq: " Viresh Kumar
2025-01-23 11:35 ` [PATCH 10/33] cpufreq: imx6q: " Viresh Kumar
2025-01-23 11:35 ` [PATCH 11/33] cpufreq: kirkwood: " Viresh Kumar
2025-01-23 11:35 ` [PATCH 12/33] cpufreq: longhaul: " Viresh Kumar
2025-01-23 11:35 ` [PATCH 13/33] cpufreq: loongson: " Viresh Kumar
2025-01-23 11:35 ` [PATCH 14/33] cpufreq: mediatek: " Viresh Kumar
2025-01-23 11:35 ` [PATCH 15/33] cpufreq: omap: " Viresh Kumar
2025-01-23 11:35 ` [PATCH 16/33] cpufreq: p4: " Viresh Kumar
2025-01-23 11:35 ` [PATCH 17/33] cpufreq: pasemi: " Viresh Kumar
2025-01-23 11:35 ` [PATCH 18/33] cpufreq: pmac: " Viresh Kumar
2025-01-23 11:35 ` [PATCH 19/33] cpufreq: powernow: " Viresh Kumar
2025-01-23 11:35 ` [PATCH 20/33] cpufreq: powernv: Stop setting common freq attributes Viresh Kumar
2025-02-03 9:53 ` Viresh Kumar [this message]
2025-01-23 11:35 ` [PATCH 21/33] cpufreq: qcom: Stop setting cpufreq_driver->attr field Viresh Kumar
2025-01-23 11:35 ` [PATCH 22/33] cpufreq: qoriq: " Viresh Kumar
2025-01-23 11:35 ` [PATCH 23/33] cpufreq: sc520_freq: " Viresh Kumar
2025-01-23 11:36 ` [PATCH 24/33] cpufreq: scmi: " Viresh Kumar
2025-01-23 12:01 ` Sudeep Holla
2025-01-24 3:37 ` Viresh Kumar
2025-01-23 11:36 ` [PATCH 25/33] cpufreq: scpi: " Viresh Kumar
2025-01-23 11:52 ` Sudeep Holla
2025-01-23 11:36 ` [PATCH 26/33] cpufreq: sh: " Viresh Kumar
2025-01-23 11:36 ` [PATCH 27/33] cpufreq: spear: " Viresh Kumar
2025-01-23 11:36 ` [PATCH 28/33] cpufreq: speedstep: " Viresh Kumar
2025-01-23 11:36 ` [PATCH 29/33] cpufreq: tegra: " Viresh Kumar
2025-01-23 11:36 ` [PATCH 30/33] cpufreq: vexpress: " Viresh Kumar
2025-01-23 11:50 ` Sudeep Holla
2025-01-23 11:36 ` [PATCH 31/33] cpufreq: virtual: " Viresh Kumar
2025-01-23 11:36 ` [PATCH 32/33] cpufreq: Remove cpufreq_generic_attrs Viresh Kumar
2025-01-23 11:36 ` [PATCH 33/33] cpufreq: Stop checking for duplicate available/boost freq attributes Viresh Kumar
2025-01-23 19:40 ` [PATCH 00/33] cpufreq: manage common sysfs attributes from core Rafael J. Wysocki
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=fa304da30d5f10e7ff069d72fb3aff2741630ca4.1738576306.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.com \
--cc=rafael@kernel.org \
--cc=vincent.guittot@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
all inboxes | Powered by JetHome®