From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Joel Stanley <joel@jms.id.au>
Cc: Arnd Bergmann <arnd@arndb.de>, Andrew Jeffery <andrew@aj.id.au>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org
Subject: Re: [PATCH v3 0/3] firmware: Add boot information to sysfs
Date: Fri, 22 Apr 2022 08:48:15 +0200 [thread overview]
Message-ID: <YmJPrxB8x/zE4Vy7@kroah.com> (raw)
In-Reply-To: <20220204072234.304543-1-joel@jms.id.au>
On Fri, Feb 04, 2022 at 05:52:31PM +1030, Joel Stanley wrote:
> 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.
I would like arch maintainers to review this before it going any
further.
thanks,
greg k-h
prev parent reply other threads:[~2022-04-22 6:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 7:22 Joel Stanley
2022-02-04 7:22 ` [PATCH v3 1/3] " Joel Stanley
2022-04-22 6:46 ` Greg Kroah-Hartman
2022-04-22 9:05 ` Arnd Bergmann
2022-04-22 12:26 ` Greg Kroah-Hartman
2022-02-04 7:22 ` [PATCH v3 2/3] ARM: aspeed: Add secure boot controller support Joel Stanley
2022-02-04 7:22 ` [PATCH v3 3/3] x86/setup: Populate bootinfo with secure boot status Joel Stanley
2022-04-22 6:48 ` Greg Kroah-Hartman [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=YmJPrxB8x/zE4Vy7@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrew@aj.id.au \
--cc=arnd@arndb.de \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robin.murphy@arm.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
all inboxes | Powered by JetHome®