From: Heiner Kallweit <hkallweit1@gmail.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Question on generic PCI ACPI/DT device property wrt ASPM
Date: Tue, 16 Sep 2025 21:48:06 +0200 [thread overview]
Message-ID: <5b00870c-be1a-42d6-8857-48b89716d5e2@gmail.com> (raw)
There are drivers (in my case r8169) disabling ASPM for a device per default
because there are known issues on a number of systems. However on other
systems ASPM works flawlessly, and vendors (especially of notebooks) would
like to (re-)enable ASPM for this device on such systems.
Reference:
https://lore.kernel.org/netdev/20250912072939.2553835-1-acelan.kao@canonical.com/
Realtek NICs are used on more or less every consumer device, and maintaining
long DMI-based whitelists wouldn't be too nice.
Therefore idea is to use a device property (working title: aspm-is-safe), that
can be set via ACPI or DT. In my case it's a PCIe NIC, but in general the
property could be applicable on every PCIe device.
So question is to which schema such a property would belong. Here?
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Documentation/devicetree/bindings/pci/pci-ep.yaml?h=next-20250916
next reply other threads:[~2025-09-16 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 19:48 Heiner Kallweit [this message]
2025-09-16 20:25 ` Question on generic PCI ACPI/DT device property wrt ASPM Bjorn Helgaas
2025-09-16 20:56 ` Heiner Kallweit
2025-09-16 22:22 ` 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=5b00870c-be1a-42d6-8857-48b89716d5e2@gmail.com \
--to=hkallweit1@gmail.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-pci@vger.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