From: sashiko-bot@kernel.org
To: "Barnabás Czémán" <barnabas.czeman@mainlining.org>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 1/6] dt-bindings: power: qcom-rpmpd: Remove unused MSM8953 indices
Date: Tue, 29 Sep 2026 18:36:40 +0000 [thread overview]
Message-ID: <20260929183641.239A21F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260929-sdm632-rpmpd-v2-1-97ef8858161b@mainlining.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Critical] dt-bindings: ABI breakage by removing MSM8953_VDDMD index
--
commit e44d0dc9a145a838a007b1d8e81abb98d56a4d20
Author: Barnabás Czémán <barnabas.czeman@mainlining.org>
dt-bindings: power: qcom-rpmpd: Remove unused MSM8953 indices
This commit removes MSM8953_VDDMD and MSM8953_VDDMD_AO from the MSM8953 power
domain bindings, as the hardware now uses mss-supply as a regulator. It also
defines RPMPD_VDDMD for the SDM632 MSS.
> diff --git a/include/dt-bindings/power/qcom-rpmpd.h b/include/dt-bindings/power/qcom-rpmpd.h
> index 4371ac941f29d..120f8855b4275 100644
> --- a/include/dt-bindings/power/qcom-rpmpd.h
> +++ b/include/dt-bindings/power/qcom-rpmpd.h
[ ... ]
> @@ -84,8 +85,6 @@
> #define QM215_VDDMX_AO MSM8917_VDDMX_AO
>
> /* MSM8953 Power Domain Indexes */
> -#define MSM8953_VDDMD 0
> -#define MSM8953_VDDMD_AO 1
[Severity: Critical]
Does removing these identifiers explicitly break the established DT ABI?
Older compiled device trees (DTBs) for the MSM8953 platform encode the power
domain index 0 for MSM8953_VDDMD in the mss (modem) node's power-domains
property. Removing this index from the dt-bindings header and driver removes
support for these existing DTBs, causing a backward compatibility regression.
When booting a new kernel with an older DTB that uses MSM8953_VDDMD, the new
qcom_q6v5_mss driver expects an mss-supply regulator. With the old DTB, the
new kernel will fail to find mss-supply, rendering the modem subsystem
non-functional during system boot.
Is there a fallback mechanism planned to ensure older device trees still probe
successfully?
> #define MSM8953_VDDCX 2
> #define MSM8953_VDDCX_AO 3
> #define MSM8953_VDDCX_VFL 4
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260929-sdm632-rpmpd-v2-0-97ef8858161b@mainlining.org?part=1
next prev parent reply other threads:[~2026-09-29 18:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 18:28 [PATCH v2 0/6] MSM8953/SDM632 rpmpd/mss fixes Barnabás Czémán
2026-09-29 18:28 ` [PATCH v2 1/6] dt-bindings: power: qcom-rpmpd: Remove unused MSM8953 indices Barnabás Czémán
2026-09-29 18:36 ` sashiko-bot [this message]
2026-10-01 8:10 ` Krzysztof Kozlowski
2026-09-29 18:28 ` [PATCH v2 2/6] pmdomain: qcom: rpmpd: Split SDM632 pm domains from MSM8953 Barnabás Czémán
2026-09-29 18:44 ` sashiko-bot
2026-09-29 18:28 ` [PATCH v2 3/6] remoteproc: qcom_q6v5_mss: Use mss as regulator for MSM8953 Barnabás Czémán
2026-09-29 18:40 ` sashiko-bot
2026-09-29 18:28 ` [PATCH v2 4/6] dt-bindings: remoteproc: qcom,msm8916-mss-pil: Add SDM632 Barnabás Czémán
2026-09-29 18:28 ` [PATCH v2 5/6] remoteproc: qcom_q6v5_mss: Add SDM632 MSS Barnabás Czémán
2026-09-29 18:28 ` [PATCH v2 6/6] arm64: dts: qcom: sdm632: Correct power domains Barnabás Czémán
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=20260929183641.239A21F000FF@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