From: MANNURU VENKATESWARLU <v-mannuru@ti.com>
To: <nm@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <n-francis@ti.com>, <s-k6@ti.com>,
<bb@ti.com>, <v-mannuru@ti.com>
Subject: [RFC PATCH 09/22] arm64: dts: ti: k3-j7200: Add DDR node for j7200
Date: Tue, 14 Jul 2026 18:26:00 +0530 [thread overview]
Message-ID: <20260714125607.3304375-1-v-mannuru@ti.com> (raw)
From: Gandhar Deshpande <g-deshpande@ti.com>
Add device tree node for the DDR controller on the j7200 device.
This defines the memory controller with its register regions, interrupts,
power domains, and clock requirements.
This enables proper DDR controller temperature monitoring.
Signed-off-by: Gandhar Deshpande <g-deshpande@ti.com>
Signed-off-by: Neha Malcom Francis <n-francis@ti.com>
Signed-off-by: MANNURU VENKATESWARLU <v-mannuru@ti.com>
---
arch/arm64/boot/dts/ti/k3-j7200-main.dtsi | 32 +++++++++++++++++++++++
1 file changed, 32 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-j7200-main.dtsi b/arch/arm64/boot/dts/ti/k3-j7200-main.dtsi
index 67fde5667b8d9..db519239129a0 100644
--- a/arch/arm64/boot/dts/ti/k3-j7200-main.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-j7200-main.dtsi
@@ -1556,4 +1556,36 @@ main_esm: esm@700000 {
bootph-pre-ram;
ti,esm-pins = <656>, <657>;
};
+
+ memorycontroller: memorycontroller@2980000 {
+ compatible = "ti,j721e-ddrss";
+ reg = <0x0 0x02990000 0x0 0x4000>,
+ <0x0 0x0114000 0x0 0x100>;
+ reg-names = "cfg", "ctrl_mmr_lp4";
+ power-domains = <&k3_pds 47 TI_SCI_PD_SHARED>,
+ <&k3_pds 90 TI_SCI_PD_SHARED>;
+ interrupts = <GIC_SPI 216 IRQ_TYPE_LEVEL_HIGH>;
+ #address-cells = <2>;
+ #size-cells = <2>;
+ ranges = <0x00 0x0000 0x00 0x02990000 0x00 0x4000>;
+ ti,ddr-freq1 = <0>;
+ ti,ddr-freq2 = <0>;
+ ti,ddr-fhs-cnt = <0>;
+ clocks = <&k3_clks 47 2>, <&k3_clks 30 9>;
+ bootph-pre-ram;
+
+ ddr: ddr@0 {
+ compatible = "cdns,k3-ddr";
+ reg = <0x00 0x0000 0x00 0x72c>,
+ <0x00 0x2000 0x00 0x4b0>,
+ <0x00 0x4000 0x00 0x163c>;
+ reg-names = "ctl_cfg", "ctl_cfg_pi", "ctl_cfg_phy";
+ bootph-pre-ram;
+ };
+
+ ddr_pmu0: ddr-pmu@100 {
+ compatible = "ti,k3-ddr-pmu";
+ reg = <0x00 0x100 0x00 0x14>;
+ };
+ };
};
--
2.34.1
next reply other threads:[~2026-07-14 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 12:56 MANNURU VENKATESWARLU [this message]
2026-07-14 12:56 ` [RFC PATCH 10/22] arm64: dts: ti: k3-j721e: Add DDR and controller node MANNURU VENKATESWARLU
2026-07-14 12:56 ` [RFC PATCH 11/22] arm64: dts: ti: k3-j721s2-main: Add DDR nodes for J721S2 MANNURU VENKATESWARLU
2026-07-14 12:56 ` [RFC PATCH 12/22] arm64: dts: ti: k3-j784s4-main: Add DDR nodes for J784S4 MANNURU VENKATESWARLU
2026-07-14 12:56 ` [RFC PATCH 13/22] arm64: dts: ti: k3-am62: Add DDR and controller node MANNURU VENKATESWARLU
2026-07-14 12:56 ` [RFC PATCH 14/22] arm64: dts: ti: k3-am62a: " MANNURU VENKATESWARLU
2026-07-14 12:56 ` [RFC PATCH 15/22] arm64: dts: ti: k3-am62p: " MANNURU VENKATESWARLU
2026-07-14 12:56 ` [RFC PATCH 16/22] arm64: dts: ti: k3-am64: " MANNURU VENKATESWARLU
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=20260714125607.3304375-1-v-mannuru@ti.com \
--to=v-mannuru@ti.com \
--cc=bb@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=n-francis@ti.com \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=s-k6@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