[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c138c3dc-14ab-4daa-bbed-3cbe5d7c33e4@zhaoxin.com>
Date: Thu, 22 Jan 2026 10:13:29 +0800
From: Tony W Wang-oc <TonyWWang-oc@...oxin.com>
To: Viresh Kumar <viresh.kumar@...aro.org>
CC: <rafael@...nel.org>, <linux-pm@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <CobeChen@...oxin.com>, <TimGuo@...oxin.com>,
<LeoLiu-oc@...oxin.com>, <LindaChai@...oxin.com>
Subject: Re: [PATCH] cpufreq: Add CPU frequency policy change notification
support
On 2026/1/21 18:02, Viresh Kumar wrote:
>
>
> On 21-01-26, 16:37, Tony W Wang-oc wrote:
>> The expectation is to register a notifier of type CPUFREQ_POLICY_NOTIFIER
>> via cpufreq_register_notifier in one of our drivers. The notifier callback
>> will configure Zhaoxin registers to different values based on the different
>> cpufreq governors when the event is CPUFREQ_GOVERNOR_CHANGE, thereby
>> allowing the Zhaoxin hardware to adopt different power management
>> strategies.
>
> Firstly, for this change to be acceptable, we would need your upstream
> platform specific changes as well.
>
> And then I am still not sure if this it the right way to solve this
> problem.
>
The driver for Zhaoxin using this patch still needs further verification
on actual platforms; it cannot yet be submitted to the mainline.
However, we have already verified that this patch itself has no issues
with Zhaoxin's driver.
From the perspective of this patch itself, we think it provides the
capability to perceive changes in cpufreq policy for all modules
concerned, and it can serve not just this Zhaoxin driver.
Sincerely
TonyWWang-oc
Powered by blists - more mailing lists