From: "Mario Limonciello (AMD) (kernel.org)" <superm1@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
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>,
Linux ACPI <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH v1 4/4] cpufreq: Drop unused symbol CPUFREQ_ETERNAL
Date: Thu, 25 Sep 2025 11:36:20 -0500 [thread overview]
Message-ID: <4067f542-d0d1-4055-b5ee-a468dd7eb559@kernel.org> (raw)
In-Reply-To: <9533136.CDJkKcVGEf@rafael.j.wysocki>
On 9/25/2025 10:47 AM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> Drop CPUFREQ_ETERNAL that has no users any more along with all
> references to it in the documentation.
>
> No functional impact.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>> ---
> Documentation/admin-guide/pm/cpufreq.rst | 4 ----
> Documentation/cpu-freq/cpu-drivers.rst | 3 +--
> Documentation/translations/zh_CN/cpu-freq/cpu-drivers.rst | 3 +--
> Documentation/translations/zh_TW/cpu-freq/cpu-drivers.rst | 3 +--
> include/linux/cpufreq.h | 5 -----
> 5 files changed, 3 insertions(+), 15 deletions(-)
>
> --- a/Documentation/admin-guide/pm/cpufreq.rst
> +++ b/Documentation/admin-guide/pm/cpufreq.rst
> @@ -274,10 +274,6 @@ are the following:
> The time it takes to switch the CPUs belonging to this policy from one
> P-state to another, in nanoseconds.
>
> - If unknown or if known to be so high that the scaling driver does not
> - work with the `ondemand`_ governor, -1 (:c:macro:`CPUFREQ_ETERNAL`)
> - will be returned by reads from this attribute.
> -
> ``related_cpus``
> List of all (online and offline) CPUs belonging to this policy.
>
> --- a/Documentation/cpu-freq/cpu-drivers.rst
> +++ b/Documentation/cpu-freq/cpu-drivers.rst
> @@ -109,8 +109,7 @@ Then, the driver must fill in the follow
> +-----------------------------------+--------------------------------------+
> |policy->cpuinfo.transition_latency | the time it takes on this CPU to |
> | | switch between two frequencies in |
> -| | nanoseconds (if appropriate, else |
> -| | specify CPUFREQ_ETERNAL) |
> +| | nanoseconds |
> +-----------------------------------+--------------------------------------+
> |policy->cur | The current operating frequency of |
> | | this CPU (if appropriate) |
> --- a/Documentation/translations/zh_CN/cpu-freq/cpu-drivers.rst
> +++ b/Documentation/translations/zh_CN/cpu-freq/cpu-drivers.rst
> @@ -112,8 +112,7 @@ CPUfreq核心层注册一个cpufreq_driv
> | | |
> +-----------------------------------+--------------------------------------+
> |policy->cpuinfo.transition_latency | CPU在两个频率之间切换所需的时间,以 |
> -| | 纳秒为单位(如不适用,设定为 |
> -| | CPUFREQ_ETERNAL) |
> +| | 纳秒为单位 |
> | | |
> +-----------------------------------+--------------------------------------+
> |policy->cur | 该CPU当前的工作频率(如适用) |
> --- a/Documentation/translations/zh_TW/cpu-freq/cpu-drivers.rst
> +++ b/Documentation/translations/zh_TW/cpu-freq/cpu-drivers.rst
> @@ -112,8 +112,7 @@ CPUfreq核心層註冊一個cpufreq_driv
> | | |
> +-----------------------------------+--------------------------------------+
> |policy->cpuinfo.transition_latency | CPU在兩個頻率之間切換所需的時間,以 |
> -| | 納秒爲單位(如不適用,設定爲 |
> -| | CPUFREQ_ETERNAL) |
> +| | 納秒爲單位 |
> | | |
> +-----------------------------------+--------------------------------------+
> |policy->cur | 該CPU當前的工作頻率(如適用) |
> --- a/include/linux/cpufreq.h
> +++ b/include/linux/cpufreq.h
> @@ -26,13 +26,8 @@
> *********************************************************************/
> /*
> * Frequency values here are CPU kHz
> - *
> - * Maximum transition latency is in nanoseconds - if it's unknown,
> - * CPUFREQ_ETERNAL shall be used.
> */
>
> -#define CPUFREQ_ETERNAL (-1)
> -
> #define CPUFREQ_DEFAULT_TANSITION_LATENCY_NS NSEC_PER_MSEC
>
> #define CPUFREQ_NAME_LEN 16
>
>
>
next prev parent reply other threads:[~2025-09-25 16:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 15:42 [PATCH v1 0/4] cpufreq: Fixes and cleanups related to CPUFREQ_ETERNAL Rafael J. Wysocki
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) [this message]
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=4067f542-d0d1-4055-b5ee-a468dd7eb559@kernel.org \
--to=superm1@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pierre.gondois@arm.com \
--cc=pprakash@codeaurora.org \
--cc=qyousef@layalina.io \
--cc=rafael@kernel.org \
--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