Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Thomas Turner" <tturner@lineageos.org>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: exynos850: Add GPU/Mali Bifrost node
Date: Thu, 20 Aug 2026 13:43:05 +0000	[thread overview]
Message-ID: <20260820134305.C15641F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260820133556.76300-1-tturner@lineageos.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The newly introduced compatible string 'samsung,exynos850-mali' is not documented in the device tree bindings schema.
--

--- Patch [1]: [PATCH] arm64: dts: exynos850: Add GPU/Mali Bifrost node ---
commit 358cd68635088d124d51d9f2284625ff11e03e28
Author: Thomas Turner <tturner@lineageos.org>

arm64: dts: exynos850: Add GPU/Mali Bifrost node

This commit adds a GPU node for the Exynos850 platform to provide basic GPU
functionality. The panfrost driver can probe the Mali-G52 GPU with core
clocks set up, though advanced power management features are not yet
supported.

> diff --git a/arch/arm64/boot/dts/exynos/exynos850.dtsi b/arch/arm64/boot/dts/exynos/exynos850.dtsi
> index 3881f573ec08d..8ed85c125030a 100644
> --- a/arch/arm64/boot/dts/exynos/exynos850.dtsi
> +++ b/arch/arm64/boot/dts/exynos/exynos850.dtsi
> @@ -296,6 +296,18 @@ cmu_g3d: clock-controller@11400000 {
>  			clock-names = "oscclk", "dout_g3d_switch";
>  		};
>  
> +		gpu: gpu@11500000 {
> +			compatible = "samsung,exynos850-mali", "arm,mali-bifrost";

[Severity: Low]
Is the new compatible string samsung,exynos850-mali documented in the
device tree bindings schema?

It appears this SoC-specific compatible string lacks a corresponding entry in
the dt-bindings documentation (e.g.
Documentation/devicetree/bindings/gpu/arm,mali-bifrost.yaml). This will
likely cause make dtbs_check to emit warnings or fail validation for this
device tree file.

> +			reg = <0x11500000 0x5000>;
[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260820133556.76300-1-tturner@lineageos.org?part=1

  reply	other threads:[~2026-08-20 13:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <GVYP280MB12139AB976CA7ACF49FEB768A1A52@GVYP280MB1213.SWEP280.PROD.OUTLOOK.COM>
2026-08-20 13:35 ` [PATCH] arm64: dts: exynos850: Add GPU/Mali Bifrost node Thomas Turner
2026-08-20 13:43   ` sashiko-bot [this message]
2026-08-20 14:13   ` Krzysztof Kozlowski
2026-08-20 14:23 ` [PATCH v2 0/2] Exynos850 GPU support Thomas Turner
2026-08-20 14:23   ` [PATCH v2 1/2] dt-bindings: gpu: arm,mali-bifrost: add exynos850-mali compatible Thomas Turner
2026-08-20 14:23   ` [PATCH v2 2/2] arm64: dts: exynos850: Add GPU/Mali Bifrost node Thomas Turner
2026-08-20 14:28   ` [PATCH v2 0/2] Exynos850 GPU support Krzysztof Kozlowski
     [not found]     ` <GVYP280MB1213F9511E062056470AE74AA1A42@GVYP280MB1213.SWEP280.PROD.OUTLOOK.COM>
2026-08-20 16:22       ` thomas_turner@talktalk.net
2026-08-20 18:15         ` Krzysztof Kozlowski

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=20260820134305.C15641F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=tturner@lineageos.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox