Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Dawid Wróbel" <me@dawidwrobel.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org,
	dri-devel@lists.freedesktop.org, robh@kernel.org
Subject: Re: [PATCH 4/4] arm64: dts: qcom: sm8250: add device tree for the Xiaomi Mi Pad 5 Pro 5G
Date: Thu, 30 Jul 2026 22:03:06 +0000	[thread overview]
Message-ID: <20260730220307.61C961F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260730-sm8250-xiaomi-enuma-v1-4-ed6d8fb99668@dawidwrobel.com>

Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider:
- [Low] The newly added device tree source `sm8250-xiaomi-enuma.dts` fails to compile because it references an undefined label `&wifi_0`.
- [Low] The root `compatible` string violates the `qcom.yaml` schema expectations and will fail `make dtbs_check`.
- [Low] The display panel `compatible` string violates the `novatek,nt36523.yaml` schema expectations and will fail `make dtbs_check`.
--

--- Patch [4]: [PATCH 4/4] arm64: dts: qcom: sm8250: add device tree for the Xiaomi Mi Pad 5 Pro 5G ---
commit 3ad8e67e479446954f8eea3da616a9b04bf046b8
Author: Dawid Wróbel <me@dawidwrobel.com>

arm64: dts: qcom: sm8250: add device tree for the Xiaomi Mi Pad 5 Pro 5G

This patch adds a new device tree for the Xiaomi Mi Pad 5 Pro 5G (enuma),
which is the modem-equipped variant of the Mi Pad 5 Pro. It describes the
board using the common device tree along with its own board ID, panel
compatible, and WiFi board data variant.

> diff --git a/arch/arm64/boot/dts/qcom/sm8250-xiaomi-enuma.dts b/arch/arm64/boot/dts/qcom/sm8250-xiaomi-enuma.dts
> new file mode 100644
> index 0000000000000..7cc9ed7d12b28
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/sm8250-xiaomi-enuma.dts
> @@ -0,0 +1,26 @@
[ ... ]
> +/ {
> +	model = "Xiaomi Mi Pad 5 Pro 5G";
> +	compatible = "xiaomi,enuma", "xiaomi,elish", "qcom,sm8250";

[Severity: Low]
Does this root compatible string violate the qcom.yaml schema expectations?
It looks like it contains 3 items instead of the strictly expected 2, and
"xiaomi,enuma" is not documented in the schema, which could cause
make dtbs_check to fail.

> +
> +	/* Platform type differs from elish; msm-id is inherited unchanged. */
> +	qcom,board-id = <0x2e 0>;
> +};
> +
> +&display_panel {
> +	compatible = "xiaomi,enuma-csot-nt36523", "xiaomi,elish-csot-nt36523",
> +		     "novatek,nt36523";

[Severity: Low]
Does this display panel compatible string violate the novatek,nt36523.yaml
schema expectations? It appears to contain 3 items instead of 2, and
"xiaomi,enuma-csot-nt36523" is not listed in the schema, which could cause
a make dtbs_check failure.

> +	status = "okay";
> +};
> +
> +&wifi_0 {

[Severity: Low]
Is wifi_0 defined in any of the included files? It looks like this block
references an undefined label &wifi_0, which triggers a fatal dtc compile
error during make dtbs.

> +	qcom,calibration-variant = "Xiaomi_Pad_5Pro_5G";
> +};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260730-sm8250-xiaomi-enuma-v1-0-ed6d8fb99668@dawidwrobel.com?part=4

      reply	other threads:[~2026-07-30 22:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30 21:51 [PATCH 0/4] arm64: dts: qcom: add the Xiaomi Mi Pad 5 Pro 5G Dawid Wróbel via B4 Relay
2026-07-30 21:52 ` [PATCH 1/4] dt-bindings: display: panel: novatek,nt36523: add the Mi Pad 5 Pro 5G panel Dawid Wróbel via B4 Relay
2026-07-30 21:52 ` [PATCH 2/4] dt-bindings: arm: qcom: add the Xiaomi Mi Pad 5 Pro 5G Dawid Wróbel via B4 Relay
2026-07-30 21:52 ` [PATCH 3/4] arm64: dts: qcom: sm8250-xiaomi-elish: label the WiFi node Dawid Wróbel via B4 Relay
2026-07-30 21:52 ` [PATCH 4/4] arm64: dts: qcom: sm8250: add device tree for the Xiaomi Mi Pad 5 Pro 5G Dawid Wróbel via B4 Relay
2026-07-30 22:03   ` sashiko-bot [this message]

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=20260730220307.61C961F000E9@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=me@dawidwrobel.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