From: sashiko-bot@kernel.org
To: "Iker Pedrosa" <ikerpedrosam@gmail.com>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH RFC 1/2] riscv: dts: spacemit: k1: add PowerVR GPU device node
Date: Thu, 15 Oct 2026 19:06:31 +0000 [thread overview]
Message-ID: <sashiko-outbox-173346@kernel.org> (raw)
In-Reply-To: <20261015-orangepi-gpu-v1-1-03566a615660@gmail.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] dts: build failure due to missing k1-power.h dt-binding header
- [Low] dts: undocumented compatible strings for spacemit k1-gpu
--
commit 8e44783c41b2ae5db8c6c7e6e7e39b06ba8d49af
Author: Iker Pedrosa <ikerpedrosam@gmail.com>
riscv: dts: spacemit: k1: add PowerVR GPU device node
Add device tree node for the Imagination Technologies PowerVR Rogue GPU
(BVNC 36.29.52.182 / BXE-2-32) found in the Spacemit K1 SoC.
> diff --git a/arch/riscv/boot/dts/spacemit/k1.dtsi b/arch/riscv/boot/dts/spacemit/k1.dtsi
> index 3fabfd34114b2..82cade2f76fe4 100644
> --- a/arch/riscv/boot/dts/spacemit/k1.dtsi
> +++ b/arch/riscv/boot/dts/spacemit/k1.dtsi
> @@ -5,6 +5,7 @@
>
> #include <dt-bindings/clock/spacemit,k1-syscon.h>
> #include <dt-bindings/phy/phy.h>
> +#include <dt-bindings/power/spacemit,k1-power.h>
[Severity: Low]
Does this header exist in the tree? It doesn't appear to be added in this
patch or in the tree yet, which causes a fatal preprocessor error and
compilation failure.
[ ... ]
> @@ -1119,6 +1120,17 @@ multimedia-bus {
> #size-cells = <2>;
> dma-ranges = <0x0 0x00000000 0x0 0x00000000 0x0 0x80000000>,
> <0x0 0x80000000 0x1 0x00000000 0x3 0x80000000>;
> +
> + gpu: gpu@cac00000 {
> + compatible = "spacemit,k1-gpu", "img,img-bxe-2-32", "img,img-rogue";
[Severity: Low]
Are these compatible strings documented in a DT binding schema?
"spacemit,k1-gpu" and "img,img-bxe-2-32" appear to be undocumented, which will
cause dt_binding_check to fail. Omitting them from the schema also means
their constraints (like required clocks or power domains) won't be properly
validated.
> + reg = <0x0 0xcac00000 0x0 0x80000>;
> + interrupts = <75>;
> + clocks = <&syscon_apmu CLK_GPU>;
> + clock-names = "core";
> + resets = <&syscon_apmu RESET_GPU>;
> + power-domains = <&syscon_apmu K1_PMDOMAIN_GPU>;
[Severity: Low]
Is it possible to build this node? This relies on K1_PMDOMAIN_GPU which was
presumably provided by the missing spacemit,k1-power.h header mentioned
above.
> + status = "disabled";
> + };
> };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261015-orangepi-gpu-v1-0-03566a615660@gmail.com?part=1
next prev parent reply other threads:[~2026-10-15 19:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 18:56 [PATCH RFC 0/2] riscv: dts: spacemit: Enable PowerVR GPU on OrangePi RV2 Iker Pedrosa
2026-10-15 18:56 ` [PATCH RFC 1/2] riscv: dts: spacemit: k1: add PowerVR GPU device node Iker Pedrosa
2026-10-15 19:06 ` sashiko-bot [this message]
2026-10-15 18:56 ` [PATCH RFC 2/2] riscv: dts: spacemit: k1-orangepi-rv2: enable GPU Iker Pedrosa
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=sashiko-outbox-173346@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ikerpedrosam@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox