Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Barnabás Czémán" <barnabas.czeman@mainlining.org>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 4/7] remoteproc: qcom_q6v5_mss: Use mss as regulator for MSM8953
Date: Fri, 02 Oct 2026 09:14:04 +0000	[thread overview]
Message-ID: <20261002091405.0E7F71F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20261002-sdm632-rpmpd-v3-4-95c47d0f26cf@mainlining.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] remoteproc: qcom_q6v5_mss: universal probe failure on MSM8953 due to missing mss-supply
--

commit 726993c6f2fb948fb92664f68a46c91f069ed760
Author: Barnabás Czémán <barnabas.czeman@mainlining.org>

remoteproc: qcom_q6v5_mss: Use mss as regulator for MSM8953

The commit modifies the MSM8953 MSS configuration to use an "mss" regulator
rather than a power domain. The device tree definition is updated to remove
the power domain, and the driver is updated to expect the new active supply.

> diff --git a/arch/arm64/boot/dts/qcom/msm8953.dtsi b/arch/arm64/boot/dts/qcom/msm8953.dtsi
> index 753167c3f8619..c7dc08858d542 100644
> --- a/arch/arm64/boot/dts/qcom/msm8953.dtsi
> +++ b/arch/arm64/boot/dts/qcom/msm8953.dtsi
> @@ -1451,9 +1451,8 @@ mpss: remoteproc@4080000 {
>  					  "handover", "stop-ack";
>  
>  			power-domains = <&rpmpd MSM8953_VDDCX>,
> -					<&rpmpd MSM8953_VDDMX>,
> -					<&rpmpd MSM8953_VDDMD>;
> -			power-domain-names = "cx", "mx","mss";
> +					<&rpmpd MSM8953_VDDMX>;
> +			power-domain-names = "cx", "mx";

[Severity: High]
The old power domain is removed but the required mss-supply replacement to power
the MSS hardware is missing.

Is it expected that mss-supply is missing here?

Without mss-supply in the device tree, devm_regulator_get(dev, "mss") will
return either -ENODEV or a dummy regulator.

>  
>  			clocks = <&gcc GCC_MSS_CFG_AHB_CLK>,
>  				 <&gcc GCC_MSS_Q6_BIMC_AXI_CLK>,

[ ... ]

> diff --git a/drivers/remoteproc/qcom_q6v5_mss.c b/drivers/remoteproc/qcom_q6v5_mss.c
> index 2f71ed2feff69..8f6312213e1ab 100644
> --- a/drivers/remoteproc/qcom_q6v5_mss.c
> +++ b/drivers/remoteproc/qcom_q6v5_mss.c
> @@ -2728,6 +2728,14 @@ static const struct rproc_hexagon_res msm8953_mss = {
>  		},
>  		{}
>  	},
> +	.active_supply = (struct qcom_mss_reg_res[]) {
> +		{
> +			.supply = "mss",
> +			.uV = 1050000,
> +			.uA = 100000,
> +		},

[Severity: High]
This makes the "mss" regulator mandatory and strictly requires a specific
voltage to be set.

Since a dummy regulator lacks voltage-setting operations, an unconditional call
to regulator_set_voltage() in q6v5_regulator_enable() will return -EINVAL,
causing the driver to unconditionally fail to probe:

drivers/remoteproc/qcom_q6v5_mss.c:q6v5_regulator_enable() {
    ...
			ret = regulator_set_voltage(regs[i].reg,
					regs[i].uV, INT_MAX);
			if (ret) {
    ...
}

Could this cause the modem driver to fail probing, making the modem unusable
on all MSM8953 devices (and SDM632 devices due to later patches in the series)?

> +		{}
> +	},

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261002-sdm632-rpmpd-v3-0-95c47d0f26cf@mainlining.org?part=4

  reply	other threads:[~2026-10-02  9:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 22:38 [PATCH v3 0/7] MSM8953/SDM632 rpmpd/mss fixes Barnabás Czémán
2026-10-01 22:38 ` [PATCH v3 1/7] dt-bindings: power: qcom-rpmpd: define RPMPD_VDDMD Barnabás Czémán
2026-10-02  9:14   ` sashiko-bot
2026-10-02  9:57   ` Krzysztof Kozlowski
2026-10-02 14:04     ` Barnabás Czémán
2026-10-05  7:00       ` Dmitry Baryshkov
2026-10-01 22:38 ` [PATCH v3 2/7] dt-bindings: power: qcom,rpmpd: Add SDM632 Barnabás Czémán
2026-10-05  7:01   ` Dmitry Baryshkov
2026-10-01 22:38 ` [PATCH v3 3/7] pmdomain: qcom: rpmpd: Split SDM632 pm domains from MSM8953 Barnabás Czémán
2026-10-02  9:14   ` sashiko-bot
2026-10-05  7:04   ` Dmitry Baryshkov
2026-10-06 18:21     ` Barnabás Czémán
2026-10-01 22:38 ` [PATCH v3 4/7] remoteproc: qcom_q6v5_mss: Use mss as regulator for MSM8953 Barnabás Czémán
2026-10-02  9:14   ` sashiko-bot [this message]
2026-10-05  7:06   ` Dmitry Baryshkov
2026-10-06 18:18     ` Barnabás Czémán
2026-10-01 22:38 ` [PATCH v3 5/7] dt-bindings: remoteproc: qcom,msm8916-mss-pil: Add SDM632 Barnabás Czémán
2026-10-02  9:14   ` sashiko-bot
2026-10-02 10:01   ` Krzysztof Kozlowski
2026-10-02 14:05     ` Barnabás Czémán
2026-10-01 22:38 ` [PATCH v3 6/7] remoteproc: qcom_q6v5_mss: Add SDM632 MSS Barnabás Czémán
2026-10-01 22:38 ` [PATCH v3 7/7] arm64: dts: qcom: sdm632: Correct power domains Barnabás Czémán
2026-10-02  9:14   ` 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=20261002091405.0E7F71F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=barnabas.czeman@mainlining.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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