Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bryan Brattlof <bb@ti.com>
To: <a-christidis@ti.com>
Cc: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
	"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>,
	Michael Walle <mwalle@kernel.org>
Subject: Re: [PATCH v2] arm64: dts: ti: add am62p/j722s GPU node
Date: Thu, 3 Sep 2026 08:06:10 -0500	[thread overview]
Message-ID: <20260903130610.pasaudigf4vrr6nv@bryanbrattlof.com> (raw)
In-Reply-To: <20260831-am62p-gpu-node-v2-1-69945a2db2af@ti.com>

On August 31, 2026 thus sayeth a-christidis@ti.com:
> From: Michael Walle <mwalle@kernel.org>
> 
> Add BXS-4 GPU node for J722s/AM62P.
> 
> Signed-off-by: Michael Walle <mwalle@kernel.org>
> Signed-off-by: Antonios Christidis <a-christidis@ti.com>
> ---
> v2:
>   - Reword commit message and title for clarity
>   - Resend patch, missed merge window previously
> ---
>  arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi | 11 +++++++++++
>  1 file changed, 11 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi
> index f130c7cb998d..e36205eccfc9 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi
> @@ -1111,6 +1111,17 @@ dphy0: phy@30110000 {
>  		status = "disabled";
>  	};
>  
> +	gpu: gpu@fd80000 {
> +		compatible = "ti,am62p-gpu", "img,img-bxs-4-64", "img,img-rogue";
> +		reg = <0x00 0x0fd80000 0x00 0x80000>;
> +		clocks = <&k3_clks 237 3>;
> +		clock-names = "core";
> +		interrupts = <GIC_SPI 241 IRQ_TYPE_LEVEL_HIGH>;
> +		power-domains = <&k3_pds 237 TI_SCI_PD_EXCLUSIVE>,
> +				<&k3_pds 242 TI_SCI_PD_EXCLUSIVE>;
> +		power-domain-names = "a", "b";
> +	};
> +

What an exciting thing to see! Way to go Antonios! Without talking to 
you guys I would have never known how much work went into this node.

Reviewed-by: Bryan Brattlof <bb@ti.com>

~Bryan


      reply	other threads:[~2026-09-03 13:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31 18:09 [PATCH v2] arm64: dts: ti: add am62p/j722s GPU node a-christidis
2026-09-03 13:06 ` Bryan Brattlof [this message]

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=20260903130610.pasaudigf4vrr6nv@bryanbrattlof.com \
    --to=bb@ti.com \
    --cc=a-christidis@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mwalle@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