From: sashiko-bot@kernel.org
To: "Nabige Aala" <nabige.aala@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v5 1/4] arm64: dts: qcom: shikra: Add MDSS display subsystem
Date: Wed, 30 Sep 2026 11:25:54 +0000 [thread overview]
Message-ID: <20260930112555.69F211F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260930-shikra-dt-changes-v5-1-8eaf658a0e38@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dts: incorrect over-indentation of the mdss node
--
commit c036145cd42553cee75513d9d43a23d346a733a4
Author: Nabige Aala <nabige.aala@oss.qualcomm.com>
arm64: dts: qcom: shikra: Add MDSS display subsystem
This commit adds the SoC-level display subsystem nodes for Qualcomm Shikra,
including the MDSS wrapper, DPU display controller, DSI host controller,
and 14nm DSI PHY.
> diff --git a/arch/arm64/boot/dts/qcom/shikra.dtsi b/arch/arm64/boot/dts/qcom/shikra.dtsi
> index 9823c591b02b1..4ff85c1c8fddc 100644
> --- a/arch/arm64/boot/dts/qcom/shikra.dtsi
> +++ b/arch/arm64/boot/dts/qcom/shikra.dtsi
[ ... ]
> @@ -2809,6 +2810,207 @@ adreno_smmu: iommu@59a0000 {
> power-domains = <&gpucc GPU_CX_GDSC>;
> };
>
> + mdss: display-subsystem@5e00000 {
> + compatible = "qcom,shikra-mdss", "qcom,qcm2290-mdss";
[Severity: Low]
This isn't a bug, but does the mdss node have incorrect over-indentation here?
The node is declared with 4 tabs, while its properties (e.g., compatible)
and children use 3 tabs, and its siblings use 2 tabs. This creates visually
confusing formatting where a parent is indented further than its children.
Could this be adjusted to match standard device tree coding style?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260930-shikra-dt-changes-v5-0-8eaf658a0e38@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-09-30 11:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 11:15 [PATCH v5 0/4] arm64: qcom: dts: Add display support for Qualcomm Shikra Nabige Aala
2026-09-30 11:15 ` [PATCH v5 1/4] arm64: dts: qcom: shikra: Add MDSS display subsystem Nabige Aala
2026-09-30 11:25 ` sashiko-bot [this message]
2026-09-30 11:15 ` [PATCH v5 2/4] arm64: dts: qcom: shikra-cqs-evk: Enable display and add ili7807s panel Nabige Aala
2026-09-30 11:27 ` sashiko-bot
2026-09-30 11:15 ` [PATCH v5 3/4] arm64: dts: qcom: shikra-cqm-evk: " Nabige Aala
2026-09-30 11:26 ` sashiko-bot
2026-09-30 11:15 ` [PATCH v5 4/4] arm64: defconfig: Enable ILI7807S DSI panel driver Nabige Aala
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=20260930112555.69F211F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=nabige.aala@oss.qualcomm.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