Linux Power Management development
 help / color / mirror / Atom feed
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>,
	Pierre Gondois <pierre.gondois@arm.com>,
	Mario Limonciello <mario.limonciello@amd.com>,
	Linux ACPI <linux-acpi@vger.kernel.org>
Subject: [PATCH v3 0/4] cpufreq: Fixes and cleanups related to CPUFREQ_ETERNAL
Date: Fri, 26 Sep 2025 12:04:57 +0200	[thread overview]
Message-ID: <5069803.31r3eYUQgx@rafael.j.wysocki> (raw)

Hi All,

This is an update of

https://lore.kernel.org/linux-pm/8605612.T7Z3S40VBb@rafael.j.wysocki/

The update is due because of some changes in the first patch (involving Rust)
and in the second patch (function rename).  It is v3 because a v2 of the
third patch was sent after the v1.

The original cover letter quoted below still applies:

 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!




             reply	other threads:[~2025-09-26 10:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-26 10:04 Rafael J. Wysocki [this message]
2025-09-26 10:12 ` [PATCH v3 1/4] cpufreq: Make drivers using CPUFREQ_ETERNAL specify transition latency Rafael J. Wysocki
2025-09-28  3:23   ` Shawn Guo
2025-09-28 10:00     ` Rafael J. Wysocki
2025-09-29  3:14       ` Shawn Guo
2025-10-01 10:38   ` Qais Yousef
2025-09-26 10:19 ` [PATCH v3 2/4] cpufreq: CPPC: Avoid using CPUFREQ_ETERNAL as transition delay Rafael J. Wysocki
2025-09-28  1:59   ` Jie Zhan
2025-09-26 10:29 ` [PATCH v3 3/4] ACPI: CPPC: Do not use CPUFREQ_ETERNAL as an error value Rafael J. Wysocki
2025-09-26 10:31 ` [PATCH v3 4/4] cpufreq: Drop unused symbol CPUFREQ_ETERNAL 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=5069803.31r3eYUQgx@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=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