Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: vishnu.saini@oss.qualcomm.com
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 1/7] arm64: dts: qcom: shikra-cqm-evk, shikra-cqs-evk: Add HDMI overlay
Date: Wed, 21 Oct 2026 14:37:08 +0000	[thread overview]
Message-ID: <sashiko-outbox-180387@kernel.org> (raw)
In-Reply-To: <20261021-shikra_display_overlays-v1-1-adaea735999f@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] arm64: dts: qcom: unit_address_vs_reg warning on panel@0 in HDMI overlay
--

commit 76425af69dfb56a6561d933cc0de85c2b87df761
Author: Mohit Dsor <mohit.dsor@oss.qualcomm.com>

arm64: dts: qcom: shikra-cqm-evk, shikra-cqs-evk: Add HDMI overlay

This commit adds a device tree overlay for the Shikra evaluation kits to
enable hdmi output via the lt9611uxd bridge on i2c4 and disable the default
dsi0 panel node.

> diff --git a/arch/arm64/boot/dts/qcom/shikra-cqm-cqs-evk-hdmi.dtso b/arch/arm64/boot/dts/qcom/shikra-cqm-cqs-evk-hdmi.dtso
> new file mode 100644
> index 0000000000000..a7b77114061a5
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/shikra-cqm-cqs-evk-hdmi.dtso

[ ... ]

> +&mdss_dsi0 {
> +	panel@0 {
> +		status = "disabled";
> +	};
> +};

[Severity: Low]
Does defining panel@0 inside &mdss_dsi0 without a reg property trigger a
dtc unit_address_vs_reg warning when building device trees with extra
warnings enabled?

In scripts/Makefile.dtbs, -Wno-unit_address_vs_reg is not passed to dtc
when extra warnings are enabled:

scripts/Makefile.dtbs:
ifeq ($(findstring 1,$(KBUILD_EXTRA_WARN)),)
DTC_FLAGS += -Wno-unit_address_vs_reg \
...

When dtc compiles shikra-cqm-cqs-evk-hdmi.dtso, check_unit_address_vs_reg()
in scripts/dtc/checks.c only exempts the fragment node that directly
contains __overlay__, not child nodes nested inside __overlay__:

scripts/dtc/checks.c:check_unit_address_vs_reg() {
	if (get_subnode(node, "__overlay__")) {
		/* HACK: Overlay fragments are a special case */
		return;
	}
	...
	} else {
		if (unitname[0])
			FAIL(c, dti, node, "node has a unit name, but no reg or ranges property");
	}
}

Because panel@0 has a unit address and no reg property in the overlay, dtc
warns on /fragment@2/__overlay__/panel@0.

Could panel@0 be given a label in arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts
and arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts so the overlay can disable it
via a top-level phandle reference (or specify #address-cells, #size-cells,
and reg = <0> here)?

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261021-shikra_display_overlays-v1-0-adaea735999f@oss.qualcomm.com?part=1

  reply	other threads:[~2026-10-21 14:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21 14:21 [PATCH 0/7] arm64: dts: qcom: shikra: Add display overlays for EVK boards vishnu.saini
2026-10-21 14:21 ` [PATCH 1/7] arm64: dts: qcom: shikra-cqm-evk, shikra-cqs-evk: Add HDMI overlay vishnu.saini
2026-10-21 14:37   ` sashiko-bot [this message]
2026-10-22  8:13   ` Konrad Dybcio
2026-10-21 14:21 ` [PATCH 2/7] arm64: dts: qcom: shikra-iqs-evk: Add DLC0697 panel overlay Vishnu Saini
2026-10-21 14:21 ` [PATCH 3/7] arm64: dts: qcom: shikra-iqs-evk: Add AUO G133HAN01 LVDS " vishnu.saini
2026-10-21 14:33   ` sashiko-bot
2026-10-21 14:21 ` [PATCH 4/7] arm64: defconfig: Enable RPi touchscreen V2 regulator and ILI9881C panel Vishnu Saini
2026-10-21 14:21 ` [PATCH 5/7] arm64: dts: qcom: shikra-iqs-evk: Add RPi 7-inch DSI panel overlay vishnu.saini
2026-10-21 14:21 ` [PATCH 6/7] arm64: defconfig: Enable Waveshare DSI panel and touch GPIO drivers Vishnu Saini
2026-10-21 14:21 ` [PATCH 7/7] arm64: dts: qcom: shikra-iqs-evk: Add Waveshare 8-inch DSI panel overlay vishnu.saini
2026-10-21 14:37   ` sashiko-bot
2026-10-22  8:14 ` [PATCH 0/7] arm64: dts: qcom: shikra: Add display overlays for EVK boards Konrad Dybcio

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-180387@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=vishnu.saini@oss.qualcomm.com \
    /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