Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Komal Bajaj" <komal.bajaj@oss.qualcomm.com>
Cc: robh@kernel.org, linux-phy@lists.infradead.org,
	neil.armstrong@linaro.org, vkoul@kernel.org, olteanv@gmail.com,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 3/4] arm64: dts: qcom: Add Shikra CQM SoM platform
Date: Wed, 13 May 2026 04:28:35 +0000	[thread overview]
Message-ID: <20260513042836.073F9C2BCB7@smtp.kernel.org> (raw)
In-Reply-To: <20260512-shikra-dt-v1-3-716438330dd0@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [High] The PMIC regulator definitions omit their required input supply dependencies (e.g., `vdd_s2-supply`, `vdd_l3-supply`), breaking the power hierarchy.
- [Medium] The device tree inaccurately hardcodes the `compatible` string to a different PMIC model (`qcom,rpm-pm2250-regulators`) instead of explicitly identifying the actual hardware (PM4125).
--

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

arm64: dts: qcom: Add Shikra CQM SoM platform

Add device tree include for the CQM variant of the Shikra System-on-Module.
This variant integrates the Shikra SoC and PM4125 PMIC. The DTSI includes
the common shikra.dtsi and adds PM4125 PMIC regulator definitions.

> 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
> index 0000000000000..401e71720519d
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/shikra-cqm-som.dtsi
[ ... ]
> +&rpm_requests {
> +	regulators {
> +		compatible = "qcom,rpm-pm2250-regulators";

Since the commit message indicates this is a PM4125 PMIC, should the
compatible string include a specific identifier for the actual hardware?

Using a specific identifier like "qcom,rpm-pm4125-regulators" alongside
the fallback allows the kernel to apply specific quirks if PM4125 errata
are discovered later.

> +
> +		pm4125_s2: s2 {
> +			regulator-min-microvolt = <1000000>;
> +			regulator-max-microvolt = <1200000>;
> +		};

Do these regulators need to explicitly define their input supply dependencies
such as vdd_s2-supply?

Without these properties, the regulator framework might be unaware that the
PMIC regulators draw power from upstream supplies.

If the kernel dynamically manages the upstream supply and its reference count
drops to zero, could it be disabled, causing an unexpected power loss for
downstream components?

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260512-shikra-dt-v1-0-716438330dd0@oss.qualcomm.com?part=3

  reply	other threads:[~2026-05-13  4:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12  4:08 [PATCH 0/4] arm64: dts: qcom: Add initial device tree support for Shikra Komal Bajaj
2026-05-12  4:08 ` [PATCH 1/4] dt-bindings: arm: qcom: Document Shikra and its EVK boards Komal Bajaj
2026-05-12  4:08 ` [PATCH 2/4] arm64: dts: qcom: Introduce Shikra SoC base dtsi Komal Bajaj
2026-05-13  4:06   ` sashiko-bot
2026-05-12  4:08 ` [PATCH 3/4] arm64: dts: qcom: Add Shikra CQM SoM platform Komal Bajaj
2026-05-13  4:28   ` sashiko-bot [this message]
2026-05-13 12:01     ` Dmitry Baryshkov
2026-05-13 13:31     ` Rakesh Kota
2026-05-12  4:08 ` [PATCH 4/4] arm64: dts: qcom: Add Shikra CQM and CQS EVK boards Komal Bajaj
2026-05-13 12:04   ` Dmitry Baryshkov

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=20260513042836.073F9C2BCB7@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=krzk+dt@kernel.org \
    --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