From: Lukas Wunner <lukas@wunner.de>
To: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, Ashok Raj <ashok.raj@intel.com>,
Yinghai Lu <yinghai@kernel.org>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Erik Veijola <erik.veijola@linux.intel.com>,
Keith Busch <keith.busch@intel.com>,
Krishna Dhulipala <krishnad@fb.com>, Wei Zhang <wzhang@fb.com>
Subject: [PATCH 0/5] pciehp runtime PM
Date: Mon, 1 May 2017 14:06:39 +0200 [thread overview]
Message-ID: <cover.1493631639.git.lukas@wunner.de> (raw)
Introduce runtime PM to pciehp in a more thorough and comprehensive way
than the reverted 68db9bc81436, taking into account the regressions
reported against it.
@Yinghai Lu & Intel/Facebook engineers, I would be grateful if you
could test this on as many systems as you can get your hands on,
in particular the Skylake servers that were broken by 68db9bc81436.
I guess those were Skylake-SP Xeon systems (Purley platform).
They're still unreleased and not available outside Intel and their
partners. Their release date has been pushed further back to
mid-summer. Myself I've only got a puny, 7 years old "Light Ridge"
Thunderbolt controller to test with and it doesn't even fully adhere
to the PCIe spec.
I'd also be interested to learn if you can measure a drop in power usage
on systems with unoccupied hotplug ports.
I've pushed this series to GitHub to ease reviewing:
https://github.com/l1k/linux/commits/pciehp_runpm_v1
Thanks!
Lukas
Lukas Wunner (5):
PCI: pciehp: Resume to D0 on board addition/removal
PCI: pciehp: Remain in D0 while awaiting command completion
PCI: pciehp: Resume to D0 on sysfs read access
PCI: pciehp: Remain in D0 if poll mode is enabled
PCI: Whitelist native hotplug ports for runtime PM
drivers/pci/hotplug/pciehp_ctrl.c | 13 +++++++++++--
drivers/pci/hotplug/pciehp_hpc.c | 25 ++++++++++++++++++++++---
drivers/pci/pci.c | 7 ++-----
3 files changed, 35 insertions(+), 10 deletions(-)
--
2.11.0
next reply other threads:[~2017-05-01 12:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 12:06 Lukas Wunner [this message]
2017-05-01 12:06 ` [PATCH 5/5] PCI: Whitelist native hotplug ports for runtime PM Lukas Wunner
2017-05-01 12:06 ` [PATCH 3/5] PCI: pciehp: Resume to D0 on sysfs read access Lukas Wunner
2017-05-01 12:06 ` [PATCH 4/5] PCI: pciehp: Remain in D0 if poll mode is enabled Lukas Wunner
2017-05-01 12:06 ` [PATCH 2/5] PCI: pciehp: Remain in D0 while awaiting command completion Lukas Wunner
2017-05-01 12:06 ` [PATCH 1/5] PCI: pciehp: Resume to D0 on board addition/removal Lukas Wunner
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.1493631639.git.lukas@wunner.de \
--to=lukas@wunner.de \
--cc=ashok.raj@intel.com \
--cc=bhelgaas@google.com \
--cc=erik.veijola@linux.intel.com \
--cc=keith.busch@intel.com \
--cc=krishnad@fb.com \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=wzhang@fb.com \
--cc=yinghai@kernel.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).