[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250929072852.2krpxwaq2uxwj6cp@vireshk-i7>
Date: Mon, 29 Sep 2025 12:58:52 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: "Rafael J. Wysocki" <rafael@...nel.org>
Cc: Linux PM <linux-pm@...r.kernel.org>, Shawn Guo <shawnguo@...nel.org>,
Qais Yousef <qyousef@...alina.io>,
LKML <linux-kernel@...r.kernel.org>,
Prashanth Prakash <pprakash@...eaurora.org>,
Pierre Gondois <pierre.gondois@....com>,
Mario Limonciello <mario.limonciello@....com>,
Linux ACPI <linux-acpi@...r.kernel.org>
Subject: Re: [PATCH v1 0/4] cpufreq: Fixes and cleanups related to
CPUFREQ_ETERNAL
On 25-09-25, 17:42, Rafael J. Wysocki wrote:
> 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.
Acked-by: Viresh Kumar <viresh.kumar@...aro.org>
--
viresh
Powered by blists - more mailing lists