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>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Power management fixes for v5.10-rc5
Date: Thu, 19 Nov 2020 19:27:00 +0100	[thread overview]
Message-ID: <CAJZ5v0jBUToP9sxeuhw_AVwoPNc8RwJD_31WoCLSOiXH6Dcy8A@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.10-rc5

with top-most commit 3a8ac4d39651c71d6d2f3376b13d0bad1484249a

 Merge branch 'pm-cpuidle'

on top of commit 09162bc32c880a791c6c0668ce0745cf7958f576

 Linux 5.10-rc4

to receive power management fixes for 5.10-rc5.

These fix two issues in ARM cpufreq drivers and one cpuidle
driver issue.

Specifics:

 - Add missing RCU_NONIDLE() annotations to the Tegra cpuidle
   driver (Dmitry Osipenko).

 - Fix boot frequency computation in the tegra186 cpufreq driver (Jon
   Hunter).

 - Make the SCMI cpufreq driver register a dummy clock provider to
   avoid OPP addition failures (Sudeep Holla).

Thanks!


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

Dmitry Osipenko (1):
      cpuidle: tegra: Annotate tegra_pm_set_cpu_in_lp2() with RCU_NONIDLE

Jon Hunter (1):
      cpufreq: tegra186: Fix get frequency callback

Sudeep Holla (1):
      cpufreq: scmi: Fix OPP addition failure with a dummy clock provider

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

 drivers/cpufreq/scmi-cpufreq.c     |  6 ++++++
 drivers/cpufreq/tegra186-cpufreq.c | 33 +++++++++++++++++++++------------
 drivers/cpuidle/cpuidle-tegra.c    |  4 ++--
 3 files changed, 29 insertions(+), 14 deletions(-)

             reply	other threads:[~2020-11-19 18:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19 18:27 Rafael J. Wysocki [this message]
2020-11-19 19:17 ` [GIT PULL] Power management fixes for v5.10-rc5 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=CAJZ5v0jBUToP9sxeuhw_AVwoPNc8RwJD_31WoCLSOiXH6Dcy8A@mail.gmail.com \
    --to=rafael@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.