* Re: [PATCH v2] arm64: dts: ti: k3-am62-main: Add PRUSS-M node
2025-04-30 14:43 [PATCH v2] arm64: dts: ti: k3-am62-main: Add PRUSS-M node Judith Mendez
@ 2025-04-30 16:32 ` Hari Nagalla
2025-05-02 12:24 ` Nishanth Menon
` (3 subsequent siblings)
4 siblings, 0 replies; 7+ messages in thread
From: Hari Nagalla @ 2025-04-30 16:32 UTC (permalink / raw)
To: Judith Mendez, Nishanth Menon, Vignesh Raghavendra
Cc: Tero Kristo, Rob Herring, Krzysztof Kozlowski, Conor Dooley,
linux-arm-kernel, devicetree, linux-kernel, Beleswar Padhi
On 4/30/25 09:43, Judith Mendez wrote:
> From: Kishon Vijay Abraham I <kishon@ti.com>
>
> Add the DT node for the PRUSS-M processor subsystem that is present
> on the K3 AM62x SoCs. The K3 AM62x family of SoC has one PRUSS-M
> instance and it has two Programmable Real-Time Units (PRU0 and PRU1).
>
> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
> [ Judith: Fix pruss_iclk id for pruss_coreclk_mux ]
> Signed-off-by: Judith Mendez <jm@ti.com>
> ---
Acked-by: Hari Nagalla <hnagalla@ti.com>
> Changelog:
> - drop internal tags
> - rebase against ti-k3-dts-next
> - fix header
>
> Link to v1:
> https://lore.kernel.org/linux-devicetree/20250108222048.818835-1-jm@ti.com/
> ---
> arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 90 ++++++++++++++++++++++++
> 1 file changed, 90 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
> index 7d355aa73ea2..ee53e663b5bd 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
> @@ -1079,6 +1079,96 @@ dphy0: phy@30110000 {
> status = "disabled";
> };
>
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [PATCH v2] arm64: dts: ti: k3-am62-main: Add PRUSS-M node
2025-04-30 14:43 [PATCH v2] arm64: dts: ti: k3-am62-main: Add PRUSS-M node Judith Mendez
2025-04-30 16:32 ` Hari Nagalla
@ 2025-05-02 12:24 ` Nishanth Menon
2025-05-02 21:08 ` Judith Mendez
2025-05-05 4:00 ` Beleswar Prasad Padhi
` (2 subsequent siblings)
4 siblings, 1 reply; 7+ messages in thread
From: Nishanth Menon @ 2025-05-02 12:24 UTC (permalink / raw)
To: Judith Mendez
Cc: Vignesh Raghavendra, Tero Kristo, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, linux-arm-kernel, devicetree,
linux-kernel, Hari Nagalla, Beleswar Padhi
On 09:43-20250430, Judith Mendez wrote:
> From: Kishon Vijay Abraham I <kishon@ti.com>
>
> Add the DT node for the PRUSS-M processor subsystem that is present
> on the K3 AM62x SoCs. The K3 AM62x family of SoC has one PRUSS-M
> instance and it has two Programmable Real-Time Units (PRU0 and PRU1).
>
> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
> [ Judith: Fix pruss_iclk id for pruss_coreclk_mux ]
> Signed-off-by: Judith Mendez <jm@ti.com>
> ---
> Changelog:
> - drop internal tags
> - rebase against ti-k3-dts-next
> - fix header
>
> Link to v1:
> https://lore.kernel.org/linux-devicetree/20250108222048.818835-1-jm@ti.com/
> ---
> arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 90 ++++++++++++++++++++++++
> 1 file changed, 90 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
> index 7d355aa73ea2..ee53e663b5bd 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
> @@ -1079,6 +1079,96 @@ dphy0: phy@30110000 {
> status = "disabled";
> };
>
> + pruss: pruss@30040000 {
> + compatible = "ti,am625-pruss";
> + reg = <0x00 0x30040000 0x00 0x80000>;
> + power-domains = <&k3_pds 81 TI_SCI_PD_EXCLUSIVE>;
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges = <0x0 0x00 0x30040000 0x80000>;
Should this not be default disabled? pruss needs pinmux to operate
correctly, right?
> +
> + pruss_mem: memories@0 {
> + reg = <0x0 0x2000>,
> + <0x2000 0x2000>,
> + <0x10000 0x10000>;
> + reg-names = "dram0", "dram1", "shrdram2";
> + };
> +
> + pruss_cfg: cfg@26000 {
> + compatible = "ti,pruss-cfg", "syscon";
> + reg = <0x26000 0x200>;
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges = <0x0 0x26000 0x2000>;
> +
> + clocks {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + pruss_coreclk_mux: coreclk-mux@3c {
> + reg = <0x3c>;
> + #clock-cells = <0>;
> + clocks = <&k3_clks 81 0>, /* pruss_core_clk */
> + <&k3_clks 81 14>; /* pruss_iclk */
> + assigned-clocks = <&pruss_coreclk_mux>;
> + assigned-clock-parents = <&k3_clks 81 14>;
> + };
> +
> + pruss_iepclk_mux: iepclk-mux@30 {
> + reg = <0x30>;
> + #clock-cells = <0>;
> + clocks = <&k3_clks 81 3>, /* pruss_iep_clk */
> + <&pruss_coreclk_mux>; /* pruss_coreclk_mux */
> + assigned-clocks = <&pruss_iepclk_mux>;
> + assigned-clock-parents = <&pruss_coreclk_mux>;
> + };
> + };
> + };
> +
> + pruss_intc: interrupt-controller@20000 {
> + compatible = "ti,pruss-intc";
> + reg = <0x20000 0x2000>;
> + interrupt-controller;
> + #interrupt-cells = <3>;
> + interrupts = <GIC_SPI 88 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 89 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 90 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 91 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 92 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 93 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 94 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 95 IRQ_TYPE_LEVEL_HIGH>;
> + interrupt-names = "host_intr0", "host_intr1",
> + "host_intr2", "host_intr3",
> + "host_intr4", "host_intr5",
> + "host_intr6", "host_intr7";
> + };
> +
> + pru0: pru@34000 {
> + compatible = "ti,am625-pru";
> + reg = <0x34000 0x3000>,
> + <0x22000 0x100>,
> + <0x22400 0x100>;
> + reg-names = "iram", "control", "debug";
> + firmware-name = "am62x-pru0-fw";
> + interrupt-parent = <&pruss_intc>;
> + interrupts = <16 2 2>;
> + interrupt-names = "vring";
> + };
> +
> + pru1: pru@38000 {
> + compatible = "ti,am625-pru";
> + reg = <0x38000 0x3000>,
> + <0x24000 0x100>,
> + <0x24400 0x100>;
> + reg-names = "iram", "control", "debug";
> + firmware-name = "am62x-pru1-fw";
> + interrupt-parent = <&pruss_intc>;
> + interrupts = <18 3 3>;
> + interrupt-names = "vring";
> + };
> + };
> +
> gpmc0: memory-controller@3b000000 {
> compatible = "ti,am64-gpmc";
> power-domains = <&k3_pds 80 TI_SCI_PD_EXCLUSIVE>;
> --
> 2.49.0
>
>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [PATCH v2] arm64: dts: ti: k3-am62-main: Add PRUSS-M node
2025-05-02 12:24 ` Nishanth Menon
@ 2025-05-02 21:08 ` Judith Mendez
0 siblings, 0 replies; 7+ messages in thread
From: Judith Mendez @ 2025-05-02 21:08 UTC (permalink / raw)
To: Nishanth Menon
Cc: Vignesh Raghavendra, Tero Kristo, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, linux-arm-kernel, devicetree,
linux-kernel, Hari Nagalla, Beleswar Padhi
Hi Nishanth,
On 5/2/25 7:24 AM, Nishanth Menon wrote:
> On 09:43-20250430, Judith Mendez wrote:
>> From: Kishon Vijay Abraham I <kishon@ti.com>
>>
>> Add the DT node for the PRUSS-M processor subsystem that is present
>> on the K3 AM62x SoCs. The K3 AM62x family of SoC has one PRUSS-M
>> instance and it has two Programmable Real-Time Units (PRU0 and PRU1).
>>
>> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
>> [ Judith: Fix pruss_iclk id for pruss_coreclk_mux ]
>> Signed-off-by: Judith Mendez <jm@ti.com>
>> ---
>> Changelog:
>> - drop internal tags
>> - rebase against ti-k3-dts-next
>> - fix header
>>
>> Link to v1:
>> https://lore.kernel.org/linux-devicetree/20250108222048.818835-1-jm@ti.com/
>> ---
>> arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 90 ++++++++++++++++++++++++
>> 1 file changed, 90 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
>> index 7d355aa73ea2..ee53e663b5bd 100644
>> --- a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
>> +++ b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
>> @@ -1079,6 +1079,96 @@ dphy0: phy@30110000 {
>> status = "disabled";
>> };
>>
>> + pruss: pruss@30040000 {
>> + compatible = "ti,am625-pruss";
>> + reg = <0x00 0x30040000 0x00 0x80000>;
>> + power-domains = <&k3_pds 81 TI_SCI_PD_EXCLUSIVE>;
>> + #address-cells = <1>;
>> + #size-cells = <1>;
>> + ranges = <0x0 0x00 0x30040000 0x80000>;
>
> Should this not be default disabled? pruss needs pinmux to operate
> correctly, right?
No, PRU node does not need pinmux to work properly. ATM we are using
RPMSG echo test as the default experience and this does not require
any pinmux configuration since signals are internal to the SoC. Now
it is possible for an application to use a PRU GPO for ex and then they
would require pinmux but it is application specific.
~ Judith
>
>> +
>> + pruss_mem: memories@0 {
>> + reg = <0x0 0x2000>,
>> + <0x2000 0x2000>,
>> + <0x10000 0x10000>;
>> + reg-names = "dram0", "dram1", "shrdram2";
>> + };
>> +
>> + pruss_cfg: cfg@26000 {
>> + compatible = "ti,pruss-cfg", "syscon";
>> + reg = <0x26000 0x200>;
>> + #address-cells = <1>;
>> + #size-cells = <1>;
>> + ranges = <0x0 0x26000 0x2000>;
>> +
>> + clocks {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + pruss_coreclk_mux: coreclk-mux@3c {
>> + reg = <0x3c>;
>> + #clock-cells = <0>;
>> + clocks = <&k3_clks 81 0>, /* pruss_core_clk */
>> + <&k3_clks 81 14>; /* pruss_iclk */
>> + assigned-clocks = <&pruss_coreclk_mux>;
>> + assigned-clock-parents = <&k3_clks 81 14>;
>> + };
>> +
>> + pruss_iepclk_mux: iepclk-mux@30 {
>> + reg = <0x30>;
>> + #clock-cells = <0>;
>> + clocks = <&k3_clks 81 3>, /* pruss_iep_clk */
>> + <&pruss_coreclk_mux>; /* pruss_coreclk_mux */
>> + assigned-clocks = <&pruss_iepclk_mux>;
>> + assigned-clock-parents = <&pruss_coreclk_mux>;
>> + };
>> + };
>> + };
>> +
>> + pruss_intc: interrupt-controller@20000 {
>> + compatible = "ti,pruss-intc";
>> + reg = <0x20000 0x2000>;
>> + interrupt-controller;
>> + #interrupt-cells = <3>;
>> + interrupts = <GIC_SPI 88 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 89 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 90 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 91 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 92 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 93 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 94 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 95 IRQ_TYPE_LEVEL_HIGH>;
>> + interrupt-names = "host_intr0", "host_intr1",
>> + "host_intr2", "host_intr3",
>> + "host_intr4", "host_intr5",
>> + "host_intr6", "host_intr7";
>> + };
>> +
>> + pru0: pru@34000 {
>> + compatible = "ti,am625-pru";
>> + reg = <0x34000 0x3000>,
>> + <0x22000 0x100>,
>> + <0x22400 0x100>;
>> + reg-names = "iram", "control", "debug";
>> + firmware-name = "am62x-pru0-fw";
>> + interrupt-parent = <&pruss_intc>;
>> + interrupts = <16 2 2>;
>> + interrupt-names = "vring";
>> + };
>> +
>> + pru1: pru@38000 {
>> + compatible = "ti,am625-pru";
>> + reg = <0x38000 0x3000>,
>> + <0x24000 0x100>,
>> + <0x24400 0x100>;
>> + reg-names = "iram", "control", "debug";
>> + firmware-name = "am62x-pru1-fw";
>> + interrupt-parent = <&pruss_intc>;
>> + interrupts = <18 3 3>;
>> + interrupt-names = "vring";
>> + };
>> + };
>> +
>> gpmc0: memory-controller@3b000000 {
>> compatible = "ti,am64-gpmc";
>> power-domains = <&k3_pds 80 TI_SCI_PD_EXCLUSIVE>;
>> --
>> 2.49.0
>>
>>
>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH v2] arm64: dts: ti: k3-am62-main: Add PRUSS-M node
2025-04-30 14:43 [PATCH v2] arm64: dts: ti: k3-am62-main: Add PRUSS-M node Judith Mendez
2025-04-30 16:32 ` Hari Nagalla
2025-05-02 12:24 ` Nishanth Menon
@ 2025-05-05 4:00 ` Beleswar Prasad Padhi
2025-05-05 7:49 ` Daniel Schultz
2025-05-06 13:10 ` Nishanth Menon
4 siblings, 0 replies; 7+ messages in thread
From: Beleswar Prasad Padhi @ 2025-05-05 4:00 UTC (permalink / raw)
To: Judith Mendez, Nishanth Menon, Vignesh Raghavendra
Cc: Tero Kristo, Rob Herring, Krzysztof Kozlowski, Conor Dooley,
linux-arm-kernel, devicetree, linux-kernel, Hari Nagalla
Hi Judith,
On 4/30/2025 8:13 PM, Judith Mendez wrote:
> From: Kishon Vijay Abraham I <kishon@ti.com>
>
> Add the DT node for the PRUSS-M processor subsystem that is present
> on the K3 AM62x SoCs. The K3 AM62x family of SoC has one PRUSS-M
> instance and it has two Programmable Real-Time Units (PRU0 and PRU1).
>
> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
> [ Judith: Fix pruss_iclk id for pruss_coreclk_mux ]
> Signed-off-by: Judith Mendez <jm@ti.com>
> ---
> Changelog:
> - drop internal tags
> - rebase against ti-k3-dts-next
> - fix header
Reviewed-by: Beleswar Padhi <b-padhi@ti.com>
Thanks,
Beleswar
>
> Link to v1:
> https://lore.kernel.org/linux-devicetree/20250108222048.818835-1-jm@ti.com/
> ---
> arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 90 ++++++++++++++++++++++++
> 1 file changed, 90 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
> index 7d355aa73ea2..ee53e663b5bd 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
> @@ -1079,6 +1079,96 @@ dphy0: phy@30110000 {
> status = "disabled";
> };
>
> + pruss: pruss@30040000 {
> + compatible = "ti,am625-pruss";
> + reg = <0x00 0x30040000 0x00 0x80000>;
> + power-domains = <&k3_pds 81 TI_SCI_PD_EXCLUSIVE>;
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges = <0x0 0x00 0x30040000 0x80000>;
> +
> + pruss_mem: memories@0 {
> + reg = <0x0 0x2000>,
> + <0x2000 0x2000>,
> + <0x10000 0x10000>;
> + reg-names = "dram0", "dram1", "shrdram2";
> + };
> +
> + pruss_cfg: cfg@26000 {
> + compatible = "ti,pruss-cfg", "syscon";
> + reg = <0x26000 0x200>;
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges = <0x0 0x26000 0x2000>;
> +
> + clocks {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + pruss_coreclk_mux: coreclk-mux@3c {
> + reg = <0x3c>;
> + #clock-cells = <0>;
> + clocks = <&k3_clks 81 0>, /* pruss_core_clk */
> + <&k3_clks 81 14>; /* pruss_iclk */
> + assigned-clocks = <&pruss_coreclk_mux>;
> + assigned-clock-parents = <&k3_clks 81 14>;
> + };
> +
> + pruss_iepclk_mux: iepclk-mux@30 {
> + reg = <0x30>;
> + #clock-cells = <0>;
> + clocks = <&k3_clks 81 3>, /* pruss_iep_clk */
> + <&pruss_coreclk_mux>; /* pruss_coreclk_mux */
> + assigned-clocks = <&pruss_iepclk_mux>;
> + assigned-clock-parents = <&pruss_coreclk_mux>;
> + };
> + };
> + };
> +
> + pruss_intc: interrupt-controller@20000 {
> + compatible = "ti,pruss-intc";
> + reg = <0x20000 0x2000>;
> + interrupt-controller;
> + #interrupt-cells = <3>;
> + interrupts = <GIC_SPI 88 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 89 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 90 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 91 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 92 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 93 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 94 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 95 IRQ_TYPE_LEVEL_HIGH>;
> + interrupt-names = "host_intr0", "host_intr1",
> + "host_intr2", "host_intr3",
> + "host_intr4", "host_intr5",
> + "host_intr6", "host_intr7";
> + };
> +
> + pru0: pru@34000 {
> + compatible = "ti,am625-pru";
> + reg = <0x34000 0x3000>,
> + <0x22000 0x100>,
> + <0x22400 0x100>;
> + reg-names = "iram", "control", "debug";
> + firmware-name = "am62x-pru0-fw";
> + interrupt-parent = <&pruss_intc>;
> + interrupts = <16 2 2>;
> + interrupt-names = "vring";
> + };
> +
> + pru1: pru@38000 {
> + compatible = "ti,am625-pru";
> + reg = <0x38000 0x3000>,
> + <0x24000 0x100>,
> + <0x24400 0x100>;
> + reg-names = "iram", "control", "debug";
> + firmware-name = "am62x-pru1-fw";
> + interrupt-parent = <&pruss_intc>;
> + interrupts = <18 3 3>;
> + interrupt-names = "vring";
> + };
> + };
> +
> gpmc0: memory-controller@3b000000 {
> compatible = "ti,am64-gpmc";
> power-domains = <&k3_pds 80 TI_SCI_PD_EXCLUSIVE>;
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [PATCH v2] arm64: dts: ti: k3-am62-main: Add PRUSS-M node
2025-04-30 14:43 [PATCH v2] arm64: dts: ti: k3-am62-main: Add PRUSS-M node Judith Mendez
` (2 preceding siblings ...)
2025-05-05 4:00 ` Beleswar Prasad Padhi
@ 2025-05-05 7:49 ` Daniel Schultz
2025-05-06 13:10 ` Nishanth Menon
4 siblings, 0 replies; 7+ messages in thread
From: Daniel Schultz @ 2025-05-05 7:49 UTC (permalink / raw)
To: Judith Mendez, Nishanth Menon, Vignesh Raghavendra
Cc: Tero Kristo, Rob Herring, Krzysztof Kozlowski, Conor Dooley,
linux-arm-kernel, devicetree, linux-kernel, Hari Nagalla,
Beleswar Padhi
On 4/30/25 16:43, Judith Mendez wrote:
> From: Kishon Vijay Abraham I <kishon@ti.com>
>
> Add the DT node for the PRUSS-M processor subsystem that is present
> on the K3 AM62x SoCs. The K3 AM62x family of SoC has one PRUSS-M
> instance and it has two Programmable Real-Time Units (PRU0 and PRU1).
>
> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
> [ Judith: Fix pruss_iclk id for pruss_coreclk_mux ]
> Signed-off-by: Judith Mendez <jm@ti.com>
Tested-by: Daniel Schultz <d.schultz@phytec.de>
> ---
> Changelog:
> - drop internal tags
> - rebase against ti-k3-dts-next
> - fix header
>
> Link to v1:
> https://lore.kernel.org/linux-devicetree/20250108222048.818835-1-jm@ti.com/
> ---
> arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 90 ++++++++++++++++++++++++
> 1 file changed, 90 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
> index 7d355aa73ea2..ee53e663b5bd 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
> @@ -1079,6 +1079,96 @@ dphy0: phy@30110000 {
> status = "disabled";
> };
>
> + pruss: pruss@30040000 {
> + compatible = "ti,am625-pruss";
> + reg = <0x00 0x30040000 0x00 0x80000>;
> + power-domains = <&k3_pds 81 TI_SCI_PD_EXCLUSIVE>;
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges = <0x0 0x00 0x30040000 0x80000>;
> +
> + pruss_mem: memories@0 {
> + reg = <0x0 0x2000>,
> + <0x2000 0x2000>,
> + <0x10000 0x10000>;
> + reg-names = "dram0", "dram1", "shrdram2";
> + };
> +
> + pruss_cfg: cfg@26000 {
> + compatible = "ti,pruss-cfg", "syscon";
> + reg = <0x26000 0x200>;
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges = <0x0 0x26000 0x2000>;
> +
> + clocks {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + pruss_coreclk_mux: coreclk-mux@3c {
> + reg = <0x3c>;
> + #clock-cells = <0>;
> + clocks = <&k3_clks 81 0>, /* pruss_core_clk */
> + <&k3_clks 81 14>; /* pruss_iclk */
> + assigned-clocks = <&pruss_coreclk_mux>;
> + assigned-clock-parents = <&k3_clks 81 14>;
> + };
> +
> + pruss_iepclk_mux: iepclk-mux@30 {
> + reg = <0x30>;
> + #clock-cells = <0>;
> + clocks = <&k3_clks 81 3>, /* pruss_iep_clk */
> + <&pruss_coreclk_mux>; /* pruss_coreclk_mux */
> + assigned-clocks = <&pruss_iepclk_mux>;
> + assigned-clock-parents = <&pruss_coreclk_mux>;
> + };
> + };
> + };
> +
> + pruss_intc: interrupt-controller@20000 {
> + compatible = "ti,pruss-intc";
> + reg = <0x20000 0x2000>;
> + interrupt-controller;
> + #interrupt-cells = <3>;
> + interrupts = <GIC_SPI 88 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 89 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 90 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 91 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 92 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 93 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 94 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 95 IRQ_TYPE_LEVEL_HIGH>;
> + interrupt-names = "host_intr0", "host_intr1",
> + "host_intr2", "host_intr3",
> + "host_intr4", "host_intr5",
> + "host_intr6", "host_intr7";
> + };
> +
> + pru0: pru@34000 {
> + compatible = "ti,am625-pru";
> + reg = <0x34000 0x3000>,
> + <0x22000 0x100>,
> + <0x22400 0x100>;
> + reg-names = "iram", "control", "debug";
> + firmware-name = "am62x-pru0-fw";
> + interrupt-parent = <&pruss_intc>;
> + interrupts = <16 2 2>;
> + interrupt-names = "vring";
> + };
> +
> + pru1: pru@38000 {
> + compatible = "ti,am625-pru";
> + reg = <0x38000 0x3000>,
> + <0x24000 0x100>,
> + <0x24400 0x100>;
> + reg-names = "iram", "control", "debug";
> + firmware-name = "am62x-pru1-fw";
> + interrupt-parent = <&pruss_intc>;
> + interrupts = <18 3 3>;
> + interrupt-names = "vring";
> + };
> + };
> +
> gpmc0: memory-controller@3b000000 {
> compatible = "ti,am64-gpmc";
> power-domains = <&k3_pds 80 TI_SCI_PD_EXCLUSIVE>;
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [PATCH v2] arm64: dts: ti: k3-am62-main: Add PRUSS-M node
2025-04-30 14:43 [PATCH v2] arm64: dts: ti: k3-am62-main: Add PRUSS-M node Judith Mendez
` (3 preceding siblings ...)
2025-05-05 7:49 ` Daniel Schultz
@ 2025-05-06 13:10 ` Nishanth Menon
4 siblings, 0 replies; 7+ messages in thread
From: Nishanth Menon @ 2025-05-06 13:10 UTC (permalink / raw)
To: Vignesh Raghavendra, Judith Mendez
Cc: Nishanth Menon, Tero Kristo, Rob Herring, Krzysztof Kozlowski,
Conor Dooley, linux-arm-kernel, devicetree, linux-kernel,
Hari Nagalla, Beleswar Padhi
Hi Judith Mendez,
On Wed, 30 Apr 2025 09:43:43 -0500, Judith Mendez wrote:
> Add the DT node for the PRUSS-M processor subsystem that is present
> on the K3 AM62x SoCs. The K3 AM62x family of SoC has one PRUSS-M
> instance and it has two Programmable Real-Time Units (PRU0 and PRU1).
>
>
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/1] arm64: dts: ti: k3-am62-main: Add PRUSS-M node
commit: 3df22a8622fafa1c5a0dba93c207f66f48366858
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
^ permalink raw reply [flat|nested] 7+ messages in thread