From: Vabhav Sharma <vabhav.sharma@nxp.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Franck LENORMAND <franck.lenormand@nxp.com>,
Dong Aisheng <aisheng.dong@nxp.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Peng Fan <peng.fan@nxp.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Varun Sethi <V.Sethi@nxp.com>,
Silvano Di Ninno <silvano.dininno@nxp.com>,
Pankaj Gupta <pankaj.gupta@nxp.com>,
frank.li@nxp.com, daniel.baluta@nxp.com,
Vabhav Sharma <vabhav.sharma@nxp.com>
Subject: [PATCH 4/4] arm64: dts: imx8q: Add node for Security Violation
Date: Thu, 09 May 2024 02:45:35 +0200 [thread overview]
Message-ID: <20240509-secvio-v1-4-90fbe2baeda2@nxp.com> (raw)
In-Reply-To: <20240509-secvio-v1-0-90fbe2baeda2@nxp.com>
Add secvio node definition for imx8qxp.
Signed-off-by: Franck LENORMAND <franck.lenormand@nxp.com>
Signed-off-by: Vabhav Sharma <vabhav.sharma@nxp.com>
---
arch/arm64/boot/dts/freescale/imx8qxp.dtsi | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/imx8qxp.dtsi b/arch/arm64/boot/dts/freescale/imx8qxp.dtsi
index 0313f295de2e..09d3e11eef3f 100644
--- a/arch/arm64/boot/dts/freescale/imx8qxp.dtsi
+++ b/arch/arm64/boot/dts/freescale/imx8qxp.dtsi
@@ -241,6 +241,11 @@ rtc: rtc {
compatible = "fsl,imx8qxp-sc-rtc";
};
+ secvio: secvio {
+ compatible = "fsl,imx-sc-secvio";
+ nvmem = <&ocotp>;
+ };
+
watchdog {
compatible = "fsl,imx8qxp-sc-wdt", "fsl,imx-sc-wdt";
timeout-sec = <60>;
--
2.25.1
next prev parent reply other threads:[~2024-05-09 0:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 0:45 [PATCH 0/4] soc: imx: secvio: Add secvio support Vabhav Sharma
2024-05-09 0:45 ` [PATCH 1/4] dt-bindings: firmware: secvio: Add device tree bindings Vabhav Sharma
2024-05-09 3:06 ` Frank Li
2024-05-09 5:54 ` Krzysztof Kozlowski
2024-06-07 5:00 ` [EXT] " Vabhav Sharma
2024-06-07 5:08 ` Vabhav Sharma
2024-05-09 5:53 ` Krzysztof Kozlowski
2024-06-07 4:58 ` [EXT] " Vabhav Sharma
2024-06-07 7:07 ` Krzysztof Kozlowski
2024-06-12 7:20 ` Aisheng Dong
2024-06-13 6:13 ` Krzysztof Kozlowski
2024-06-13 8:48 ` Aisheng Dong
2024-06-16 7:33 ` Krzysztof Kozlowski
2024-06-17 10:11 ` Aisheng Dong
2024-06-17 12:11 ` Krzysztof Kozlowski
2024-05-09 0:45 ` [PATCH 2/4] firmware: imx: Add SC APIs required for secvio module Vabhav Sharma
2024-05-09 0:45 ` [PATCH 3/4] soc: imx: secvio: Add support for SNVS secvio and tamper via SCFW Vabhav Sharma
2024-05-09 0:45 ` Vabhav Sharma [this message]
2024-05-09 5:51 ` [PATCH 0/4] soc: imx: secvio: Add secvio support Krzysztof Kozlowski
2024-06-07 4:52 ` [EXT] " Vabhav Sharma
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=20240509-secvio-v1-4-90fbe2baeda2@nxp.com \
--to=vabhav.sharma@nxp.com \
--cc=V.Sethi@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=franck.lenormand@nxp.com \
--cc=frank.li@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.gupta@nxp.com \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=silvano.dininno@nxp.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 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).