From: Nishanth Menon <nm@ti.com>
To: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Tero Kristo <kristo@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>, Nishanth Menon <nm@ti.com>,
Udit Kumar <u-kumar1@ti.com>, Nitin Yadav <n-yadav@ti.com>,
Andrew Davis <afd@ti.com>
Subject: [PATCH 4/7] arm64: dts: ti: k3-j7200-mcu: Add mcu_secproxy
Date: Tue, 30 May 2023 11:58:57 -0500 [thread overview]
Message-ID: <20230530165900.47502-5-nm@ti.com> (raw)
In-Reply-To: <20230530165900.47502-1-nm@ti.com>
MCU domain has it's own secure proxy for communicating with ROM and
for R5 micro controller firmware operations. This is in addition to
the one in the main domain NAVSS subsystem that is used for general
purpose communication.
Describe the node for use with bootloaders and firmware that require
this communication path which uses interrupts to corresponding micro
controller interrupt controller. Mark the node as disabled since this
instance does not have interrupts routed to the main processor by
default for a complete description of the node.
Signed-off-by: Nishanth Menon <nm@ti.com>
---
New patch
arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
index 674e695ef844..dff23b258240 100644
--- a/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi
@@ -209,6 +209,21 @@ mcu_udmap: dma-controller@285c0000 {
};
};
+ secure_proxy_mcu: mailbox@2a480000 {
+ compatible = "ti,am654-secure-proxy";
+ #mbox-cells = <1>;
+ reg-names = "target_data", "rt", "scfg";
+ reg = <0x0 0x2a480000 0x0 0x80000>,
+ <0x0 0x2a380000 0x0 0x80000>,
+ <0x0 0x2a400000 0x0 0x80000>;
+ /*
+ * Marked Disabled:
+ * Node is incomplete as it is meant for bootloaders and
+ * firmware on non-MPU processors
+ */
+ status = "disabled";
+ };
+
mcu_cpsw: ethernet@46000000 {
compatible = "ti,j721e-cpsw-nuss";
#address-cells = <2>;
--
2.40.0
next prev parent reply other threads:[~2023-05-30 16:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 16:58 [PATCH 0/7] arm64: dts: ti: Add additional secproxy instances Nishanth Menon
2023-05-30 16:58 ` [PATCH 1/7] arm64: dts: ti: k3-am62-main: Add sa3_secproxy Nishanth Menon
2023-05-30 16:58 ` [PATCH 2/7] arm64: dts: ti: k3-am62a-main: " Nishanth Menon
2023-05-30 16:58 ` [PATCH 3/7] arm64: dts: ti: k3-am65-mcu: Add mcu_secproxy Nishanth Menon
2023-05-30 16:58 ` Nishanth Menon [this message]
2023-05-31 17:07 ` [PATCH 4/7] arm64: dts: ti: k3-j7200-mcu: " Kumar, Udit
2023-05-31 17:39 ` Nishanth Menon
2023-06-06 13:08 ` Kumar, Udit
2023-05-30 16:58 ` [PATCH 5/7] arm64: dts: ti: k3-j721e-mcu: " Nishanth Menon
2023-05-30 16:58 ` [PATCH 6/7] arm64: dts: ti: k3-j721s2-mcu-wakeup: Add sa3_secproxy and mcu_sec_proxy Nishanth Menon
2023-05-30 16:59 ` [PATCH 7/7] arm64: dts: ti: k3-j784s4-mcu-wakeup: " Nishanth Menon
2023-06-15 13:13 ` [PATCH 0/7] arm64: dts: ti: Add additional secproxy instances Vignesh Raghavendra
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=20230530165900.47502-5-nm@ti.com \
--to=nm@ti.com \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=n-yadav@ti.com \
--cc=robh+dt@kernel.org \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.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