Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Geert Uytterhoeven" <geert+renesas@glider.be>
Cc: robh@kernel.org, dri-devel@lists.freedesktop.org,
	conor+dt@kernel.org, wsa+renesas@sang-engineering.com,
	devicetree@vger.kernel.org
Subject: Re: [PATCH/RFC 1/3] dt-bindings: gpu: img,powervr-rogue: Document R-Car V4H and V4M support
Date: Thu, 10 Sep 2026 08:34:04 +0000	[thread overview]
Message-ID: <20260910083404.796031F000FF@smtp.kernel.org> (raw)
In-Reply-To: <1c2771f8882cde0fde694b9f5aae50c02a2ae4cb.1789028076.git.geert+renesas@glider.be>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The newly added compatible string `img,img-axm-8-256` is omitted from the `power-domains` conditional block, allowing incomplete device tree nodes to silently pass validation.
--

commit 2124d2433f8e144a72392a5dd4a2382c06e9682a
Author: Geert Uytterhoeven <geert+renesas@glider.be>

dt-bindings: gpu: img,powervr-rogue: Document R-Car V4H and V4M support
    
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.

> diff --git a/Documentation/devicetree/bindings/gpu/img,powervr-rogue.yaml b/Documentation/devicetree/bindings/gpu/img,powervr-rogue.yaml
> index e9218e0f363d1..9bea037602c13 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

[Severity: Medium]
Does the newly added img,img-axm-8-256 compatible string need to be included
in the power-domains conditional block?

Looking at the allOf/power-domains constraints further down in
Documentation/devicetree/bindings/gpu/img,powervr-rogue.yaml, the existing
block requires two power domains for similar hardware:

  - if:
      properties:
        compatible:
          contains:
            enum:
              - img,img-bxs-4-64
              - img,img-ge7800
              - img,img-gx6250
    then:
      properties:
        power-domains:
          minItems: 2
        power-domain-names:
          minItems: 2
      required:
        - power-domains
        - power-domain-names

If a developer compiles a device tree using renesas,r8a779g0-gpu without
providing the required two power domains, will the dtbs_check tool process
the device tree without flagging the omission?

Should this enum list be updated to include img,img-axm-8-256 to correctly
enforce the two power domains requirement for the R-Car V4H hardware?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1789028076.git.geert+renesas@glider.be?part=1

  reply	other threads:[~2026-09-10  8:34 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 [this message]
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

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=20260910083404.796031F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geert+renesas@glider.be \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=wsa+renesas@sang-engineering.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