From: Andrew Davis <afd@ti.com>
To: Judith Mendez <jm@ti.com>, 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>,
Devarsh Thakkar <devarsht@ti.com>, Hari Nagalla <hnagalla@ti.com>
Subject: Re: [PATCH 2/4] arm64: dts: ti: k3-am62a-mcu: Add R5F remote proc node
Date: Tue, 28 Jan 2025 10:27:42 -0600 [thread overview]
Message-ID: <8b152f81-0848-4f34-adcb-fee9b4f2fd7f@ti.com> (raw)
In-Reply-To: <20250127221631.3974583-3-jm@ti.com>
On 1/27/25 4:16 PM, Judith Mendez wrote:
> From: Hari Nagalla <hnagalla@ti.com>
>
> AM62A SoCs have a single R5F core in the MCU voltage domain. The MCU
> domain also has a 512KB sram memory, the R5F core can use for
> applications needing fast memory access.
>
> Signed-off-by: Hari Nagalla <hnagalla@ti.com>
> [Judith: Fix commit message header]
> Signed-off-by: Judith Mendez <jm@ti.com>
> ---
> arch/arm64/boot/dts/ti/k3-am62a-mcu.dtsi | 36 ++++++++++++++++++++++++
> 1 file changed, 36 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..9a20f75e48063 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62a-mcu.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am62a-mcu.dtsi
> @@ -6,6 +6,18 @@
> */
>
> &cbass_mcu {
> + mcu_ram: sram@79100000 {
> + compatible = "mmio-sram";
> + reg = <0x00 0x79100000 0x00 0x80000>;
> + ranges = <0x00 0x00 0x79100000 0x80000>;
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + mcu1-sram@0 {
> + reg = <0x0 0x80000>;
> + };
> + };
> +
> mcu_pmx0: pinctrl@4084000 {
> compatible = "pinctrl-single";
> reg = <0x00 0x04084000 0x00 0x88>;
> @@ -175,4 +187,28 @@ 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>;
Newline here.
Also this should be default "disabled". It can be set to "okay"
in the board DTS file when the needed mboxes and memory-region
are set. Speaking of that, where are those patches? This is
incomplete without them and these nodes will not function.
Same for the DSP patch.
Andrew
> + 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>;
> + sram = <&mcu_ram>;
> + };
> + };
> };
next prev parent reply other threads:[~2025-01-28 16:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 22:16 [PATCH 0/4] Add R5F and C7xv device nodes Judith Mendez
2025-01-27 22:16 ` [PATCH 1/4] arm64: dts: ti: k3-am62-wakeup: Add wakeup r5f node Judith Mendez
2025-01-28 16:22 ` Andrew Davis
2025-01-28 16:27 ` Judith Mendez
2025-01-27 22:16 ` [PATCH 2/4] arm64: dts: ti: k3-am62a-mcu: Add R5F remote proc node Judith Mendez
2025-01-28 16:27 ` Andrew Davis [this message]
2025-01-28 16:52 ` Hari Nagalla
2025-01-28 17:48 ` Judith Mendez
2025-01-30 22:40 ` Judith Mendez
2025-01-31 18:25 ` Andrew Davis
2025-01-27 22:16 ` [PATCH 3/4] arm64: dts: ti: k3-am62a-wakeup: Add R5F device node Judith Mendez
2025-01-27 22:16 ` [PATCH 4/4] arm64: dts: ti: k3-am62a-main: Add C7xv " Judith Mendez
2025-01-27 22:37 ` [PATCH 0/4] Add R5F and C7xv device nodes Rob Herring (Arm)
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=8b152f81-0848-4f34-adcb-fee9b4f2fd7f@ti.com \
--to=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=hnagalla@ti.com \
--cc=jm@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