From: Dan Williams <dan.j.williams@intel.com>
To: <bhelgaas@google.com>
Cc: <linux-pci@vger.kernel.org>, <lukas@wunner.de>,
<linux-kernel@vger.kernel.org>, <Jonathan.Cameron@huawei.com>
Subject: [PATCH 1/3] PCI: Establish document for PCI host bridge sysfs attributes
Date: Wed, 16 Jul 2025 09:08:33 -0700 [thread overview]
Message-ID: <20250716160835.680486-2-dan.j.williams@intel.com> (raw)
In-Reply-To: <20250716160835.680486-1-dan.j.williams@intel.com>
In preparation for adding more host bridge sysfs attributes, document the
existing naming format and 'firmware_node' attribute.
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
---
.../ABI/testing/sysfs-devices-pci-host-bridge | 19 +++++++++++++++++++
MAINTAINERS | 1 +
2 files changed, 20 insertions(+)
create mode 100644 Documentation/ABI/testing/sysfs-devices-pci-host-bridge
diff --git a/Documentation/ABI/testing/sysfs-devices-pci-host-bridge b/Documentation/ABI/testing/sysfs-devices-pci-host-bridge
new file mode 100644
index 000000000000..8c3a652799f1
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-devices-pci-host-bridge
@@ -0,0 +1,19 @@
+What: /sys/devices/pciDDDD:BB
+ /sys/devices/.../pciDDDD:BB
+Contact: linux-pci@vger.kernel.org
+Description:
+ A PCI host bridge device parents a PCI bus device topology. PCI
+ controllers may also parent host bridges. The DDDD:BB format
+ conveys the PCI domain (ACPI segment) number and root bus number
+ (in hexadecimal) of the host bridge. Note that the domain number
+ may be larger than the 16-bits that the "DDDD" format implies
+ for emulated host-bridges.
+
+What: pciDDDD:BB/firmware_node
+Contact: linux-pci@vger.kernel.org
+Description:
+ (RO) Symlink to the platform firmware device object "companion"
+ of the host bridge. For example, an ACPI device with an _HID of
+ PNP0A08 (/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00). See
+ /sys/devices/pciDDDD:BB entry for details about the DDDD:BB
+ format.
diff --git a/MAINTAINERS b/MAINTAINERS
index 0c1d245bf7b8..368ca0bfdb9f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -19198,6 +19198,7 @@ Q: https://patchwork.kernel.org/project/linux-pci/list/
B: https://bugzilla.kernel.org
C: irc://irc.oftc.net/linux-pci
T: git git://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git
+F: Documentation/ABI/testing/sysfs-devices-pci-host-bridge
F: Documentation/PCI/
F: Documentation/devicetree/bindings/pci/
F: arch/x86/kernel/early-quirks.c
--
2.50.1
next prev parent reply other threads:[~2025-07-16 16:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 16:08 [PATCH 0/3] PCI: Unify domain emulation and misc documentation update Dan Williams
2025-07-16 16:08 ` Dan Williams [this message]
2025-07-16 16:08 ` [PATCH 2/3] PCI: Enable host bridge emulation for PCI_DOMAINS_GENERIC platforms Dan Williams
2025-07-17 17:25 ` Michael Kelley
2025-07-17 19:59 ` dan.j.williams
2025-07-17 23:06 ` Michael Kelley
2025-07-18 0:22 ` dan.j.williams
2025-07-18 3:03 ` Michael Kelley
2025-07-18 19:17 ` dan.j.williams
2025-07-16 16:08 ` [PATCH 3/3] PCI: vmd: Switch to pci_bus_find_emul_domain_nr() Dan Williams
2025-07-17 22:13 ` [PATCH 0/3] PCI: Unify domain emulation and misc documentation update Bjorn Helgaas
2025-07-18 0:26 ` dan.j.williams
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=20250716160835.680486-2-dan.j.williams@intel.com \
--to=dan.j.williams@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
/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