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";
+ 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>,
--
2.48.0On 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>,
Hi Andrew,
On 1/28/25 10:22 AM, Andrew Davis wrote:
> 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.
Understood, will respin with fixed name, thanks.
~ Judith
>
> 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>,
© 2016 - 2026 Red Hat, Inc.