mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Wed, 21 Jan 2026 16:37:48 +0800	[thread overview]
Message-ID: <345044bb-15e8-48d3-bc03-d5f327aeb3ae@zhaoxin.com> (raw)
In-Reply-To: <pdp3oabac4g6bakm46w5wj7edl446dqhggdfrlke55gniuju5b@jzodjar7tc2e>



On 2026/1/21 13:51, Viresh Kumar wrote:
> 
> 
> 
> On 20-01-26, 17:24, Tony W Wang-oc wrote:
>> Implemented CPUFREQ_CHANGE_POLICY notification in cpufreq subsystem.
>> This enhancement allows kernel modules to be notified when a CPU frequency
>> policy is modified, facilitating more integrated system management.
>> The notification is dispatched after a successful governor switch during
>> policy updates.
>>
>> Signed-off-by: Tony W Wang-oc <TonyWWang-oc@zhaoxin.com>
>> ---
>>   drivers/cpufreq/cpufreq.c | 2 ++
>>   include/linux/cpufreq.h   | 1 +
>>   2 files changed, 3 insertions(+)
> 
> Who is using this stuff ? Please explain why you need this and how you
> are going to use it. I don't think it is a great idea, but I still
> want to see what you are doing in the first place.
> 

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.

Sincerely!
TonyWWang-oc

  reply	other threads:[~2026-01-21  8:51 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 [this message]
2026-01-21 10:02     ` Viresh Kumar
2026-01-22  2:13       ` Tony W Wang-oc
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=345044bb-15e8-48d3-bc03-d5f327aeb3ae@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®