From: Beleswar Prasad Padhi <b-padhi@ti.com>
To: Judith Mendez <jm@ti.com>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>
Cc: Tero Kristo <kristo@kernel.org>, 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>,
Hari Nagalla <hnagalla@ti.com>
Subject: Re: [PATCH v2] arm64: dts: ti: k3-am62-main: Add PRUSS-M node
Date: Mon, 5 May 2025 09:30:59 +0530 [thread overview]
Message-ID: <4bddfa36-7cdb-4e74-b356-8ec4d7fb55aa@ti.com> (raw)
In-Reply-To: <20250430144343.972234-1-jm@ti.com>
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>;
next prev parent reply other threads:[~2025-05-05 4:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2025-05-05 7:49 ` Daniel Schultz
2025-05-06 13:10 ` Nishanth Menon
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=4bddfa36-7cdb-4e74-b356-8ec4d7fb55aa@ti.com \
--to=b-padhi@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hnagalla@ti.com \
--cc=jm@ti.com \
--cc=kristo@kernel.org \
--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