All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux PM <linux-pm@vger.kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] More power management updates for v5.12-rc1
Date: Tue, 23 Feb 2021 21:05:26 +0100	[thread overview]
Message-ID: <CAJZ5v0gOvJ4OXK2Sqt6ncm-G0BVeC1Aiuettd02E=7wq73g=oA@mail.gmail.com> (raw)

Hi Linus,

Please pull from the tag

 git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
 pm-5.12-rc1-2

with top-most commit 08c2a406b974eea893dd9b2f159d715f2b15c683

 Merge branches 'pm-cpufreq' and 'pm-opp'

on top of commit a9a939cb34dfffb9f43b988a681d2566ca157b74

 Merge branches 'powercap' and 'pm-misc'

to receive more power management updates for 5.12-rc1.

These are fixes and cleanups on top of the power management
material for 5.12-rc1 merged previously.

Specifics:

 - Address cpufreq regression introduced in 5.11 that causes
   CPU frequency reporting to be distorted on systems with CPPC
   that use acpi-cpufreq as the scaling driver (Rafael Wysocki).

 - Fix regression introduced during the 5.10 development cycle
   related to CPU hotplug and policy recreation in the
   qcom-cpufreq-hw driver (Shawn Guo).

 - Fix recent regression in the operating performance points (OPP)
   framework that may cause frequency updates to be skipped by
   mistake in some cases (Jonathan Marek).

 - Simplify schedutil governor code and remove a misleading comment
   from it (Yue Hu).

 - Fix kerneldoc comment typo in the cpufreq core (Yue Hu).

Thanks!


---------------

Jonathan Marek (1):
      opp: Don't skip freq update for different frequency

Rafael J. Wysocki (1):
      cpufreq: ACPI: Set cpuinfo.max_freq directly if max boost is known

Shawn Guo (1):
      cpufreq: qcom-hw: drop devm_xxx() calls from init/exit hooks

Yue Hu (3):
      cpufreq: schedutil: Remove needless sg_policy parameter from
ignore_dl_rate_limit()
      cpufreq: schedutil: Remove update_lock comment from struct
sugov_policy definition
      cpufreq: Fix typo in kerneldoc comment

---------------

 drivers/cpufreq/acpi-cpufreq.c    | 62 ++++++++++-----------------------------
 drivers/cpufreq/cpufreq.c         |  2 +-
 drivers/cpufreq/freq_table.c      |  8 ++++-
 drivers/cpufreq/qcom-cpufreq-hw.c | 40 ++++++++++++++++++++-----
 drivers/opp/core.c                |  8 +++--
 drivers/opp/opp.h                 |  2 ++
 kernel/sched/cpufreq_schedutil.c  | 14 ++++-----
 7 files changed, 69 insertions(+), 67 deletions(-)

             reply	other threads:[~2021-02-23 20:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 20:05 Rafael J. Wysocki [this message]
2021-02-23 23:36 ` [GIT PULL] More power management updates for v5.12-rc1 pr-tracker-bot

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='CAJZ5v0gOvJ4OXK2Sqt6ncm-G0BVeC1Aiuettd02E=7wq73g=oA@mail.gmail.com' \
    --to=rafael@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.