Messages in this thread | | | From | Joel Stanley <> | Subject | [PATCH v3 0/3] firmware: Add boot information to sysfs | Date | Fri, 4 Feb 2022 17:52:31 +1030 |
| |
v3 resolves Greg's review for the bootinfo header and macros, and drops uart_boot as it's unlikely to be common across platforms.
v2 reworks the series to put the sysfs properties in the core, and optionally show them with the is_visible() callback.
This is the second iteration of this idea. The first used socinfo custom attribute groups, but Arnd suggested we make this something standardised under /sys/firmware instead:
http://lore.kernel.org/all/CAK8P3a3MRf0aGt1drkgsuZyBbeoy+S7Ha18SBM01q+3f33oL+Q@mail.gmail.com
Some ARM systems have a firmware that provides a hardware root of trust. It's useful for the system to know how this root of trust has been configured, so provide a standardised interface that expose this information to userspace.
This is implemented as a sysfs attribute group registration in the driver core, with platforms populating values obtained from firmware at kernel boot time.
Patch 2 provides a user of the properties on an ARM system.
Patch 3 is new in v2 and is an example of populating bootinfo with the EFI secure boot status.
Joel Stanley (3): firmware: Add boot information to sysfs ARM: aspeed: Add secure boot controller support x86/setup: Populate bootinfo with secure boot status
.../ABI/testing/sysfs-firmware-bootinfo | 37 +++++++++ arch/x86/kernel/setup.c | 6 ++ drivers/base/firmware.c | 80 +++++++++++++++++++ drivers/soc/aspeed/aspeed-socinfo.c | 44 +++++++++- include/linux/firmware_bootinfo.h | 48 +++++++++++ 5 files changed, 214 insertions(+), 1 deletion(-) create mode 100644 Documentation/ABI/testing/sysfs-firmware-bootinfo create mode 100644 include/linux/firmware_bootinfo.h
-- 2.34.1
| |