From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Linux PM <linux-pm@vger.kernel.org>
Cc: Shawn Guo <shawnguo@kernel.org>,
Qais Yousef <qyousef@layalina.io>,
LKML <linux-kernel@vger.kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Prashanth Prakash <pprakash@codeaurora.org>,
Pierre Gondois <pierre.gondois@arm.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Linux ACPI <linux-acpi@vger.kernel.org>
Subject: [PATCH v1 0/4] cpufreq: Fixes and cleanups related to CPUFREQ_ETERNAL
Date: Thu, 25 Sep 2025 17:42:16 +0200 [thread overview]
Message-ID: <8605612.T7Z3S40VBb@rafael.j.wysocki> (raw)
Hi All,
The first patch in this series is meant to address the failure discussed in
https://lore.kernel.org/linux-pm/20250922125929.453444-1-shawnguo2@yeah.net/
but in a different way than proposed by Shawn.
The second one is a CPPC cpufreq driver fix preventing it from using an
overly large transition delay in the cases when that delay cannot be
obtained from the platform firmware.
Patch [3/4] makes CPPC use a specific symbol instead of CPUFREQ_ETERNAL for
signaling error conditions while attempting to retrieve a transition latency
value from the platform firmware.
The last patch removes CPUFREQ_ETERNAL (which has no users any more) from
cpufreq, including all references to it in cpufreq documentation.
Thanks!
next reply other threads:[~2025-09-25 15:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 15:42 Rafael J. Wysocki [this message]
2025-09-25 15:44 ` [PATCH v1 1/4] cpufreq: Make drivers using CPUFREQ_ETERNAL specify transition latency Rafael J. Wysocki
2025-09-25 16:37 ` Mario Limonciello
2025-09-26 9:46 ` Jie Zhan
2025-09-25 15:44 ` [PATCH v1 2/4] cpufreq: CPPC: Avoid using CPUFREQ_ETERNAL as transition delay Rafael J. Wysocki
2025-09-25 16:36 ` Mario Limonciello
2025-09-26 9:41 ` Jie Zhan
2025-09-25 15:46 ` [PATCH v1 3/4] ACPI: CPPC: Replace CPUFREQ_ETERNAL with CPPC-specific symbol Rafael J. Wysocki
2025-09-25 16:35 ` Mario Limonciello
2025-09-25 16:57 ` Rafael J. Wysocki
2025-09-25 17:23 ` [PATCH v2 3/4] ACPI: CPPC: Do not use CPUFREQ_ETERNAL as an error value Rafael J. Wysocki
2025-09-25 18:33 ` Mario Limonciello (AMD) (kernel.org)
2025-09-26 9:30 ` Jie Zhan
2025-09-26 10:22 ` Rafael J. Wysocki
2025-09-25 15:47 ` [PATCH v1 4/4] cpufreq: Drop unused symbol CPUFREQ_ETERNAL Rafael J. Wysocki
2025-09-25 16:36 ` Mario Limonciello (AMD) (kernel.org)
2025-09-26 9:47 ` Jie Zhan
2025-09-29 7:28 ` [PATCH v1 0/4] cpufreq: Fixes and cleanups related to CPUFREQ_ETERNAL 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=8605612.T7Z3S40VBb@rafael.j.wysocki \
--to=rafael@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=pierre.gondois@arm.com \
--cc=pprakash@codeaurora.org \
--cc=qyousef@layalina.io \
--cc=shawnguo@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