From: Heiner Kallweit <hkallweit1@gmail.com>
To: Frederick Lawler <fred@fredlawl.com>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: [PATCH 0/3] PCI/ASPM: add sysfs attribute for controlling ASPM
Date: Thu, 23 May 2019 22:03:13 +0200 [thread overview]
Message-ID: <7a6d2f14-f2a6-99ad-3a93-fdaa0726ce86@gmail.com> (raw)
Background of this extension is a problem with the r8169 network driver.
Several combinations of board chipsets and network chip versions have
problems if ASPM is enabled, therefore we have to disable ASPM per
default. However especially on notebooks ASPM can provide significant
power-saving, therefore we want to give users the option to enable
ASPM. With the new sysfs attribute users can control which ASPM
link-states are disabled.
After few RFC's this is the submission-ready version. Added to the RFC
version has been documentation of the new sysfs attribute.
Heiner Kallweit (3):
PCI/ASPM: add L1 sub-state support to pci_disable_link_state
PCI/ASPM: allow to re-enable Clock PM
PCI/ASPM: add sysfs attribute for controlling ASPM
Documentation/ABI/testing/sysfs-bus-pci | 13 ++
drivers/pci/pci.h | 8 +-
drivers/pci/pcie/aspm.c | 211 ++++++++++++++++++++++--
include/linux/pci-aspm.h | 8 +-
4 files changed, 219 insertions(+), 21 deletions(-)
--
2.21.0
next reply other threads:[~2019-05-23 20:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 20:03 Heiner Kallweit [this message]
2019-05-23 20:03 ` [PATCH 1/3] PCI/ASPM: add L1 sub-state support to pci_disable_link_state Heiner Kallweit
2019-05-23 20:04 ` [PATCH 2/3] PCI/ASPM: allow to re-enable Clock PM Heiner Kallweit
2019-05-23 20:05 ` [PATCH 3/3] PCI/ASPM: add sysfs attribute for controlling ASPM Heiner Kallweit
2019-08-20 10:34 ` Bjorn Helgaas
2019-08-20 17:05 ` Greg KH
2019-08-20 19:05 ` Rajat Jain
2019-08-20 19:32 ` Bjorn Helgaas
2019-08-20 19:51 ` Rajat Jain
2019-08-20 20:48 ` Bjorn Helgaas
2019-08-20 20:55 ` Rajat Jain
2019-07-01 20:07 ` [PATCH 0/3] " Heiner Kallweit
2019-07-10 6:59 ` AceLan Kao
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=7a6d2f14-f2a6-99ad-3a93-fdaa0726ce86@gmail.com \
--to=hkallweit1@gmail.com \
--cc=bhelgaas@google.com \
--cc=fred@fredlawl.com \
--cc=linux-pci@vger.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).