All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: David Brazdil <dbrazdil@google.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Arnd Bergmann <arnd@arndb.de>, Will Deacon <will@kernel.org>,
	Andrew Scull <ascull@google.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: firmware: Add Open Profile for DICE
Date: Wed, 15 Dec 2021 14:26:08 -0600	[thread overview]
Message-ID: <YbpPYG4rzPmJmwA6@robh.at.kernel.org> (raw)
In-Reply-To: <20211213195833.772892-2-dbrazdil@google.com>

On Mon, Dec 13, 2021 at 07:58:32PM +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 referenced by a compatible device node.
> 
> Signed-off-by: David Brazdil <dbrazdil@google.com>
> ---
>  .../bindings/firmware/google,open-dice.yaml   | 51 +++++++++++++++++++
>  1 file changed, 51 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/firmware/google,open-dice.yaml
> 
> diff --git a/Documentation/devicetree/bindings/firmware/google,open-dice.yaml b/Documentation/devicetree/bindings/firmware/google,open-dice.yaml
> new file mode 100644
> index 000000000000..1aa69f381b8c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/firmware/google,open-dice.yaml
> @@ -0,0 +1,51 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/firmware/google,open-dice.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Open Profile for DICE Device Tree Bindings
> +
> +description: |
> +  This binding represents a reserved memory region containing data
> +  generated by the Open Profile for DICE protocol.
> +
> +  See https://pigweed.googlesource.com/open-dice/
> +
> +maintainers:
> +  - David Brazdil <dbrazdil@google.com>
> +
> +properties:
> +  compatible:
> +    enum:
> +      - google,open-dice
> +
> +  memory-region:
> +    maxItems: 1
> +    description: |
> +      phandle to the reserved memory node to be associated with the device
> +      The reserved memory node should be defined as per the bindings,
> +      Documentation/devicetree/bindings/reserved-memory/reserved-memory.yaml
> +
> +required:
> +  - compatible
> +  - memory-region
> +
> +additionalProperties: false
> +
> +examples:
> +  - |
> +    reserved-memory {
> +        #address-cells = <2>;
> +        #size-cells = <1>;
> +
> +        dice_reserved: dice@12340000 {
> +            reg = <0x00 0x12340000 0x2000>;
> +            no-map;
> +        };
> +    };
> +
> +    dice {
> +        compatible = "google,open-dice";
> +        memory-region = <&dice_reserved>;

There's no need for this indirection. Just add the compatible to the 
dice@12340000 node. You can bind drivers to /reserved-memory nodes.

Rob

  reply	other threads:[~2021-12-15 20:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13 19:58 [PATCH v3 0/2] Driver for Open Profile for DICE David Brazdil
2021-12-13 19:58 ` [PATCH v3 1/2] dt-bindings: firmware: Add " David Brazdil
2021-12-15 20:26   ` Rob Herring [this message]
2021-12-15 21:08     ` David Brazdil
2021-12-16 15:21       ` Rob Herring
2021-12-21 17:43         ` David Brazdil
2021-12-13 19:58 ` [PATCH v3 2/2] misc: open-dice: Add driver to expose DICE data to userspace David Brazdil
2021-12-14  3:25   ` kernel test robot
2021-12-14  3:25     ` kernel test robot
2021-12-14  3:56   ` kernel test robot
2021-12-14  3:56     ` kernel test robot
2021-12-14  7:18   ` Greg Kroah-Hartman
2021-12-14 14:37     ` 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=YbpPYG4rzPmJmwA6@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=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.