mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "zhenglifeng (A)" <zhenglifeng1@huawei.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>
Cc: <linux-pm@vger.kernel.org>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Nicholas Chin <nic.c3.14@gmail.com>,
	<linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH 0/6] cpufreq: Boost related cleanups / fixes
Date: Tue, 22 Apr 2025 20:33:00 +0800	[thread overview]
Message-ID: <93b0a8ad-8de7-4a17-a908-4ef0eb316e1f@huawei.com> (raw)
In-Reply-To: <cover.1745315548.git.viresh.kumar@linaro.org>

On 2025/4/22 17:53, Viresh Kumar wrote:

> Hello,
> 
> This series tries to fix boost related issues found recently.
> 
> The first two patches (hopefully) fixes the boost related breakage
> introduced recently. These should be applied for v6.15-rc4. Nicholas,
> please give the first two patches a try.
> 
> The other four patches are general optimizations and fixes for boost
> handling in general. These can be applied to -rc or next merge window.
> 
> --
> Viresh
> 
> Viresh Kumar (6):
>   cpufreq: acpi: Don't enable boost on policy exit
>   cpufreq: acpi: Re-sync CPU boost state on system resume
>   cpufreq: Don't unnecessarily call set_boost()
>   cpufreq: Introduce policy_set_boost()
>   cpufreq: Preserve policy's boost state after resume
>   cpufreq: Force sync policy boost with global boost on sysfs update
> 
>  drivers/cpufreq/acpi-cpufreq.c | 38 ++++++++++------------
>  drivers/cpufreq/cpufreq.c      | 58 ++++++++++++++++++++--------------
>  2 files changed, 50 insertions(+), 46 deletions(-)
> 

Reviewed-by: Lifeng Zheng <zhenglifeng1@huawei.com>

      parent reply	other threads:[~2025-04-22 12:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22  9:53 Viresh Kumar
2025-04-22  9:53 ` [PATCH 1/6] cpufreq: acpi: Don't enable boost on policy exit Viresh Kumar
2025-04-23  2:56   ` Nicholas Chin
2025-04-23 14:14   ` Rafael J. Wysocki
2025-04-24  7:15     ` Viresh Kumar
2025-04-24 11:26       ` Rafael J. Wysocki
2025-04-24 13:15         ` zhenglifeng (A)
2025-04-24 15:50         ` Viresh Kumar
2025-04-22  9:53 ` [PATCH 2/6] cpufreq: acpi: Re-sync CPU boost state on system resume Viresh Kumar
2025-04-23  2:57   ` Nicholas Chin
2025-04-23 14:26   ` Rafael J. Wysocki
2025-04-23 14:40     ` Rafael J. Wysocki
2025-04-23 14:59       ` Rafael J. Wysocki
2025-04-24  7:27         ` Viresh Kumar
2025-04-24 11:27           ` Rafael J. Wysocki
2025-04-22  9:53 ` [PATCH 3/6] cpufreq: Don't unnecessarily call set_boost() Viresh Kumar
2025-04-22  9:53 ` [PATCH 4/6] cpufreq: Introduce policy_set_boost() Viresh Kumar
2025-04-22  9:53 ` [PATCH 5/6] cpufreq: Preserve policy's boost state after resume Viresh Kumar
2025-04-22  9:53 ` [PATCH 6/6] cpufreq: Force sync policy boost with global boost on sysfs update Viresh Kumar
2025-04-22 12:33 ` zhenglifeng (A) [this message]

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=93b0a8ad-8de7-4a17-a908-4ef0eb316e1f@huawei.com \
    --to=zhenglifeng1@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nic.c3.14@gmail.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rafael@kernel.org \
    --cc=vincent.guittot@linaro.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®