From: franck.lenormand@oss.nxp.com
To: shawnguo@kernel.org, s.hauer@pengutronix.de, festevam@gmail.com
Cc: aisheng.dong@nxp.com, peng.fan@nxp.com, qiangqing.zhang@nxp.com,
abel.vesa@nxp.com, Anson.Huang@nxp.com,
linux-kernel@vger.kernel.org, linux@rempel-privat.de,
linux-imx@nxp.com, kernel@pengutronix.de,
franck.lenormand@oss.nxp.com, daniel.baluta@nxp.com,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 4/5] dt-bindings: arm: imx: Documentation of the SC secvio driver
Date: Thu, 10 Dec 2020 09:48:49 +0100 [thread overview]
Message-ID: <1607590130-11065-5-git-send-email-franck.lenormand@oss.nxp.com> (raw)
In-Reply-To: <1607590130-11065-1-git-send-email-franck.lenormand@oss.nxp.com>
From: Franck LENORMAND <franck.lenormand@nxp.com>
This patch adds the documentation for the security violation
driver using the SCU on imx8x and imx8q.
Signed-off-by: Franck LENORMAND <franck.lenormand@nxp.com>
---
.../bindings/arm/freescale/fsl,imx-sc-secvio.yaml | 34 ++++++++++++++++++++++
1 file changed, 34 insertions(+)
create mode 100644 Documentation/devicetree/bindings/arm/freescale/fsl,imx-sc-secvio.yaml
diff --git a/Documentation/devicetree/bindings/arm/freescale/fsl,imx-sc-secvio.yaml b/Documentation/devicetree/bindings/arm/freescale/fsl,imx-sc-secvio.yaml
new file mode 100644
index 0000000..8037395
--- /dev/null
+++ b/Documentation/devicetree/bindings/arm/freescale/fsl,imx-sc-secvio.yaml
@@ -0,0 +1,34 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/arm/freescale/fsl,imx-sc-secvio.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: NXP i.MX Security Violation driver
+
+maintainers:
+ - Franck LENORMAND <franck.lenormand@nxp.com>
+
+description: |
+ Receive security violation from the SNVS via the SCU firmware. Allow to
+ register notifier for additional processing
+
+properties:
+ compatible:
+ enum:
+ - fsl,imx-sc-secvio
+ nvmem:
+ $ref: http://devicetree.org/schemas/nvmem/nvmem-consumer.yaml
+ description:
+ Phandle to the nvmem provider.
+
+required:
+ - compatible
+ - nvmem
+
+examples:
+ - |
+ sc_secvio: sc-secvio
+ compatible = "fsl,imx-sc-secvio";
+ nvmem = <&ocotp>
+ };
--
2.7.4
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-12-10 8:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 8:48 [PATCH v4 0/5] Add support of SECVIO from SNVS on iMX8q/x franck.lenormand
2020-12-10 8:48 ` [PATCH v4 1/5] firmware: imx: scu-seco: Add Secure Controller APIS franck.lenormand
2020-12-10 8:48 ` [PATCH v4 2/5] firmware: imx: scu-irq: Add API to retrieve status of IRQ franck.lenormand
2020-12-10 8:48 ` [PATCH v4 3/5] dt-bindings: firmware: imx-scu: Add SECVIO resource franck.lenormand
2020-12-10 8:48 ` franck.lenormand [this message]
2020-12-10 8:48 ` [PATCH v4 5/5] soc: imx8: Add the SC SECVIO driver franck.lenormand
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=1607590130-11065-5-git-send-email-franck.lenormand@oss.nxp.com \
--to=franck.lenormand@oss.nxp.com \
--cc=Anson.Huang@nxp.com \
--cc=abel.vesa@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=daniel.baluta@nxp.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=peng.fan@nxp.com \
--cc=qiangqing.zhang@nxp.com \
--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).