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 1/3] dt-bindings: gpu: img, powervr-rogue: Document R-Car V4H and V4M support
Date: Fri, 11 Sep 2026 10:20:47 +0000 [thread overview]
Message-ID: <497bc6a40d67f01decfcc2f52e9b8d57754f21f6.camel@imgtec.com> (raw)
In-Reply-To: <1c2771f8882cde0fde694b9f5aae50c02a2ae4cb.1789028076.git.geert+renesas@glider.be>
Hi Geert,
On Thu, 2026-09-10 at 10:19 +0200, Geert Uytterhoeven wrote:
> The Renesas R-Car V4H SoC integrates an Imagination Technologies IMG
> AXM-8-256 GPU, while R-Car V4M integrates an Imagination Technologies
> IMG BXS-4-64 GPU. Both variants can generate 8 interrupts.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> .../bindings/gpu/img,powervr-rogue.yaml | 22 ++++++++++++++++++-
> 1 file changed, 21 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/gpu/img,powervr-rogue.yaml b/Documentation/devicetree/bindings/gpu/img,powervr-rogue.yaml
> index e9218e0f363d1848..9bea037602c137a7 100644
> --- a/Documentation/devicetree/bindings/gpu/img,powervr-rogue.yaml
> +++ b/Documentation/devicetree/bindings/gpu/img,powervr-rogue.yaml
> @@ -35,6 +35,11 @@ properties:
> # work with newer dts.
> - const: img,img-axe
> - const: img,img-rogue
> + - items:
> + - enum:
> + - renesas,r8a779g0-gpu
> + - const: img,img-axm-8-256
> + - const: img,img-rogue
It was already pointed out in another reply, but AXM is a Volcanic GPU where
Volcanic is the architecture following Rogue.
We will have a separate set of bindings for Volcanic with a few differences
including a new base compatible name. The driver is going to be the same, just
with a whole lot of changes that are still being worked on.
The updates for AXM and V4H from this series will need to wait until at least
the new bindings have been upstreamed.
Thanks,
Alessio
> - items:
> - enum:
> - thead,th1520-gpu
> @@ -44,6 +49,7 @@ properties:
> - enum:
> - ti,am62p-gpu
> - ti,j721s2-gpu
> + - renesas,r8a779h0-gpu
> - const: img,img-bxs-4-64
> - const: img,img-rogue
>
> @@ -70,7 +76,8 @@ properties:
> minItems: 1
>
> interrupts:
> - maxItems: 1
> + minItems: 1
> + maxItems: 8
>
> power-domains:
> minItems: 1
> @@ -173,6 +180,19 @@ allOf:
> required:
> - power-domains
>
> + - if:
> + not:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - renesas,r8a779g0-gpu
> + - renesas,r8a779h0-gpu
> + then:
> + properties:
> + interrupts:
> + maxItems: 1
> +
> examples:
> - |
> #include <dt-bindings/interrupt-controller/irq.h>
next prev parent reply other threads:[~2026-09-11 10:21 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 ` Alessio Belle [this message]
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
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=497bc6a40d67f01decfcc2f52e9b8d57754f21f6.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