[PATCH v3 0/4] cpufreq: Fixes and cleanups related to CPUFREQ_ETERNAL

From: Rafael J. Wysocki
Date: Fri Sep 26 2025 - 06:33:24 EST


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@xxxxxxxx/

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!