From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Anh Nguyen <anh.nguyen.pv@renesas.com>
Cc: "magnus.damm" <magnus.damm@gmail.com>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Duy Dang <duy.dang.yw@renesas.com>,
Duy Nguyen <duy.nguyen.rh@renesas.com>
Subject: Re: [PATCH v1] arm64: dts: renesas: r8a779g0: Add new gsx node for V4H
Date: Mon, 1 Sep 2025 12:24:07 +0200 [thread overview]
Message-ID: <CAMuHMdXDW5=UCVRSq2DBks++YpyoJ9rtsdaKheYLv7foEZmg-A@mail.gmail.com> (raw)
In-Reply-To: <OS7PR01MB1370309A85A300195896C0619A73EA@OS7PR01MB13703.jpnprd01.prod.outlook.com>
Hi Anh,
On Mon, 25 Aug 2025 at 06:37, Anh Nguyen <anh.nguyen.pv@renesas.com> wrote:
> From 8a8391bc4ceaac5248267851b71c9cce6b5c434a Mon Sep 17 00:00:00 2001
> From: Anh Nguyen <anh.nguyen.pv@renesas.com>
> Date: Thu, 21 Aug 2025 10:01:30 +0700
> Subject: [PATCH 2/2] arm64: dts: renesas: r8a779g0: Add new gsx node for V4H SoC
>
> Add new gsx node to enable GPU for V4H SoC
>
> Signed-off-by: Anh Nguyen <anh.nguyen.pv@renesas.com>
> Reviewed-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Thanks for your patch!
> --- a/arch/arm64/boot/dts/renesas/r8a779g0.dtsi
> +++ b/arch/arm64/boot/dts/renesas/r8a779g0.dtsi
> @@ -2121,6 +2121,15 @@ gic: interrupt-controller@f1000000 {
> interrupts = <GIC_PPI 9 IRQ_TYPE_LEVEL_HIGH>;
> };
>
> + gsx: gsx@fd000000 {
> + compatible = "renesas,gsx";
This compatible value is not documented. However, I don't think this
can be used as-is. I think the property should look like:
compatible = "renesas,r8a779g0-gpu", "img,img-axm-8-256".
The first step would be to add it to the DT bindings in
Documentation/devicetree/bindings/gpu/img,powervr-rogue.yaml.
Furthermore, support for this variant should be added to the driver
under drivers/gpu/drm/imagination/.
And where to get the firmware required to operate the GPU?
> + reg = <0 0xfd000000 0 0x800000>;
> + interrupts = <GIC_SPI 464 IRQ_TYPE_LEVEL_HIGH>;
According to the documentation, there are 8 interrupts?
> + clocks = <&cpg CPG_MOD 0>;
> + power-domains = <&sysc R8A779G0_PD_A23DGB>;
> + resets = <&cpg 0>;
> + };
> +
> csi40: csi2@fe500000 {
> compatible = "renesas,r8a779g0-csi2";
> reg = <0 0xfe500000 0 0x40000>;
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2025-09-01 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OS7PR01MB137037775991BBBDB29E54105A77BA@OS7PR01MB13703.jpnprd01.prod.outlook.com>
[not found] ` <87zfdw2wlt.wl-kuninori.morimoto.gx@renesas.com>
[not found] ` <OS7PR01MB13703B662D2AE6ECB77F59584A77BA@OS7PR01MB13703.jpnprd01.prod.outlook.com>
[not found] ` <877c0z2vz3.wl-kuninori.morimoto.gx@renesas.com>
[not found] ` <OS7PR01MB13703654640293E4F1F95B694A730A@OS7PR01MB13703.jpnprd01.prod.outlook.com>
[not found] ` <877byyzjcm.wl-kuninori.morimoto.gx@renesas.com>
[not found] ` <OS7PR01MB137031EFD84919AA36666E1FAA732A@OS7PR01MB13703.jpnprd01.prod.outlook.com>
[not found] ` <87bjo971ns.wl-kuninori.morimoto.gx@renesas.com>
[not found] ` <OS7PR01MB13703647C4AABD03C6345F221A732A@OS7PR01MB13703.jpnprd01.prod.outlook.com>
[not found] ` <87cy8k2uf1.wl-kuninori.morimoto.gx@renesas.com>
2025-08-25 4:33 ` [PATCH v1] clk: renesas: r8a779g0: Add ZG clocks Anh Nguyen
2025-09-01 10:09 ` Geert Uytterhoeven
2025-08-25 4:37 ` [PATCH v1] arm64: dts: renesas: r8a779g0: Add new gsx node for V4H Anh Nguyen
2025-09-01 10:24 ` Geert Uytterhoeven [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='CAMuHMdXDW5=UCVRSq2DBks++YpyoJ9rtsdaKheYLv7foEZmg-A@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=anh.nguyen.pv@renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=duy.dang.yw@renesas.com \
--cc=duy.nguyen.rh@renesas.com \
--cc=krzk+dt@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).