From: Vladlen Grachev via B4 Relay <devnull+webholt.gmail.com@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Abel Vesa <abelvesa@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Vladlen Grachev <webholt@gmail.com>
Subject: [PATCH] arm64: dts: qcom: msm8996-oneplus-common: Drop LVS2 voltage constraints
Date: Thu, 29 Oct 2026 18:12:17 +0000 [thread overview]
Message-ID: <20261029-op3t-lvs2-fix-v1-1-42ca9d992c20@gmail.com> (raw)
From: Vladlen Grachev <webholt@gmail.com>
Since commit 27880745470a ("arm64: dts: qcom: msm8996-oneplus: Add SLPI
VDD_PX"), OnePlus 3T no longer boots: the PM8994 RPM regulator device
fails to probe, so UFS, USB and the display never come up and the phone
hangs on the bootloader splash screen:
lvs2: failed to get the current voltage: -EINVAL
qcom_rpm_smd_regulator remoteproc:glink-edge:rpm-requests:regulators:
lvs2: devm_regulator_register() failed, ret=-22
qcom_rpm_smd_regulator remoteproc:glink-edge:rpm-requests:regulators:
probe with driver qcom_rpm_smd_regulator failed with error -22
The switch LVS2 cannot report its voltage, so the regulator core asks
its input supply, vdd_lvs1_2, which is not described on these
boards. Checking the 1.8 V constraint then fails with -EINVAL, and the
RPM regulator driver aborts the probe of all PM8994 regulators.
Drop the constraints, like apq8096-db820c, which describes LVS1/LVS2
without them. Keep the node, so that the SLPI still gets its px-supply.
Describing vdd_lvs1_2-supply as S4, as done on other MSM8996 boards,
would also work, but it would only serve the constraint, which has
nothing to enforce on a switch.
Tested on OnePlus 3T with the msm8996-mainline kernel based on v6.19.5.
Fixes: 27880745470a ("arm64: dts: qcom: msm8996-oneplus: Add SLPI VDD_PX")
Cc: stable@vger.kernel.org
Signed-off-by: Vladlen Grachev <webholt@gmail.com>
---
arch/arm64/boot/dts/qcom/msm8996-oneplus-common.dtsi | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/msm8996-oneplus-common.dtsi b/arch/arm64/boot/dts/qcom/msm8996-oneplus-common.dtsi
index 7a3f8afae..98fc45dc8 100644
--- a/arch/arm64/boot/dts/qcom/msm8996-oneplus-common.dtsi
+++ b/arch/arm64/boot/dts/qcom/msm8996-oneplus-common.dtsi
@@ -497,8 +497,6 @@ vreg_l32a_1p8: l32 {
};
vreg_lvs2a: lvs2 {
- regulator-min-microvolt = <1800000>;
- regulator-max-microvolt = <1800000>;
};
};
};
---
base-commit: f5672a3dff0291d6a45eb0c258b9d2baeb4dc577
change-id: 20261029-op3t-lvs2-fix-44c8905ce34f
Best regards,
--
Vladlen Grachev <webholt@gmail.com>
next reply other threads:[~2026-10-29 18:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 18:12 Vladlen Grachev via B4 Relay [this message]
2026-10-30 8:49 ` Konrad Dybcio
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=20261029-op3t-lvs2-fix-v1-1-42ca9d992c20@gmail.com \
--to=devnull+webholt.gmail.com@kernel.org \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=stable@vger.kernel.org \
--cc=webholt@gmail.com \
/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
all inboxes | Powered by JetHome®