From: Alessio Belle <Alessio.Belle@imgtec.com>
To: "geert+renesas@glider.be" <geert+renesas@glider.be>
Cc: Luigi Santivetti <Luigi.Santivetti@imgtec.com>,
"robh@kernel.org" <robh@kernel.org>,
"tzimmermann@suse.de" <tzimmermann@suse.de>,
"anh.nguyen.pv@renesas.com" <anh.nguyen.pv@renesas.com>,
"imagination@lists.freedesktop.org"
<imagination@lists.freedesktop.org>,
"simona@ffwll.ch" <simona@ffwll.ch>,
"marek.vasut+renesas@mailbox.org"
<marek.vasut+renesas@mailbox.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"mripard@kernel.org" <mripard@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"maarten.lankhorst@linux.intel.com"
<maarten.lankhorst@linux.intel.com>,
"kuninori.morimoto.gx@renesas.com"
<kuninori.morimoto.gx@renesas.com>,
"airlied@gmail.com" <airlied@gmail.com>
Subject: Re: [PATCH/RFC 3/3] arm64: dts: renesas: r8a779h0: Add GPU node
Date: Fri, 11 Sep 2026 10:32:44 +0000 [thread overview]
Message-ID: <01f4558dd80451880a9bb72766fc283ade4e295d.camel@imgtec.com> (raw)
In-Reply-To: <2eb9d054023049e1aa282c141981a39de4d4abe6.1789028076.git.geert+renesas@glider.be>
Hi Geert,
On Thu, 2026-09-10 at 10:19 +0200, Geert Uytterhoeven wrote:
> Add a device node for the Imagination Technologies IMG BXS-4-64 GPU.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> TI K3 J721s2 uses the same GPU, and firmware is available in upstream
> linux-firmware. The firmware is loaded, but fails to boot:
>
> powervr fd000000.gpu: [drm] loaded firmware powervr/rogue_36.53.104.796_v1.fw
> powervr fd000000.gpu: [drm] FW version v1.1 (build 6976702 OS)
> powervr fd000000.gpu: [drm] *ERROR* Firmware failed to boot
This is suspicious because as you said the same GPU/firmware are already used on
at least another platform. We have a V4M so we can try figuring out soon what's
preventing the firmware from booting from the driver/firmware point of view.
In the meantime, could you hold off on merging the updated bindings and DT node
in case they need fixing?
Thanks,
Alessio
> ---
> arch/arm64/boot/dts/renesas/r8a779h0.dtsi | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/renesas/r8a779h0.dtsi b/arch/arm64/boot/dts/renesas/r8a779h0.dtsi
> index 0c9ca0f90badc096..ac6665568bd83a12 100644
> --- a/arch/arm64/boot/dts/renesas/r8a779h0.dtsi
> +++ b/arch/arm64/boot/dts/renesas/r8a779h0.dtsi
> @@ -1873,6 +1873,27 @@ its: msi-controller@40000 {
> };
> };
>
> + gsx: gpu@fd000000 {
> + compatible = "renesas,r8a779h0-gpu",
> + "img,img-bxs-4-64", "img,img-rogue";
> + reg = <0 0xfd000000 0 0x800000>;
> + interrupts = <GIC_SPI 464 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 465 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 466 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 467 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 468 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 469 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 470 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 471 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&cpg CPG_MOD 0>;
> + clock-names = "core";
> + power-domains = <&sysc R8A779H0_PD_A33DGA>,
> + <&sysc R8A779H0_PD_A23DGB>;
> + power-domain-names = "a", "b";
> + resets = <&cpg 0>;
> + status = "disabled";
> + };
> +
> csi40: csi2@fe500000 {
> compatible = "renesas,r8a779h0-csi2";
> reg = <0 0xfe500000 0 0x40000>;
prev parent reply other threads:[~2026-09-11 10:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 8:19 [PATCH/RFC 0/3] power: Add Renesas R-Car V4H and V4M support Geert Uytterhoeven
2026-09-10 8:19 ` [PATCH/RFC 1/3] dt-bindings: gpu: img,powervr-rogue: Document " Geert Uytterhoeven
2026-09-10 8:34 ` sashiko-bot
2026-09-11 10:20 ` [PATCH/RFC 1/3] dt-bindings: gpu: img, powervr-rogue: " Alessio Belle
2026-09-10 8:19 ` [PATCH/RFC 2/3] arm64: dts: renesas: r8a779g0: Add GPU node Geert Uytterhoeven
2026-09-10 14:20 ` Marek Vasut
2026-09-10 8:19 ` [PATCH/RFC 3/3] arm64: dts: renesas: r8a779h0: " Geert Uytterhoeven
2026-09-11 10:32 ` Alessio Belle [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=01f4558dd80451880a9bb72766fc283ade4e295d.camel@imgtec.com \
--to=alessio.belle@imgtec.com \
--cc=Luigi.Santivetti@imgtec.com \
--cc=airlied@gmail.com \
--cc=anh.nguyen.pv@renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert+renesas@glider.be \
--cc=imagination@lists.freedesktop.org \
--cc=krzk+dt@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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