From: Bjorn Helgaas <helgaas@kernel.org>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH] PCI/ASPM: Fix L1 sub-state handling in aspm_attr_store_common
Date: Tue, 24 Oct 2023 19:38:29 -0500 [thread overview]
Message-ID: <20231025003829.GA1705553@bhelgaas> (raw)
In-Reply-To: <6ba7dd79-9cfe-4ed0-a002-d99cb842f361@gmail.com>
On Wed, Oct 11, 2023 at 09:46:45AM +0200, Heiner Kallweit wrote:
> So far we may see an unexpected behavior regard L1 sub-states.
> Following scenario:
>
> Write 0 to "l1_aspm" to disable L1
> Write 1 to "l1_1_aspm" to enable L1.1
>
> Intention of step 1 is to implicitly disable also L1.1 and L1.2.
> However after step 2 L1.2 is unexpectedly enabled.
>
> Fix this by explicitly disabling L1 sub-states when disabling L1.
>
> Fixes: 72ea91afbfb0 ("PCI/ASPM: Add sysfs attributes for controlling ASPM link states")
> Link: https://lore.kernel.org/linux-pci/20231002151452.GA560499@bhelgaas/
> Cc: stable@vger.kernel.org
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
Applied to pci/aspm for v6.7, thanks again.
> ---
> Splitted-out part of original patch according to linked discussion.
> ---
> drivers/pci/pcie/aspm.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/pci/pcie/aspm.c b/drivers/pci/pcie/aspm.c
> index 530c3bb5708c..fc18e42f0a6e 100644
> --- a/drivers/pci/pcie/aspm.c
> +++ b/drivers/pci/pcie/aspm.c
> @@ -1248,6 +1248,8 @@ static ssize_t aspm_attr_store_common(struct device *dev,
> link->aspm_disable &= ~ASPM_STATE_L1;
> } else {
> link->aspm_disable |= state;
> + if (state & ASPM_STATE_L1)
> + link->aspm_disable |= ASPM_STATE_L1SS;
> }
>
> pcie_config_aspm_link(link, policy_to_aspm_state(link));
> --
> 2.42.0
>
prev parent reply other threads:[~2023-10-25 0:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 7:46 [PATCH] PCI/ASPM: Fix L1 sub-state handling in aspm_attr_store_common Heiner Kallweit
2023-10-25 0:38 ` Bjorn Helgaas [this message]
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=20231025003829.GA1705553@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=hkallweit1@gmail.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