public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Nate DeSimone <nathaniel.l.desimone@intel.com>
To: tony.luck@intel.com
Cc: lenb@kernel.org, linux-acpi@vger.kernel.org,
	nathaniel.l.desimone@intel.com, rafael@kernel.org
Subject: Re: [PATCH v1] ACPI: FPDT: expose FBPT and S3PT subtables via sysfs
Date: Mon, 23 Feb 2026 12:32:58 -0800	[thread overview]
Message-ID: <20260223203258.2877-1-nathaniel.l.desimone@intel.com> (raw)
In-Reply-To: <SJ1PR11MB6083ECBFD999F240987EBDE1FC77A@SJ1PR11MB6083.namprd11.prod.outlook.com>

> > Add sysfs attributes at /sys/firmware/acpi/fpdt/tables/FBPT and
> > /sys/firmware/acpi/fpdt/tables/S3PT that expose the raw contents of the
> > FPDT subtables. Note that /sys/firmware/acpi/tables/FPDT only provides
> > the top level table, not the subtables. Adding access to the subtables
> > enables a usage model similar to /sys/firmware/dmi/tables/DMI, allowing
> > userspace tools to interpret newer record types (e.g. String Event
> > Records, Microcontroller Boot Performance Data Records, etc.) defined
> > in recent ACPI specifications[1] without requiring kernel changes.
>
> Is the existing (for BERT) /sys/firmware/acpi/tables/data directory a more
> appropriate spot for these? Naming the new subdirectory "tables" seems
> misleading as there aren't a top-level ACPI "FBPT" or "S3PT" tables?

I'm not experienced with the organizational semantics of sysfs. I made a
best-guess when choosing /sys/firmware/acpi/fpdt/tables/FBPT. Should I do
something like /sys/firmware/acpi/tables/data/fpdt/FBPT? That way the data
source is explicit and there won't be name collisions with other data in the
future?

Wherever the kernel maintainers think is the best place to put these new sysfs
attributes I'm completely on-board with. Please let me know where in the
filesystem they should go and I'll get a v2 patch implemented!

> Once naming is resolved, needs update to Documentation/ABI/testing/sysfs-fi=
> rmware-acpi
> for whatever names are chosed for the new files.

I will happily add that as well in a v2 patch series.

>
> Code looks good.
>
> -Tony

Thank You!
-Nate

  reply	other threads:[~2026-02-23 20:33 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 [this message]
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   ` [PATCH v2 2/2] Documentation: ABI: add FBPT and S3PT entries to sysfs-firmware-acpi Nate DeSimone

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=20260223203258.2877-1-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox