linux-kernel.vger.kernel.org archive mirror
 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.9-rc1
Date: Fri, 7 Aug 2020 20:06:01 +0200	[thread overview]
Message-ID: <CAJZ5v0hQS_aVFJpqJ2uPxpomKpyb3iM0fVUTg5oP-5AG=qwGsA@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.9-rc1-2

with top-most commit 0873ad923a05751a29a92229739ce2737c29d348

 Merge branch 'pm-core'

on top of commit 04084978003c1a1810a0b1fea581078106394a32

 Merge tag 'pm-5.9-rc1' of
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm

to receive more power management updates for 5.9-rc1.

These are mostly ARM cpufreq driver updates plus a cpufreq core
cleanup, an ARM-wide change to make schedutil the default scaling
governor, an intel_pstate driver fix and some runtime PM changes
regarding kerneldoc comments.

Specifics:

 - Add adaptive voltage scaling (AVS) support to the brcmstb cpufreq
   driver and clean it up (Florian Fainelli, Markus Mayer).

 - Add a new Tegra cpufreq driver and clean up the existing one (Jon
   Hunter, Sumit Gupta).

 - Add bandwidth level support to the Qcom cpufreq driver along with
   OPP changes (Sibi Sankar).

 - Clean up the sti, cpufreq-dt, ap806, CPPC cpufreq drivers (Viresh
   Kumar, Lee Jones, Ivan Kokshaysky, Sven Auhagen, Xin Hao).

 - Make schedutil the default governor for ARM (Valentin Schneider).

 - Fix dependency issues for the imx cpufreq driver (Walter Lozano).

 - Clean up cached_resolved_idx handlihng in the cpufreq core (Viresh
   Kumar).

 - Fix the intel_pstate driver to use the correct maximum frequency
   value when MSR_TURBO_RATIO_LIMIT is 0 (Srinivas Pandruvada).

 - Provide kenrneldoc comments for multiple runtime PM helpers and
   improve the pm_runtime_get_if_active() kerneldoc (Rafael Wysocki).

Thanks!


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

Florian Fainelli (1):
      cpufreq: brcmstb-avs-cpufreq: Support polling AVS firmware

Ivan Kokshaysky (1):
      cpufreq: dt: fix oops on armada37xx

Jon Hunter (1):
      cpufreq: tegra186: Simplify probe return path

Lee Jones (1):
      cpufreq: sti-cpufreq: Fix some formatting and misspelling issues

Markus Mayer (2):
      cpufreq: brcmstb-avs-cpufreq: more flexible interface for
__issue_avs_command()
      cpufreq: brcmstb-avs-cpufreq: send S2_ENTER / S2_EXIT commands to AVS

Rafael J. Wysocki (2):
      PM: runtime: Add kerneldoc comments to multiple helpers
      PM: runtime: Improve kerneldoc of pm_runtime_get_if_active()

Sibi Sankar (5):
      cpufreq: blacklist SDM845 in cpufreq-dt-platdev
      cpufreq: blacklist SC7180 in cpufreq-dt-platdev
      OPP: Add and export helper to set bandwidth
      cpufreq: qcom: Update the bandwidth levels on frequency change
      cpufreq: qcom: Disable fast switch when scaling DDR/L3

Srinivas Pandruvada (1):
      cpufreq: intel_pstate: Fix cpuinfo_max_freq when
MSR_TURBO_RATIO_LIMIT is 0

Sumit Gupta (2):
      dt-bindings: arm: Add NVIDIA Tegra194 CPU Complex binding
      cpufreq: Add Tegra194 cpufreq driver

Sven Auhagen (1):
      cpufreq: ap806: fix cpufreq driver needs ap cpu clk

Valentin Schneider (1):
      cpufreq: make schedutil the default for arm and arm64

Viresh Kumar (2):
      cpufreq: cppc: Reorder code and remove apply_hisi_workaround variable
      cpufreq: cached_resolved_idx can not be negative

Walter Lozano (1):
      cpufreq: imx: Select NVMEM_IMX_OCOTP

Xin Hao (1):
      cpufreq: CPPC: Reuse caps variable in few routines

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

 .../bindings/arm/nvidia,tegra194-ccplex.yaml       |  69 ++++
 drivers/base/power/runtime.c                       |  26 +-
 drivers/cpufreq/Kconfig                            |   2 +-
 drivers/cpufreq/Kconfig.arm                        |   9 +
 drivers/cpufreq/Makefile                           |   1 +
 drivers/cpufreq/armada-37xx-cpufreq.c              |   1 +
 drivers/cpufreq/brcmstb-avs-cpufreq.c              |  89 +++--
 drivers/cpufreq/cppc_cpufreq.c                     |  95 +++--
 drivers/cpufreq/cpufreq-dt-platdev.c               |   2 +
 drivers/cpufreq/cpufreq.c                          |   2 +-
 drivers/cpufreq/intel_pstate.c                     |   1 +
 drivers/cpufreq/qcom-cpufreq-hw.c                  |  91 ++++-
 drivers/cpufreq/sti-cpufreq.c                      |   8 +-
 drivers/cpufreq/tegra186-cpufreq.c                 |   6 -
 drivers/cpufreq/tegra194-cpufreq.c                 | 390 +++++++++++++++++++++
 drivers/opp/core.c                                 |  31 ++
 include/linux/cpufreq.h                            |   2 +-
 include/linux/pm_opp.h                             |   6 +
 include/linux/pm_runtime.h                         | 246 +++++++++++++
 19 files changed, 963 insertions(+), 114 deletions(-)

             reply	other threads:[~2020-08-07 18:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-07 18:06 Rafael J. Wysocki [this message]
2020-08-07 20:39 ` [GIT PULL] More power management updates for v5.9-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='CAJZ5v0hQS_aVFJpqJ2uPxpomKpyb3iM0fVUTg5oP-5AG=qwGsA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).