All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Stanley <joel@jms.id.au>
To: Andrew Jeffery <andrew@aj.id.u>, Rob Herring <robh+dt@kernel.org>
Cc: Ryan Chen <ryan_chen@aspeedtech.com>,
	Paul Menzel <pmenzel@molgen.mpg.de>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org
Subject: [PATCH 1/3] dt-bindings: aspeed: Add Secure Boot Controller bindings
Date: Wed, 17 Nov 2021 11:51:04 +0800	[thread overview]
Message-ID: <20211117035106.321454-2-joel@jms.id.au> (raw)
In-Reply-To: <20211117035106.321454-1-joel@jms.id.au>

The secure boot controller was first introduced in the AST2600.

Signed-off-by: Joel Stanley <joel@jms.id.au>
---
 .../bindings/arm/aspeed/aspeed,sbc.yaml       | 37 +++++++++++++++++++
 1 file changed, 37 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/arm/aspeed/aspeed,sbc.yaml

diff --git a/Documentation/devicetree/bindings/arm/aspeed/aspeed,sbc.yaml b/Documentation/devicetree/bindings/arm/aspeed/aspeed,sbc.yaml
new file mode 100644
index 000000000000..c72aab706484
--- /dev/null
+++ b/Documentation/devicetree/bindings/arm/aspeed/aspeed,sbc.yaml
@@ -0,0 +1,37 @@
+# SPDX-License-Identifier: (GPL-2.0-or-later OR BSD-2-Clause)
+# Copyright 2021 Joel Stanley, IBM Corp.
+%YAML 1.2
+---
+$id: "http://devicetree.org/schemas/arm/aspeed/aspeed,sbc.yaml#"
+$schema: "http://devicetree.org/meta-schemas/core.yaml#"
+
+title: ASPEED Secure Boot Controller
+
+maintainers:
+  - Joel Stanley <joel@jms.id.au>
+  - Andrew Jeffery <andrew@aj.id.au>
+
+description: |
+  The ASPEED SoCs have a register bank for interacting with the secure boot
+  controller.
+
+properties:
+  compatible:
+    items:
+      - const: aspeed,ast2600-sbc
+
+  reg:
+    maxItems: 1
+
+required:
+  - compatible
+  - reg
+
+additionalProperties: false
+
+examples:
+  - |
+    sbc: secure-boot-controller@1e6f2000 {
+            compatible = "aspeed,ast2600-sbc";
+            reg = <0x1e6f2000 0x1000>;
+    };
-- 
2.33.0


WARNING: multiple messages have this Message-ID (diff)
From: Joel Stanley <joel@jms.id.au>
To: Andrew Jeffery <andrew@aj.id.u>, Rob Herring <robh+dt@kernel.org>
Cc: Ryan Chen <ryan_chen@aspeedtech.com>,
	Paul Menzel <pmenzel@molgen.mpg.de>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org
Subject: [PATCH 1/3] dt-bindings: aspeed: Add Secure Boot Controller bindings
Date: Wed, 17 Nov 2021 11:51:04 +0800	[thread overview]
Message-ID: <20211117035106.321454-2-joel@jms.id.au> (raw)
In-Reply-To: <20211117035106.321454-1-joel@jms.id.au>

The secure boot controller was first introduced in the AST2600.

Signed-off-by: Joel Stanley <joel@jms.id.au>
---
 .../bindings/arm/aspeed/aspeed,sbc.yaml       | 37 +++++++++++++++++++
 1 file changed, 37 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/arm/aspeed/aspeed,sbc.yaml

diff --git a/Documentation/devicetree/bindings/arm/aspeed/aspeed,sbc.yaml b/Documentation/devicetree/bindings/arm/aspeed/aspeed,sbc.yaml
new file mode 100644
index 000000000000..c72aab706484
--- /dev/null
+++ b/Documentation/devicetree/bindings/arm/aspeed/aspeed,sbc.yaml
@@ -0,0 +1,37 @@
+# SPDX-License-Identifier: (GPL-2.0-or-later OR BSD-2-Clause)
+# Copyright 2021 Joel Stanley, IBM Corp.
+%YAML 1.2
+---
+$id: "http://devicetree.org/schemas/arm/aspeed/aspeed,sbc.yaml#"
+$schema: "http://devicetree.org/meta-schemas/core.yaml#"
+
+title: ASPEED Secure Boot Controller
+
+maintainers:
+  - Joel Stanley <joel@jms.id.au>
+  - Andrew Jeffery <andrew@aj.id.au>
+
+description: |
+  The ASPEED SoCs have a register bank for interacting with the secure boot
+  controller.
+
+properties:
+  compatible:
+    items:
+      - const: aspeed,ast2600-sbc
+
+  reg:
+    maxItems: 1
+
+required:
+  - compatible
+  - reg
+
+additionalProperties: false
+
+examples:
+  - |
+    sbc: secure-boot-controller@1e6f2000 {
+            compatible = "aspeed,ast2600-sbc";
+            reg = <0x1e6f2000 0x1000>;
+    };
-- 
2.33.0


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-11-17  3:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17  3:51 [PATCH 0/3] ARM: aspeed: Secure Boot Controller support Joel Stanley
2021-11-17  3:51 ` Joel Stanley
2021-11-17  3:51 ` Joel Stanley [this message]
2021-11-17  3:51   ` [PATCH 1/3] dt-bindings: aspeed: Add Secure Boot Controller bindings Joel Stanley
2021-11-29 22:41   ` Rob Herring
2021-11-29 22:41     ` Rob Herring
2021-11-17  3:51 ` [PATCH 2/3] ARM: dts: aspeed: Add secure boot controller node Joel Stanley
2021-11-17  3:51   ` Joel Stanley
2021-11-17  3:51 ` [PATCH 3/3] ARM: aspeed: Add secure boot controller support Joel Stanley
2021-11-17  3:51   ` Joel Stanley
2021-11-25  8:38   ` kernel test robot
2021-11-25  8:38     ` kernel test robot
2021-11-25  8:38     ` kernel test robot
2022-01-10 23:29   ` Joel Stanley
2022-01-10 23:29     ` Joel Stanley
2022-01-17 14:51     ` Arnd Bergmann
2022-01-17 14:51       ` Arnd Bergmann

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=20211117035106.321454-2-joel@jms.id.au \
    --to=joel@jms.id.au \
    --cc=andrew@aj.id.u \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=pmenzel@molgen.mpg.de \
    --cc=robh+dt@kernel.org \
    --cc=ryan_chen@aspeedtech.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 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.