From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Bjorn Helgaas <helgaas@kernel.org>, Johan Hovold <johan@kernel.org>
Cc: linux-pci@vger.kernel.org,
Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>,
FUKAUMI Naoki <naoki@radxa.com>,
Herve Codina <herve.codina@bootlin.com>,
Diederik de Haas <diederik@cknow-tech.com>,
Dragan Simic <dsimic@manjaro.org>,
linuxppc-dev@lists.ozlabs.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
Shawn Lin <shawn.lin@rock-chips.com>, Frank Li <Frank.li@nxp.com>,
"R.T.Dickinson" <rtd2@xtra.co.nz>,
mad skateman <madskateman@gmail.com>,
hypexed@yahoo.com.au
Subject: [PATCH] PCI/ASPM: Enable only L0s and L1 for devicetree platforms
Date: Mon, 27 Oct 2025 18:12:24 +0100 [thread overview]
Message-ID: <3aa95b26-7801-476e-840f-5976b0ee11c1@xenosoft.de> (raw)
In-Reply-To: <20251024203924.GA1361677@bhelgaas>
Hi All,
I activated CONFIG_PCIEASPM and CONFIG_PCIEASPM_DEFAULT again for the
RC3 of kernel 6.18. Unfortunately my AMD Radeon HD6870 doesn't work with
the latest patches.
But that doesn't matter because we disable the above kernel options by
default. We don't need power management for PCI Express because of boot
issues and performance issues.
Cheers,
Christian
next prev parent reply other threads:[~2025-10-27 17:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 18:06 [PATCH] PCI/ASPM: Enable only L0s and L1 for devicetree platforms Bjorn Helgaas
2025-10-23 18:25 ` Bjorn Helgaas
2025-10-23 19:59 ` Diederik de Haas
2025-10-23 20:39 ` Bjorn Helgaas
2025-10-24 4:28 ` Christian Zigotzky
2025-10-23 18:27 ` Dragan Simic
2025-10-23 20:37 ` Bjorn Helgaas
2025-10-24 15:12 ` Johan Hovold
2025-10-24 15:20 ` Johan Hovold
2025-10-24 20:39 ` Bjorn Helgaas
2025-10-27 10:00 ` Johan Hovold
2025-10-27 17:12 ` Christian Zigotzky [this message]
2025-10-28 23:33 ` Bjorn Helgaas
2025-10-29 5:47 ` Christian Zigotzky
2025-10-29 15:59 ` Bjorn Helgaas
2025-10-29 17:25 ` 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=3aa95b26-7801-476e-840f-5976b0ee11c1@xenosoft.de \
--to=chzigotzky@xenosoft.de \
--cc=Frank.li@nxp.com \
--cc=bhelgaas@google.com \
--cc=diederik@cknow-tech.com \
--cc=dsimic@manjaro.org \
--cc=helgaas@kernel.org \
--cc=herve.codina@bootlin.com \
--cc=hypexed@yahoo.com.au \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madskateman@gmail.com \
--cc=manivannan.sadhasivam@oss.qualcomm.com \
--cc=naoki@radxa.com \
--cc=rtd2@xtra.co.nz \
--cc=shawn.lin@rock-chips.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;
as well as URLs for NNTP newsgroup(s).