From: Matthew Wood <thepacketgeek@gmail.com>
To: "Bjorn Helgaas" <bhelgaas@google.com>
Cc: "Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/1] PCI/sysfs: Expose PCIe device serial number
Date: Wed, 16 Jul 2025 09:32:10 -0700 [thread overview]
Message-ID: <20250716163213.469226-1-thepacketgeek@gmail.com> (raw)
Add a single sysfs read-only interface for reading PCIe device serial
numbers from userspace, using the same hexadecimal 1-byte dashed
formatting as lspci serial number capability output:
more /sys/devices/pci0000:c0/0000:c0:01.1/0000:c1:00.0/0000:c2:1f.0/0000:cc:00.0/device_serial_number
00-80-ee-00-00-00-41-80
If a device doesn't support the serial number capability, the
device_serial_number sysfs attribute will not be visible.
Comparing serial number format to lspci output:
sudo lspci -vvv -s cc:00.0
cc:00.0 Serial Attached SCSI controller: Broadcom / LSI PCIe Switch management endpoint (rev b0)
Subsystem: Broadcom / LSI Device 0144
...
Capabilities: [100 v1] Device Serial Number 00-80-ee-00-00-00-41-80
...
This PCIe device sysfs attribute eliminates the need for parsing lspci
output (e.g. regexp) for userspace applications that utilize serial
numbers.
Matthew Wood (1):
PCI/sysfs: Expose PCIe device serial number
Documentation/ABI/testing/sysfs-bus-pci | 7 +++++++
drivers/pci/pci-sysfs.c | 27 ++++++++++++++++++++++---
2 files changed, 31 insertions(+), 3 deletions(-)
--
2.50.0
next reply other threads:[~2025-07-16 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 16:32 Matthew Wood [this message]
2025-07-16 16:32 ` [PATCH v3 1/1] PCI/sysfs: Expose PCIe device serial number Matthew Wood
2025-07-16 17:02 ` Mario Limonciello
2025-07-16 17:43 ` Matthew Wood
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=20250716163213.469226-1-thepacketgeek@gmail.com \
--to=thepacketgeek@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=thomas.weissschuh@linutronix.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;
as well as URLs for NNTP newsgroup(s).