From: Mario Limonciello <mario.limonciello@amd.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "open list:PCI SUBSYSTEM" <linux-pci@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Lukas Wunner <lukas@wunner.de>, <linux-pm@vger.kernel.org>,
Mario Limonciello <mario.limonciello@amd.com>
Subject: [PATCH] PCI/ASPM: Enable L0s/L1 for removable devices when BIOS didn't configure ASPM
Date: Mon, 4 May 2026 17:52:46 -0500 [thread overview]
Message-ID: <20260504225246.480921-1-mario.limonciello@amd.com> (raw)
When comparing lspci output between Windows and Linux for hotplugged
Thunderbolt 5 eGPU devices, Windows enables ASPM L1 but Linux doesn't:
Windows: LnkCtl: ASPM L1 Enabled
Linux: LnkCtl: ASPM Disabled
This difference in ASPM configuration can cause behavioral differences
between the two operating systems for the same hardware.
The root cause is that Linux's default ASPM policy (POLICY_DEFAULT) relies
on firmware/BIOS configuration. For hotplugged devices like Thunderbolt/USB4
eGPUs, the BIOS may not have configured ASPM since the device wasn't present
at boot time. As a result, link->aspm_enabled is 0, link->aspm_default is
set to 0, and Linux never enables ASPM for these devices.
Devicetree platforms already have special handling to enable L0s/L1 by
default regardless of firmware configuration. Extend this same logic to
removable devices when firmware hasn't configured any ASPM states.
This makes Linux behavior more consistent with Windows for hotplugged
Thunderbolt/USB4 devices.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=221319
Assisted-by: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
---
drivers/pci/pcie/aspm.c | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/drivers/pci/pcie/aspm.c b/drivers/pci/pcie/aspm.c
index 925373b98dff0..77497d90be0b7 100644
--- a/drivers/pci/pcie/aspm.c
+++ b/drivers/pci/pcie/aspm.c
@@ -804,8 +804,15 @@ static void pcie_aspm_override_default_link_state(struct pcie_link_state *link)
struct pci_dev *pdev = link->downstream;
u32 override;
- /* For devicetree platforms, enable L0s and L1 by default */
- if (of_have_populated_dt()) {
+ /*
+ * 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.
+ */
+ 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 reply other threads:[~2026-05-04 22:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 22:52 Mario Limonciello [this message]
2026-05-04 23:17 ` [PATCH] PCI/ASPM: Enable L0s/L1 for removable devices when BIOS didn't configure ASPM 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
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=20260504225246.480921-1-mario.limonciello@amd.com \
--to=mario.limonciello@amd.com \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox