From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux PM <linux-pm@vger.kernel.org>,
Linux PCI <linux-pci@vger.kernel.org>,
linux-nvme <linux-nvme@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Power management fixes for v5.3-rc5
Date: Fri, 16 Aug 2019 15:11:27 +0200 [thread overview]
Message-ID: <CAJZ5v0j4ezEuK1dk0J3wwjSuudzjhKWTXzJL=EkE1QG39HKRiw@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.3-rc5
with top-most commit a3ee2477c45f73184a64d9c6cf97855a52732dc6
Merge branch 'pm-cpufreq'
on top of commit d45331b00ddb179e291766617259261c112db872
Linux 5.3-rc4
to receive power management fixes for 5.3-rc5.
These add a check to avoid recent suspend-to-idle power regression on
systems with NVMe drives where the PCIe ASPM policy is "performance"
(or when the kernel is built without ASPM support), fix an issue
related to frequency limits in the schedutil cpufreq governor and fix a
mistake related to the PM QoS usage in the cpufreq core introduced
recently.
Specifics:
- Disable NVMe power optimization related to suspend-to-idle added
recently on systems where PCIe ASPM is not able to put PCIe links
into low-power states to prevent excess power from being drawn by
the system while suspended (Rafael Wysocki).
- Make the schedutil cpufreq governor handle frequency limits changes
properly in all cases (Viresh Kumar).
- Prevent the cpufreq core from treating positive values returned
by dev_pm_qos_update_request() as errors (Viresh Kumar).
Thanks!
---------------
Rafael J. Wysocki (2):
PCI/ASPM: Add pcie_aspm_enabled()
nvme-pci: Allow PCI bus-level PM to be used if ASPM is disabled
Viresh Kumar (2):
cpufreq: dev_pm_qos_update_request() can return 1 on success
cpufreq: schedutil: Don't skip freq update when limits change
---------------
drivers/cpufreq/cpufreq.c | 2 +-
drivers/nvme/host/pci.c | 13 ++++++++++---
drivers/pci/pcie/aspm.c | 20 ++++++++++++++++++++
include/linux/pci.h | 2 ++
kernel/sched/cpufreq_schedutil.c | 14 ++++++++++----
5 files changed, 43 insertions(+), 8 deletions(-)
next reply other threads:[~2019-08-16 13:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 13:11 Rafael J. Wysocki [this message]
2019-08-16 16:30 ` [GIT PULL] Power management fixes for v5.3-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='CAJZ5v0j4ezEuK1dk0J3wwjSuudzjhKWTXzJL=EkE1QG39HKRiw@mail.gmail.com' \
--to=rafael@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci@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).