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 1/4] arm64: dts: ti: k3-am62-wakeup: Add wakeup r5f node
Date: Tue, 28 Jan 2025 10:22:04 -0600 [thread overview]
Message-ID: <950a1e23-a943-41b0-979a-4e7a4a264fdd@ti.com> (raw)
In-Reply-To: <20250127221631.3974583-2-jm@ti.com>
On 1/27/25 4:16 PM, Judith Mendez wrote:
> From: Hari Nagalla <hnagalla@ti.com>
>
> AM62 SoC devices have a single core R5F processor in wakeup domain.
> The R5F processor in wakeup domain is used as a device manager
> for the SoC.
>
> Co-authored-by: Devarsh Thakkar <devarsht@ti.com>
> 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-am62-wakeup.dtsi | 24 ++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi
> index 9b8a1f85aa15c..79708c1c214f8 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi
> @@ -106,6 +106,30 @@ wkup_rti0: watchdog@2b000000 {
> status = "reserved";
> };
>
> + wkup_r5fss0: r5fss@78000000 {
> + compatible = "ti,am62-r5fss";
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges = <0x78000000 0x00 0x78000000 0x8000>,
> + <0x78100000 0x00 0x78100000 0x8000>;
> + power-domains = <&k3_pds 119 TI_SCI_PD_EXCLUSIVE>;
> +
> + wkup_r5fss0_core0: r5f@78000000 {
> + compatible = "ti,am62-r5f";
> + reg = <0x78000000 0x00008000>,
> + <0x78100000 0x00008000>;
> + reg-names = "atcm", "btcm";
> + ti,sci = <&dmsc>;
> + ti,sci-dev-id = <121>;
> + ti,sci-proc-ids = <0x01 0xff>;
> + resets = <&k3_reset 121 1>;
> + firmware-name = "ti-sysfw/ti-fs-stub-firmware-am62x-gp-signed.bin";
What is this firmware name? This doesn't exist in linux-firmware,
should use the normal name like "am62-wkup-r5f0_0-fw", then we
can use symlinks in our userspace to map to whatever firmware we
want to run.
Andrew
> + ti,atcm-enable = <1>;
> + ti,btcm-enable = <1>;
> + ti,loczrama = <1>;
> + };
> + };
> +
> wkup_vtm0: temperature-sensor@b00000 {
> compatible = "ti,j7200-vtm";
> reg = <0x00 0xb00000 0x00 0x400>,
next prev parent reply other threads:[~2025-01-28 16:22 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 [this message]
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
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=950a1e23-a943-41b0-979a-4e7a4a264fdd@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