From: Rob Herring <robh@kernel.org>
To: David Brazdil <dbrazdil@google.com>
Cc: devicetree@vger.kernel.org, Will Deacon <will@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Andrew Scull <ascull@google.com>,
Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v6 1/2] dt-bindings: reserved-memory: Open Profile for DICE
Date: Tue, 11 Jan 2022 19:04:47 -0600 [thread overview]
Message-ID: <Yd4pL8ktqdQAI7PU@robh.at.kernel.org> (raw)
In-Reply-To: <20220104100645.1810028-2-dbrazdil@google.com>
On Tue, 04 Jan 2022 10:06:44 +0000, David Brazdil wrote:
> Add DeviceTree bindings for Open Profile for DICE, an open protocol for
> measured boot. Firmware uses DICE to measure the hardware/software
> combination and generates Compound Device Identifier (CDI) certificates.
> These are stored in memory and the buffer is described in the DT as
> a reserved memory region compatible with 'google,open-dice'.
>
> Signed-off-by: David Brazdil <dbrazdil@google.com>
> ---
> .../reserved-memory/google,open-dice.yaml | 45 +++++++++++++++++++
> 1 file changed, 45 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/reserved-memory/google,open-dice.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-01-12 1:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 10:06 [PATCH v6 0/2] Driver for Open Profile for DICE David Brazdil
2022-01-04 10:06 ` [PATCH v6 1/2] dt-bindings: reserved-memory: " David Brazdil
2022-01-12 1:04 ` Rob Herring [this message]
2022-01-04 10:06 ` [PATCH v6 2/2] misc: open-dice: Add driver to expose DICE data to userspace David Brazdil
2022-01-11 23:32 ` Wedson Almeida Filho
2022-01-26 20:05 ` David Brazdil
2022-01-26 9:04 ` [PATCH v6 0/2] Driver for Open Profile for DICE Greg Kroah-Hartman
2022-01-26 10:39 ` David Brazdil
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=Yd4pL8ktqdQAI7PU@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=arnd@arndb.de \
--cc=ascull@google.com \
--cc=dbrazdil@google.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).