From: Bjorn Helgaas <helgaas@kernel.org>
To: manivannan.sadhasivam@oss.qualcomm.com
Cc: "Bjorn Helgaas" <bhelgaas@google.com>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Rob Herring" <robh@kernel.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
"David E. Box" <david.e.box@linux.intel.com>,
"Kai-Heng Feng" <kai.heng.feng@canonical.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Chia-Lin Kao" <acelan.kao@canonical.com>
Subject: Re: [PATCH 0/2] PCI/ASPM: Enable ASPM and Clock PM by default on devicetree platforms
Date: Tue, 16 Sep 2025 15:25:50 -0500 [thread overview]
Message-ID: <20250916202550.GA1814752@bhelgaas> (raw)
In-Reply-To: <20250916172116.GA1808269@bhelgaas>
[+cc Heiner, AceLan in case it's of interest to you]
On Tue, Sep 16, 2025 at 12:21:18PM -0500, Bjorn Helgaas wrote:
> [+cc Kai-Heng, Rafael; thread at
> https://lore.kernel.org/r/20250916-pci-dt-aspm-v1-0-778fe907c9ad@oss.qualcomm.com]
>
> On Tue, Sep 16, 2025 at 09:42:51PM +0530, Manivannan Sadhasivam via B4 Relay wrote:
> > Hi,
> >
> > This series is one of the 'let's bite the bullet' kind, where we have decided to
> > enable all ASPM and Clock PM states by default on devicetree platforms [1]. The
> > reason why devicetree platforms were chosen because, it will be of minimal
> > impact compared to the ACPI platforms. So seemed ideal to test the waters.
> >
> > Problem Statement
> > =================
> >
> > Historically, PCI subsystem relied on the BIOS to enable ASPM and Clock PM
> > states for PCI devices before the kernel boot. This was done to avoid enabling
> > ASPM for the buggy devices that are known to create issues with ASPM (even
> > though they advertise the ASPM capability). But BIOS is not at all a thing on
> > most of the non-x86 platforms. For instance, the majority of the Embedded and
> > Compute ARM based platforms using devicetree have something called bootloader,
> > which is not anyway near the standard BIOS used in x86 based platforms. And
> > these bootloaders wouldn't touch PCIe at all, unless they boot using PCIe
> > storage, even then there would be no guarantee that the ASPM states will get
> > enabled. Another example is the Intel's VMD domain that is not at all configured
> > by the BIOS. But, this series is not enabling ASPM/Clock PM for VMD domain. I
> > hope it will be done similarly in the future patches.
> >
> > Solution
> > ========
> >
> > So to avoid relying on BIOS, it was agreed [2] that the PCI subsystem has to
> > enable ASPM and Clock PM states based on the device capability. If any devices
> > misbehave, then they should be quirked accordingly.
> >
> > First patch of this series introduces two helper functions to enable all ASPM
> > and Clock PM states if CONFIG_OF is enabled. Second patch drops the custom ASPM
> > enablement code from the pcie-qcom driver as it is no longer needed.
> >
> > Testing
> > =======
> >
> > This series is tested on Lenovo Thinkpad T14s based on Snapdragon X1 SoC. All
> > supported ASPM states are getting enabled for both the NVMe and WLAN devices by
> > default.
> >
> > [1] https://lore.kernel.org/linux-pci/a47sg5ahflhvzyzqnfxvpk3dw4clkhqlhznjxzwqpf4nyjx5dk@bcghz5o6zolk
> > [2] https://lore.kernel.org/linux-pci/20250828204345.GA958461@bhelgaas
> >
> > Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
> > ---
> > Manivannan Sadhasivam (2):
> > PCI/ASPM: Override the ASPM and Clock PM states set by BIOS for devicetree platforms
> > PCI: qcom: Remove the custom ASPM enablement code
> >
> > drivers/pci/controller/dwc/pcie-qcom.c | 32 -----------------------
> > drivers/pci/pcie/aspm.c | 48 ++++++++++++++++++++++++++++++----
> > 2 files changed, 43 insertions(+), 37 deletions(-)
> > ---
> > base-commit: 8f5ae30d69d7543eee0d70083daf4de8fe15d585
> > change-id: 20250916-pci-dt-aspm-8b3a7e8d2cf1
> >
> > Best regards,
> > --
> > Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
> >
> >
prev parent reply other threads:[~2025-09-16 20:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 16:12 [PATCH 0/2] PCI/ASPM: Enable ASPM and Clock PM by default on devicetree platforms Manivannan Sadhasivam via B4 Relay
2025-09-16 16:12 ` [PATCH 1/2] PCI/ASPM: Override the ASPM and Clock PM states set by BIOS for " Manivannan Sadhasivam via B4 Relay
2025-09-16 16:28 ` Konrad Dybcio
2025-09-17 10:27 ` Manivannan Sadhasivam
2025-09-16 17:15 ` Bjorn Helgaas
2025-09-17 10:44 ` Manivannan Sadhasivam
2025-09-17 11:22 ` Bjorn Helgaas
2025-09-17 13:03 ` Manivannan Sadhasivam
2025-09-22 15:53 ` Manivannan Sadhasivam
2025-09-16 16:12 ` [PATCH 2/2] PCI: qcom: Remove the custom ASPM enablement code Manivannan Sadhasivam via B4 Relay
2025-09-16 17:21 ` [PATCH 0/2] PCI/ASPM: Enable ASPM and Clock PM by default on devicetree platforms Bjorn Helgaas
2025-09-16 20:25 ` 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=20250916202550.GA1814752@bhelgaas \
--to=helgaas@kernel.org \
--cc=acelan.kao@canonical.com \
--cc=bhelgaas@google.com \
--cc=david.e.box@linux.intel.com \
--cc=hkallweit1@gmail.com \
--cc=kai.heng.feng@canonical.com \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=manivannan.sadhasivam@oss.qualcomm.com \
--cc=rafael@kernel.org \
--cc=robh@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