Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Komal Bajaj" <komal.bajaj@oss.qualcomm.com>
Cc: neil.armstrong@linaro.org, robh@kernel.org,
	devicetree@vger.kernel.org, olteanv@gmail.com, vkoul@kernel.org,
	linux-phy@lists.infradead.org, conor+dt@kernel.org
Subject: Re: [PATCH v7 5/5] arm64: dts: qcom: Add Shikra EVK boards
Date: Wed, 08 Jul 2026 12:26:52 +0000	[thread overview]
Message-ID: <20260708122652.8CB6F1F00A3D@smtp.kernel.org> (raw)
In-Reply-To: <20260708-shikra-dt-v7-5-977b65a300c1@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The CQS EVK board incorrectly includes the SoM device tree for the CQM variant, logically coupling a modem-less platform to a modem-equipped platform.
--

--- Patch [5]: [PATCH v7 5/5] arm64: dts: qcom: Add Shikra EVK boards ---
commit 4fcaf27e44972f2edd1677d38c5edd3906fd3d1a
Author: Komal Bajaj <komal.bajaj@oss.qualcomm.com>

arm64: dts: qcom: Add Shikra EVK boards

This commit adds device trees for the Shikra EVK platform, covering the
CQ2390M, CQ2390S, and IQ2390S SoM variants. It also introduces a common
carrier-board configuration shared across all variants.

> diff --git a/arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts b/arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts
> new file mode 100644
> index 0000000000000..b3f19a64d7aed
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts
> @@ -0,0 +1,40 @@
> +// SPDX-License-Identifier: BSD-3-Clause
> +/*
> + * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
> + */
> +
> +/dts-v1/;
> +
> +#include "shikra-cqm-som.dtsi"

[Severity: Low]
Is this the intended SoM include for the CQS EVK board?

This file appears to include the device tree for the CQM (with modem)
variant instead of the CQS variant. While it might currently only define shared
configurations, future CQM-specific additions could inadvertently propagate to
the CQS platform.

Should this include a CQS-specific or shared base .dtsi instead?

> +#include "shikra-evk.dtsi"
> +
> +/ {
> +	model = "Qualcomm Technologies, Inc. Shikra CQS EVK";

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260708-shikra-dt-v7-0-977b65a300c1@oss.qualcomm.com?part=5

      reply	other threads:[~2026-07-08 12:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-08 12:17 [PATCH v7 0/5] arm64: dts: qcom: Add initial device tree support for Shikra Komal Bajaj
2026-07-08 12:17 ` [PATCH v7 1/5] dt-bindings: arm: qcom: Document Shikra and its EVK boards Komal Bajaj
2026-07-08 12:17 ` [PATCH v7 2/5] arm64: dts: qcom: Introduce Shikra SoC base dtsi Komal Bajaj
2026-07-08 12:17 ` [PATCH v7 3/5] arm64: dts: qcom: Add Shikra CQ2390M SoM platform Komal Bajaj
2026-07-08 12:17 ` [PATCH v7 4/5] arm64: dts: qcom: Add Shikra IQ2390S " Komal Bajaj
2026-07-08 12:30   ` sashiko-bot
2026-07-08 12:17 ` [PATCH v7 5/5] arm64: dts: qcom: Add Shikra EVK boards Komal Bajaj
2026-07-08 12:26   ` 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=20260708122652.8CB6F1F00A3D@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=komal.bajaj@oss.qualcomm.com \
    --cc=linux-phy@lists.infradead.org \
    --cc=neil.armstrong@linaro.org \
    --cc=olteanv@gmail.com \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=vkoul@kernel.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