From: Tony W Wang-oc <TonyWWang-oc@zhaoxin.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: <rafael@kernel.org>, <linux-pm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <CobeChen@zhaoxin.com>,
<TimGuo@zhaoxin.com>, <LeoLiu-oc@zhaoxin.com>,
<LindaChai@zhaoxin.com>
Subject: Re: [PATCH] cpufreq: Add CPU frequency policy change notification support
Date: Thu, 22 Jan 2026 10:13:29 +0800 [thread overview]
Message-ID: <c138c3dc-14ab-4daa-bbed-3cbe5d7c33e4@zhaoxin.com> (raw)
In-Reply-To: <qlcwa27dujkhxdyeminfzc3435xdz6z7bc627hd4fukr5qbhiw@anrsyspxw4mz>
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
next prev parent reply other threads:[~2026-01-22 2:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 9:24 Tony W Wang-oc
2026-01-21 5:51 ` Viresh Kumar
2026-01-21 8:37 ` Tony W Wang-oc
2026-01-21 10:02 ` Viresh Kumar
2026-01-22 2:13 ` Tony W Wang-oc [this message]
2026-01-22 5:26 ` Viresh Kumar
2026-01-22 7:41 ` Tony W Wang-oc
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=c138c3dc-14ab-4daa-bbed-3cbe5d7c33e4@zhaoxin.com \
--to=tonywwang-oc@zhaoxin.com \
--cc=CobeChen@zhaoxin.com \
--cc=LeoLiu-oc@zhaoxin.com \
--cc=LindaChai@zhaoxin.com \
--cc=TimGuo@zhaoxin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@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
all inboxes | Powered by JetHome®