Linux-PHY Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Komal Bajaj" <komal.bajaj@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, linux-phy@lists.infradead.org,
	neil.armstrong@linaro.org, conor+dt@kernel.org,
	olteanv@gmail.com, vkoul@kernel.org, robh@kernel.org
Subject: Re: [PATCH v3 3/5] arm64: dts: qcom: Add Shikra CQ2390M SoM platform
Date: Fri, 22 May 2026 19:10:12 +0000	[thread overview]
Message-ID: <20260522191013.23B0C1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260522-shikra-dt-v3-3-80ffde8a3dc4@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The commit message claims to add PM8005 PMIC regulator definitions, but the patch explicitly disables the PM8005 regulators and provides no configuration.
--

commit b8207cdfd80924e291ee52448a105708aa7b6a09
Author: Komal Bajaj <komal.bajaj@oss.qualcomm.com>

arm64: dts: qcom: Add Shikra CQ2390M SoM platform

This commit adds the device tree include for the CQ2390M variant of the
Shikra System-on-Module. It integrates the Shikra SoC and includes PMIC
regulator configurations for the retail SoM.

> The DTSI includes the common shikra.dtsi, adds PM4125 and PM8005 PMIC
> regulator definitions specific to this variant.

[ ... ]

> diff --git a/arch/arm64/boot/dts/qcom/shikra-cqm-som.dtsi b/arch/arm64/boot/dts/qcom/shikra-cqm-som.dtsi
> new file mode 100644
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/shikra-cqm-som.dtsi

[ ... ]

> +&pm8005_regulators {
> +	status = "disabled";
> +};

[Severity: Medium]
Is the commit message inaccurate, or are the definitions for the PM8005
regulators missing from this patch?

The commit message states that PM8005 PMIC regulator definitions are
added, but the code explicitly disables them without providing any
configuration. If the SoM variant requires the PM8005 regulators to power
hardware components, will leaving them disabled result in runtime failures?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260522-shikra-dt-v3-0-80ffde8a3dc4@oss.qualcomm.com?part=3

-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

  reply	other threads:[~2026-05-22 19:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-22 18:02 [PATCH v3 0/5] arm64: dts: qcom: Add initial device tree support for Shikra Komal Bajaj
2026-05-22 18:02 ` [PATCH v3 1/5] dt-bindings: arm: qcom: Document Shikra and its EVK boards Komal Bajaj
2026-05-22 18:02 ` [PATCH v3 2/5] arm64: dts: qcom: Introduce Shikra SoC base dtsi Komal Bajaj
2026-05-22 18:02 ` [PATCH v3 3/5] arm64: dts: qcom: Add Shikra CQ2390M SoM platform Komal Bajaj
2026-05-22 19:10   ` sashiko-bot [this message]
2026-05-22 18:02 ` [PATCH v3 4/5] arm64: dts: qcom: Add Shikra IQ2390S " Komal Bajaj
2026-05-22 18:02 ` [PATCH v3 5/5] arm64: dts: qcom: Add Shikra EVK boards Komal Bajaj
2026-05-22 19:39   ` sashiko-bot

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=20260522191013.23B0C1F000E9@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