From: Nate DeSimone <nathaniel.l.desimone@intel.com>
To: linux-acpi@vger.kernel.org
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
tony.luck@intel.com
Subject: [PATCH v2 2/2] Documentation: ABI: add FBPT and S3PT entries to sysfs-firmware-acpi
Date: Mon, 9 Mar 2026 21:34:41 -0700 [thread overview]
Message-ID: <20260310043449.1295-3-nathaniel.l.desimone@intel.com> (raw)
In-Reply-To: <20260310043449.1295-1-nathaniel.l.desimone@intel.com>
Document the FBPT and S3PT sysfs attributes under
/sys/firmware/acpi/fpdt/
Signed-off-by: Nate DeSimone <nathaniel.l.desimone@intel.com>
---
Documentation/ABI/testing/sysfs-firmware-acpi | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-firmware-acpi b/Documentation/ABI/testing/sysfs-firmware-acpi
index 72e7c9161ce7..fa33dda331f2 100644
--- a/Documentation/ABI/testing/sysfs-firmware-acpi
+++ b/Documentation/ABI/testing/sysfs-firmware-acpi
@@ -41,6 +41,12 @@ Description:
platform runtime firmware S3 resume, just prior to
handoff to the OS waking vector. In nanoseconds.
+ FBPT: The raw binary contents of the Firmware Basic Boot
+ Performance Table (FBPT) subtable.
+
+ S3PT: The raw binary contents of the S3 Performance Table
+ (S3PT) subtable.
+
What: /sys/firmware/acpi/bgrt/
Date: January 2012
Contact: Matthew Garrett <mjg@redhat.com>
--
2.34.1
prev parent reply other threads:[~2026-03-10 4:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-22 6:30 [PATCH v1] ACPI: FPDT: expose FBPT and S3PT subtables via sysfs Nate DeSimone
2026-02-23 17:54 ` Luck, Tony
2026-02-23 20:32 ` Nate DeSimone
2026-03-10 4:34 ` [PATCH v2 0/2] " Nate DeSimone
2026-03-10 4:34 ` [PATCH v2 1/2] " Nate DeSimone
2026-03-11 13:18 ` Rafael J. Wysocki
2026-03-24 23:20 ` Nate DeSimone
2026-03-10 4:34 ` Nate DeSimone [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=20260310043449.1295-3-nathaniel.l.desimone@intel.com \
--to=nathaniel.l.desimone@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=tony.luck@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.