The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Judith Mendez <jm@ti.com>
To: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Andrew Davis <afd@ti.com>, Hari Nagalla <hnagalla@ti.com>,
	Judith Mendez <jm@ti.com>
Subject: [PATCH v5 02/10] arm64: dts: ti: k3-am62a-mcu: Add R5F remote proc node
Date: Mon, 10 Feb 2025 16:15:22 -0600	[thread overview]
Message-ID: <20250210221530.1234009-3-jm@ti.com> (raw)
In-Reply-To: <20250210221530.1234009-1-jm@ti.com>

From: Hari Nagalla <hnagalla@ti.com>

AM62A SoCs have a single R5F core in the MCU voltage domain.
Add the R5FSS node with the child node for core0 in MCU voltage
domain .dtsi file.

Signed-off-by: Hari Nagalla <hnagalla@ti.com>
Signed-off-by: Judith Mendez <jm@ti.com>
---
Changes since v4:
- Drop SRAM node for am62ax MCU R5fSS0 core0
---
 arch/arm64/boot/dts/ti/k3-am62a-mcu.dtsi | 25 ++++++++++++++++++++++++
 1 file changed, 25 insertions(+)

diff --git a/arch/arm64/boot/dts/ti/k3-am62a-mcu.dtsi b/arch/arm64/boot/dts/ti/k3-am62a-mcu.dtsi
index 0469c766b769e..1178cc6a9be8c 100644
--- a/arch/arm64/boot/dts/ti/k3-am62a-mcu.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62a-mcu.dtsi
@@ -175,4 +175,29 @@ mcu_mcan1: can@4e18000 {
 		bosch,mram-cfg = <0x0 128 64 64 64 64 32 32>;
 		status = "disabled";
 	};
+
+	mcu_r5fss0: r5fss@79000000 {
+		compatible = "ti,am62-r5fss";
+		#address-cells = <1>;
+		#size-cells = <1>;
+		ranges = <0x79000000 0x00 0x79000000 0x8000>,
+			 <0x79020000 0x00 0x79020000 0x8000>;
+		power-domains = <&k3_pds 7 TI_SCI_PD_EXCLUSIVE>;
+		status = "disabled";
+
+		mcu_r5fss0_core0: r5f@79000000 {
+			compatible = "ti,am62-r5f";
+			reg = <0x79000000 0x00008000>,
+			      <0x79020000 0x00008000>;
+			reg-names = "atcm", "btcm";
+			ti,sci = <&dmsc>;
+			ti,sci-dev-id = <9>;
+			ti,sci-proc-ids = <0x03 0xff>;
+			resets = <&k3_reset 9 1>;
+			firmware-name = "am62a-mcu-r5f0_0-fw";
+			ti,atcm-enable = <0>;
+			ti,btcm-enable = <1>;
+			ti,loczrama = <0>;
+		};
+	};
 };
-- 
2.48.0


  parent reply	other threads:[~2025-02-10 22:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10 22:15 [PATCH v5 00/10] Add R5F and C7xv device nodes Judith Mendez
2025-02-10 22:15 ` [PATCH v5 01/10] arm64: dts: ti: k3-am62-wakeup: Add wakeup R5F node Judith Mendez
2025-02-10 22:58   ` Andrew Davis
2025-02-19 16:30   ` Beleswar Prasad Padhi
2025-02-20 16:34     ` Judith Mendez
2025-02-10 22:15 ` Judith Mendez [this message]
2025-02-10 22:58   ` [PATCH v5 02/10] arm64: dts: ti: k3-am62a-mcu: Add R5F remote proc node Andrew Davis
2025-02-10 22:15 ` [PATCH v5 03/10] arm64: dts: ti: k3-am62a-wakeup: Add R5F device node Judith Mendez
2025-02-10 22:58   ` Andrew Davis
2025-02-10 22:15 ` [PATCH v5 04/10] arm64: dts: ti: k3-am62a-main: Add C7xv " Judith Mendez
2025-02-10 22:58   ` Andrew Davis
2025-02-10 22:15 ` [PATCH v5 05/10] arm64: dts: ti: k3-am62a7-sk: Enable IPC with remote processors Judith Mendez
2025-02-10 22:59   ` Andrew Davis
2025-02-10 22:15 ` [PATCH v5 06/10] arm64: dts: ti: k3-am62p5-sk: " Judith Mendez
2025-02-18 16:38   ` Andrew Davis
2025-02-18 17:51     ` Judith Mendez
2025-02-27 12:05       ` Devarsh Thakkar
2025-03-07  1:35         ` Judith Mendez
2025-02-10 22:15 ` [PATCH v5 07/10] arm64: dts: ti: k3-am62x-sk-common: " Judith Mendez
2025-02-10 22:15 ` [PATCH v5 08/10] arm64: dts: ti: k3-am62a7-sk: Reserve main_timer2 for C7x DSP Judith Mendez
2025-02-10 22:15 ` [PATCH v5 09/10] arm64: dts: ti: k3-am62a7-sk: Reserve main_rti4 " Judith Mendez
2025-02-10 22:15 ` [PATCH v5 10/10] arm64: dts: ti: k3-am64: Reserve timers used by MCU FW Judith Mendez
2025-03-07 22:25 ` [PATCH v5 00/10] Add R5F and C7xv device nodes Judith Mendez

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=20250210221530.1234009-3-jm@ti.com \
    --to=jm@ti.com \
    --cc=afd@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hnagalla@ti.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --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