public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
	Lifeng Zheng <zhenglifeng1@huawei.com>,
	Viresh Kumar <viresh.kumar@linaro.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: [PATCH V2 0/5] cpufreq: Boost related cleanups / fixes
Date: Thu, 24 Apr 2025 21:50:13 +0530	[thread overview]
Message-ID: <cover.1745511526.git.viresh.kumar@linaro.org> (raw)

Hello,

This series tries to fix boost related issues found recently.

The first patch fixes the boost related breakage introduced recently. It should
be applied for v6.15-rc4.

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

V1->V2:
- Drop one patch.
- Fix the commit log of 1/5.
- Add Reviewed-by and Tested-by tags.

Viresh Kumar (5):
  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 | 15 +++++++--
 drivers/cpufreq/cpufreq.c      | 58 ++++++++++++++++++++--------------
 2 files changed, 47 insertions(+), 26 deletions(-)

-- 
2.31.1.272.g89b43f80a514


             reply	other threads:[~2025-04-24 16:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-24 16:20 Viresh Kumar [this message]
2025-04-24 16:20 ` [PATCH V2 1/5] cpufreq: acpi: Re-sync CPU boost state on system resume Viresh Kumar
2025-04-25 16:30   ` Rafael J. Wysocki
2025-04-24 16:20 ` [PATCH V2 2/5] cpufreq: Don't unnecessarily call set_boost() Viresh Kumar
2025-04-24 16:20 ` [PATCH V2 3/5] cpufreq: Introduce policy_set_boost() Viresh Kumar
2025-04-24 16:20 ` [PATCH V2 4/5] cpufreq: Preserve policy's boost state after resume Viresh Kumar
2025-04-24 16:20 ` [PATCH V2 5/5] cpufreq: Force sync policy boost with global boost on sysfs update Viresh Kumar

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=cover.1745511526.git.viresh.kumar@linaro.org \
    --to=viresh.kumar@linaro.org \
    --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=zhenglifeng1@huawei.com \
    /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