From: Bjorn Helgaas <helgaas@kernel.org>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
"open list:PCI SUBSYSTEM" <linux-pci@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Lukas Wunner <lukas@wunner.de>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH] PCI/ASPM: Enable L0s/L1 for removable devices when BIOS didn't configure ASPM
Date: Wed, 6 May 2026 10:27:21 -0500 [thread overview]
Message-ID: <20260506152721.GA790227@bhelgaas> (raw)
In-Reply-To: <a6ffd678-65ee-43a0-a9f2-99d45126f5b0@amd.com>
On Wed, May 06, 2026 at 10:10:47AM -0500, Mario Limonciello wrote:
> On 5/5/26 23:53, Mika Westerberg wrote:
> > On Tue, May 05, 2026 at 08:09:22PM +0200, Rafael J. Wysocki wrote:
> > > On Tue, May 5, 2026 at 12:53 AM Mario Limonciello
> > > <mario.limonciello@amd.com> wrote:
> ...
> > > > + * For devicetree platforms, enable L0s and L1 by default.
> > > > + *
> > > > + * For removable devices (e.g., Thunderbolt/USB4), enable L0s and L1
> > > > + * by default if BIOS didn't configure any ASPM states. This handles
> > > > + * hotplugged devices where firmware may not have configured ASPM.
> > > > + */
> >
> > Only L1 is supported over TB/USB4 tunnel (no L0s, no L1 substates). The
> > PCIe endpoint and the downstream port it connects to of course can support
> > the full range as that's a real PCIe link.
>
> OK - the comment should be updated but I do expect that below code
> (link->aspm_support) should remain OK.
TB/USB4 are examples of removable devices but they're not the only
ones, so I think it's OK for the comment to mention L0s. In fact, it
*should* mention L0s since the code below includes L0s, and mentioning
only L1 would just be confusing.
> > > > + if (of_have_populated_dt() ||
> > > > + (dev_is_removable(&pdev->dev) && !link->aspm_enabled)) {
> > > > if (link->aspm_support & PCIE_LINK_STATE_L0S)
> > > > link->aspm_default |= PCIE_LINK_STATE_L0S;
> > > > if (link->aspm_support & PCIE_LINK_STATE_L1)
> > > > --
> > > > 2.43.0
> > > >
>
next prev parent reply other threads:[~2026-05-06 15:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 22:52 [PATCH] PCI/ASPM: Enable L0s/L1 for removable devices when BIOS didn't configure ASPM Mario Limonciello
2026-05-04 23:17 ` sashiko-bot
2026-05-05 16:05 ` Bjorn Helgaas
2026-05-05 16:08 ` Mario Limonciello
2026-05-05 21:42 ` Bjorn Helgaas
2026-05-06 3:36 ` Mario Limonciello
2026-05-05 18:09 ` Rafael J. Wysocki
2026-05-06 4:53 ` Mika Westerberg
2026-05-06 15:10 ` Mario Limonciello
2026-05-06 15:27 ` Bjorn Helgaas [this message]
2026-05-14 17:14 ` Mario Limonciello
2026-05-14 22:54 ` 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=20260506152721.GA790227@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mario.limonciello@amd.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.