From: Heiner Kallweit <hkallweit1@gmail.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Frederick Lawler <fred@fredlawl.com>,
Greg KH <gregkh@linuxfoundation.org>,
Rajat Jain <rajatja@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH v4 0/4] PCI/ASPM: add sysfs attributes for controlling ASPM
Date: Wed, 28 Aug 2019 07:40:54 +0200 [thread overview]
Message-ID: <4eace423-8727-2957-79ab-bf954a050e20@gmail.com> (raw)
In-Reply-To: <20190827233541.GL9987@google.com>
On 28.08.2019 01:35, Bjorn Helgaas wrote:
> On Sat, Aug 24, 2019 at 05:39:37PM +0200, Heiner Kallweit wrote:
>> 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 attributes users can control which ASPM
>> link-states are disabled.
>>
>> v2:
>> - use a dedicated sysfs attribute per link state
>> - allow separate control of ASPM and PCI PM L1 sub-states
>>
>> v3:
>> - patch 3: statically allocate the attribute group
>> - patch 3: replace snprintf with printf
>> - add patch 4
>>
>> v4:
>> - patch 3: add call to sysfs_update_group because is_visible callback
>> returns false always at file creation time
>> - patch 3: simplify code a little
>>
>> Heiner Kallweit (4):
>> PCI/ASPM: add L1 sub-state support to pci_disable_link_state
>> PCI/ASPM: allow to re-enable Clock PM
>> PCI/ASPM: add sysfs attributes for controlling ASPM link states
>> PCI/ASPM: remove Kconfig option PCIEASPM_DEBUG and related code
>>
>> Documentation/ABI/testing/sysfs-bus-pci | 13 ++
>> drivers/pci/pci-sysfs.c | 10 +-
>> drivers/pci/pci.h | 12 +-
>> drivers/pci/pcie/Kconfig | 7 -
>> drivers/pci/pcie/aspm.c | 236 ++++++++++++++++--------
>> include/linux/pci-aspm.h | 10 +-
>> 6 files changed, 195 insertions(+), 93 deletions(-)
>
> I can fix this if you don't get to it, but this doesn't apply cleanly
> to either my "master" branch (v5.3-rc1) or my "next" branch. I always
> prefer series based on my "master" branch when possible.
>
> Bjorn
>
I based it on top of linux-next, can rebase it to your master branch.
Heiner
next prev parent reply other threads:[~2019-08-28 5:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-24 15:39 [PATCH v4 0/4] PCI/ASPM: add sysfs attributes for controlling ASPM Heiner Kallweit
2019-08-24 15:40 ` [PATCH v4 1/4] PCI/ASPM: add L1 sub-state support to pci_disable_link_state Heiner Kallweit
2019-08-24 15:40 ` [PATCH v4 2/4] PCI/ASPM: allow to re-enable Clock PM Heiner Kallweit
2019-08-24 15:41 ` [PATCH v4 3/4] PCI/ASPM: add sysfs attributes for controlling ASPM link states Heiner Kallweit
2019-08-28 21:04 ` Greg KH
2019-08-24 15:42 ` [PATCH v4 4/4] PCI/ASPM: remove Kconfig option PCIEASPM_DEBUG and related code Heiner Kallweit
2019-08-27 23:35 ` [PATCH v4 0/4] PCI/ASPM: add sysfs attributes for controlling ASPM Bjorn Helgaas
2019-08-28 5:40 ` Heiner Kallweit [this message]
2019-08-28 5:48 ` Heiner Kallweit
2019-08-28 13:06 ` Bjorn Helgaas
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=4eace423-8727-2957-79ab-bf954a050e20@gmail.com \
--to=hkallweit1@gmail.com \
--cc=fred@fredlawl.com \
--cc=gregkh@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rajatja@google.com \
/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