From: Joel Stanley <joel@jms.id.au>
To: Arnd Bergmann <arnd@arndb.de>, Andrew Jeffery <andrew@aj.id.au>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org
Subject: [PATCH v2 0/3] firmware: Add boot information to sysfs
Date: Thu, 3 Feb 2022 22:23:41 +1030 [thread overview]
Message-ID: <20220203115344.267159-1-joel@jms.id.au> (raw)
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 | 43 +++++++++
arch/x86/kernel/setup.c | 6 ++
drivers/base/firmware.c | 90 +++++++++++++++++++
drivers/soc/aspeed/aspeed-socinfo.c | 46 +++++++++-
include/linux/firmware_bootinfo.h | 22 +++++
5 files changed, 206 insertions(+), 1 deletion(-)
create mode 100644 Documentation/ABI/testing/sysfs-firmware-bootinfo
create mode 100644 include/linux/firmware_bootinfo.h
--
2.34.1
next reply other threads:[~2022-02-03 11:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 11:53 Joel Stanley [this message]
2022-02-03 11:53 ` [PATCH v2 1/3] firmware: Add boot information to sysfs Joel Stanley
2022-02-03 12:44 ` Greg Kroah-Hartman
2022-02-04 6:55 ` Joel Stanley
2022-02-03 14:22 ` Robin Murphy
2022-02-04 5:53 ` Joel Stanley
2022-02-07 6:39 ` Daniel Axtens
2022-02-03 11:53 ` [PATCH v2 2/3] ARM: aspeed: Add secure boot controller support Joel Stanley
2022-02-03 11:53 ` [PATCH v2 3/3] x86/setup: Populate bootinfo with secure boot status Joel Stanley
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=20220203115344.267159-1-joel@jms.id.au \
--to=joel@jms.id.au \
--cc=andrew@aj.id.au \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
/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