From: sashiko-bot@kernel.org
To: Sterling-Ash <baihui.liang@spacemit.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 1/2] dt-bindings: gpu: img,powervr-rogue: add spacemit,k3-gpu
Date: Mon, 27 Jul 2026 01:28:01 +0000 [thread overview]
Message-ID: <20260727012801.D70091F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260727012231.1025210-2-baihui.liang@spacemit.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Incomplete schema validation: `spacemit,k3-gpu` allows up to 3 clocks instead of restricting it to 1.
--
--- Patch [1]: [PATCH v2 1/2] dt-bindings: gpu: img,powervr-rogue: add spacemit,k3-gpu ---
commit 5e58bdf2ff5533bc6aae23c68852fcbc9caf9570
Author: Sterling-Ash <baihui.liang@spacemit.com>
dt-bindings: gpu: img,powervr-rogue: add spacemit,k3-gpu
This commit adds a compatible string for the IMG BXM-4-64 GPU integrated
into the SpacemiT K3 SoC. It notes that the integration requires a single
core clock and omits power-domains, falling back to general schema
constraints.
> diff --git a/Documentation/devicetree/bindings/gpu/img,powervr-rogue.yaml b/Documentation/devicetree/bindings/gpu/img,powervr-rogue.yaml
> index a1f54dbae3f31..2d58dd4076a87 100644
> --- a/Documentation/devicetree/bindings/gpu/img,powervr-rogue.yaml
> +++ b/Documentation/devicetree/bindings/gpu/img,powervr-rogue.yaml
> @@ -38,6 +38,11 @@ properties:
> - thead,th1520-gpu
> - const: img,img-bxm-4-64
> - const: img,img-rogue
> + - items:
> + - enum:
> + - spacemit,k3-gpu
> + - const: img,img-bxm-4-64
> + - const: img,img-rogue
[Severity: Medium]
Will omitting spacemit,k3-gpu from a conditional block allow invalid
device trees to silently pass schema validation?
The commit message explicitly states that the K3 GPU only needs a single
clock and relies on the general schema constraints. However, the general
schema configuration allows up to 3 clocks:
Documentation/devicetree/bindings/gpu/img,powervr-rogue.yaml:properties.clocks:
clocks:
minItems: 1
maxItems: 3
Because spacemit,k3-gpu does not match any specific allOf.if block
enforcing a maximum of 1 clock, it falls back to this general limit.
Should an if-then conditional block be added to enforce maxItems: 1 for
the clocks property on this platform?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260727012231.1025210-1-baihui.liang@spacemit.com?part=1
next prev parent reply other threads:[~2026-07-27 1:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 1:49 [PATCH] drm/imagination: allow probe when no power-domains are described Sterling-Ash
2026-07-24 14:50 ` Alessio Belle
2026-07-27 1:22 ` [PATCH v2 0/2] drm/imagination: support GPU probe without power-domains Sterling-Ash
2026-07-27 1:22 ` Sterling-Ash
2026-07-27 1:22 ` [PATCH v2 1/2] dt-bindings: gpu: img,powervr-rogue: add spacemit,k3-gpu Sterling-Ash
2026-07-27 1:22 ` Sterling-Ash
2026-07-27 1:28 ` sashiko-bot [this message]
2026-07-27 1:22 ` [PATCH v2 2/2] drm/imagination: allow probe when no power-domains are described Sterling-Ash
2026-07-27 1:22 ` Sterling-Ash
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=20260727012801.D70091F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=baihui.liang@spacemit.com \
--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 \
/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.