From: sashiko-bot@kernel.org
To: "Chen-Yu Tsai" <wenst@chromium.org>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 3/5] dt-bindings: gpu: powervr-rogue: Add MediaTek MT8173 GPU
Date: Mon, 27 Jul 2026 09:26:43 +0000 [thread overview]
Message-ID: <20260727092643.DC90B1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260727091555.1023910-4-wenst@chromium.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Schema validation failure for MT8173 GPU due to inherited power-domain constraints
--
--- Patch [3]: [PATCH v3 3/5] dt-bindings: gpu: powervr-rogue: Add MediaTek MT8173 GPU ---
commit 560e4cee0c5fbc6b0c5d09c24c260e205ca79e47
Author: Chen-Yu Tsai <wenst@chromium.org>
dt-bindings: gpu: powervr-rogue: Add MediaTek MT8173 GPU
The MediaTek MT8173 comes with a PowerVR Rogue GX6250, which is one
of the Series6XT GPUs, another sub-family of the Rogue family.
[1] https://lore.kernel.org/dri-devel/6eeccb26e09aad67fb30ffcd523c793a43c79c2a.camel@imgtec.com/
> diff --git a/Documentation/devicetree/bindings/gpu/img,powervr-rogue.yaml b/Documentation/devicetree/bindings/gpu/img,powervr-rogue.yaml
> index a1f54dbae3f31..53131cd4cc2a3 100644
> --- a/Documentation/devicetree/bindings/gpu/img,powervr-rogue.yaml
> +++ b/Documentation/devicetree/bindings/gpu/img,powervr-rogue.yaml
> @@ -15,6 +15,7 @@ properties:
> oneOf:
> - items:
> - enum:
> + - mediatek,mt8173-gpu
[Severity: Medium]
Will this cause schema validation failures for the MT8173 GPU node?
By using img,img-gx6250 as the fallback compatible string here, it seems this
will trigger the allOf conditional block lower in the file:
- 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
Since mediatek,mt8173-mfgtop only provides a single power domain, wouldn't
forcing minItems: 2 cause valid device trees to fail dt_binding_check? Should
the conditional block be updated to exclude mediatek,mt8173-gpu?
> - renesas,r8a7796-gpu
> - renesas,r8a77961-gpu
> - const: img,img-gx6250
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260727091555.1023910-1-wenst@chromium.org?part=3
next prev parent reply other threads:[~2026-07-27 9:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 9:15 [PATCH v3 0/5] powervr: MT8173 GPU support Chen-Yu Tsai
2026-07-27 9:15 ` [PATCH v3 1/5] dt-bindings: clock: mediatek: Add mt8173 mfgtop Chen-Yu Tsai
2026-07-27 11:26 ` AngeloGioacchino Del Regno
2026-07-27 9:15 ` [PATCH v3 2/5] clk: mediatek: Add mt8173-mfgtop driver Chen-Yu Tsai
2026-07-27 9:29 ` sashiko-bot
2026-07-27 11:26 ` AngeloGioacchino Del Regno
2026-07-27 16:16 ` Brian Masney
2026-07-27 9:15 ` [PATCH v3 3/5] dt-bindings: gpu: powervr-rogue: Add MediaTek MT8173 GPU Chen-Yu Tsai
2026-07-27 9:26 ` sashiko-bot [this message]
2026-07-27 9:46 ` Chen-Yu Tsai
2026-07-27 9:15 ` [PATCH v3 4/5] arm64: dts: mediatek: mt8173: Fix MFG_ASYNC power domain clock Chen-Yu Tsai
2026-07-27 9:15 ` [PATCH v3 5/5] arm64: dts: mediatek: mt8173: Add GPU device nodes Chen-Yu Tsai
2026-07-27 15:48 ` [PATCH v3 0/5] powervr: MT8173 GPU support YoungJoon Lee
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=20260727092643.DC90B1F000E9@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=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wenst@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.