From: Tanmay Shah <tanmay.shah@xilinx.com>
To: <mathieu.poirier@linaro.org>, <bjorn.andersson@linaro.org>
Cc: <michal.simek@xilinx.com>, <robh+dt@kernel.org>,
<bill.mills@linaro.org>, <linux-remoteproc@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH v4 2/6] arm64: dts: xilinx: zynqmp: Add RPU subsystem device node
Date: Wed, 20 Apr 2022 00:44:50 -0700 [thread overview]
Message-ID: <20220420074450.2034092-3-tanmay.shah@xilinx.com> (raw)
In-Reply-To: <20220420074450.2034092-1-tanmay.shah@xilinx.com>
RPU subsystem can be configured in cluster-mode or split mode.
Also each r5 core has separate power domains.
Signed-off-by: Tanmay Shah <tanmay.shah@xilinx.com>
---
Changes in v4:
- Add reserved memory region node and use it in RPU subsystem node
Changes in v3:
- Fix checkpatch.pl style warning
arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 35 ++++++++++++++++++++++++++
1 file changed, 35 insertions(+)
diff --git a/arch/arm64/boot/dts/xilinx/zynqmp.dtsi b/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
index c715a18368c2..87d4ce5155c0 100644
--- a/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
+++ b/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
@@ -100,6 +100,22 @@ opp03 {
};
};
+ reserved-memory {
+ #address-cells = <2>;
+ #size-cells = <2>;
+ ranges;
+
+ rproc_0_fw_image: memory@3ed00000 {
+ no-map;
+ reg = <0x0 0x3ed00000 0x0 0x40000>;
+ };
+
+ rproc_1_fw_image: memory@3ef00000 {
+ no-map;
+ reg = <0x0 0x3ef00000 0x0 0x40000>;
+ };
+ };
+
zynqmp_ipi: zynqmp_ipi {
compatible = "xlnx,zynqmp-ipi-mailbox";
interrupt-parent = <&gic>;
@@ -648,6 +664,25 @@ qspi: spi@ff0f0000 {
power-domains = <&zynqmp_firmware PD_QSPI>;
};
+ r5fss: r5fss@ff9a0000 {
+ compatible = "xlnx,zynqmp-r5fss";
+ xlnx,cluster-mode = <1>;
+
+ reg = <0x0 0Xff9a0000 0x0 0x228>;
+
+ r5f_core0: r5f-0 {
+ compatible = "xlnx,zynqmp-r5f";
+ power-domains = <&zynqmp_firmware PD_RPU_0>;
+ memory-region = <&rproc_0_fw_image>;
+ };
+
+ r5f_core1: r5f-1 {
+ compatible = "xlnx,zynqmp-r5f";
+ power-domains = <&zynqmp_firmware PD_RPU_1>;
+ memory-region = <&rproc_1_fw_image>;
+ };
+ };
+
psgtr: phy@fd400000 {
compatible = "xlnx,zynqmp-psgtr-v1.1";
status = "disabled";
--
2.25.1
next prev parent reply other threads:[~2022-04-20 7:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 7:44 [PATCH v4 0/6] Add Xilinx RPU subsystem support Tanmay Shah
2022-04-20 7:44 ` [PATCH v4 1/6] dt-bindings: remoteproc: Add Xilinx RPU subsystem bindings Tanmay Shah
2022-05-02 20:07 ` Rob Herring
2022-04-20 7:44 ` Tanmay Shah [this message]
2022-04-20 7:44 ` [PATCH v4 3/6] firmware: xilinx: Add ZynqMP firmware ioctl enums for RPU configuration Tanmay Shah
2022-04-20 7:44 ` [PATCH v4 4/6] firmware: xilinx: Add shutdown/wakeup APIs Tanmay Shah
2022-04-20 7:44 ` [PATCH v4 5/6] firmware: xilinx: Add RPU configuration APIs Tanmay Shah
2022-04-20 7:44 ` [PATCH v4 6/6] drivers: remoteproc: Add Xilinx r5 remoteproc driver Tanmay Shah
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=20220420074450.2034092-3-tanmay.shah@xilinx.com \
--to=tanmay.shah@xilinx.com \
--cc=bill.mills@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=michal.simek@xilinx.com \
--cc=robh+dt@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).