linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Pankaj Gupta <pankaj.gupta@nxp.com>
To: Jonathan Corbet <corbet@lwn.net>, Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	 Sascha Hauer <s.hauer@pengutronix.de>,
	 Pengutronix Kernel Team <kernel@pengutronix.de>,
	 Fabio Estevam <festevam@gmail.com>,
	Pankaj Gupta <pankaj.gupta@nxp.com>,
	 Rob Herring <robh+dt@kernel.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	 devicetree@vger.kernel.org, imx@lists.linux.dev,
	 linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 2/5] dt-bindings: arm: fsl: add imx-se-fw binding doc
Date: Fri, 12 Jul 2024 11:49:57 +0530	[thread overview]
Message-ID: <20240712-imx-se-if-v5-2-66a79903a872@nxp.com> (raw)
In-Reply-To: <20240712-imx-se-if-v5-0-66a79903a872@nxp.com>

The NXP security hardware IP(s) like: i.MX EdgeLock Enclave, V2X etc.,
creates an embedded secure enclave within the SoC boundary to enable
features like:
- HSM
- SHE
- V2X

Secure-Enclave(s) communication interface are typically via message
unit, i.e., based on mailbox linux kernel driver. This driver enables
communication ensuring well defined message sequence protocol between
Application Core and enclave's firmware.

Driver configures multiple misc-device on the MU, for multiple
user-space applications, to be able to communicate over single MU.

It exists on some i.MX processors. e.g. i.MX8ULP, i.MX93 etc.

Signed-off-by: Pankaj Gupta <pankaj.gupta@nxp.com>
---
 .../devicetree/bindings/firmware/fsl,imx-se.yaml   | 111 +++++++++++++++++++++
 1 file changed, 111 insertions(+)

diff --git a/Documentation/devicetree/bindings/firmware/fsl,imx-se.yaml b/Documentation/devicetree/bindings/firmware/fsl,imx-se.yaml
new file mode 100644
index 000000000000..bd99505de6e6
--- /dev/null
+++ b/Documentation/devicetree/bindings/firmware/fsl,imx-se.yaml
@@ -0,0 +1,111 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/firmware/fsl,imx-se.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: NXP i.MX HW Secure Enclave(s) EdgeLock Enclave
+
+maintainers:
+  - Pankaj Gupta <pankaj.gupta@nxp.com>
+
+description: |
+  NXP's SoC may contain one or multiple embedded secure-enclave HW
+  IP(s) like i.MX EdgeLock Enclave, V2X etc. These NXP's HW IP(s)
+  enables features like
+    - Hardware Security Module (HSM),
+    - Security Hardware Extension (SHE), and
+    - Vehicular to Anything (V2X)
+
+  Communication interface to the secure-enclaves is based on the
+  messaging unit(s).
+
+properties:
+  $nodename:
+    pattern: "firmware@[0-9a-f]+$"
+
+  compatible:
+    enum:
+      - fsl,imx8ulp-se
+      - fsl,imx93-se
+      - fsl,imx95-se
+
+  reg:
+    maxItems: 1
+    description: Identifier of the communication interface to secure-enclave.
+
+  mboxes:
+    items:
+      - description: mailbox phandle to send message to se firmware
+      - description: mailbox phandle to receive message from se firmware
+
+  mbox-names:
+    description: two names are to be listed, one for rx and other one for tx.
+      The name can be any of the below list.
+    items:
+      - const: tx
+      - const: rx
+
+  memory-region:
+    items:
+      - description: The phandle to the reserved external memory, the only
+          accessible memoryregion to secure enclave(SE) firmware. It is an
+          optional property based on compatible.
+          (see bindings/reserved-memory/reserved-memory.txt)
+
+  sram:
+    items:
+      - description: It is an optional property based on compatible.
+
+required:
+  - compatible
+  - reg
+  - mboxes
+  - mbox-names
+
+allOf:
+  # memory-region
+  - if:
+      properties:
+        compatible:
+          contains:
+            enum:
+              - fsl,imx8ulp-se
+              - fsl,imx93-se
+    then:
+      required:
+        - memory-region
+    else:
+      properties:
+        memory-region: false
+
+  # sram
+  - if:
+      properties:
+        compatible:
+          contains:
+            enum:
+              - fsl,imx8ulp-se
+    then:
+      required:
+        - sram
+
+    else:
+      properties:
+        sram: false
+
+additionalProperties: false
+
+examples:
+  - |
+    firmware {
+      #address-cells = <1>;
+      #size-cells = <0>;
+      firmware@0 {
+        compatible = "fsl,imx95-se";
+        reg = <0x0>;
+        mboxes = <&ele_mu0 0 0>, <&ele_mu0 1 0>;
+        mbox-names = "tx", "rx";
+      };
+    };
+...

-- 
2.34.1



  parent reply	other threads:[~2024-07-12  6:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-12  6:19 [PATCH v5 0/5] Changes in v5: Pankaj Gupta
2024-07-12  6:19 ` [PATCH v5 1/5] Documentation/firmware: add imx/se to other_interfaces Pankaj Gupta
2024-07-12  6:19 ` Pankaj Gupta [this message]
2024-07-12 18:03   ` [PATCH v5 2/5] dt-bindings: arm: fsl: add imx-se-fw binding doc Rob Herring
2024-07-15  7:56     ` [EXT] " Pankaj Gupta
2024-07-18  5:11       ` Pankaj Gupta
2024-07-19 10:08         ` Pankaj Gupta
2024-07-12  6:19 ` [PATCH v5 3/5] arm64: dts: imx8ulp-evk: add nxp secure enclave firmware Pankaj Gupta
2024-07-12  6:19 ` [PATCH v5 4/5] firmware: imx: add driver for NXP EdgeLock Enclave Pankaj Gupta
2024-07-12 18:42   ` Markus Elfring
2024-07-13 17:56   ` Amit Singh Tomar
2024-07-15  9:02     ` [EXT] " Pankaj Gupta
2024-07-16  3:20       ` Amit Singh Tomar
2024-07-12  6:20 ` [PATCH v5 5/5] firmware: imx: adds miscdev Pankaj Gupta
2024-07-12 22:19   ` Frank Li
2024-07-15 10:56     ` Sascha Hauer
2024-07-16  4:50     ` Pankaj Gupta
2024-07-16 12:54       ` Fabio Estevam
2024-07-15  7:24   ` Amit Singh Tomar
2024-07-15  9:03     ` [EXT] " Pankaj Gupta
2024-07-16  3:30       ` Amit Singh Tomar
2024-07-12 18:15 ` [PATCH v5 0/5] Changes in v5: Markus Elfring

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=20240712-imx-se-if-v5-2-66a79903a872@nxp.com \
    --to=pankaj.gupta@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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).