From: Gianluca Boiano <morf3089@gmail.com>
To: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Cc: andersson@kernel.org, konradybcio@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, robh@kernel.org, david@ixit.cz,
Gianluca Boiano <morf3089@gmail.com>
Subject: [PATCH 3/7] arm64: dts: qcom: sdm660-xiaomi-lavender: fix regulator and SD settings
Date: Tue, 20 Jan 2026 19:00:48 +0100 [thread overview]
Message-ID: <20260120180052.1031231-4-morf3089@gmail.com> (raw)
In-Reply-To: <20260120180052.1031231-1-morf3089@gmail.com>
Fix regulator configurations to ensure stable operation:
- vreg_l2b_2p95: Increase max voltage from 2696mV to 3100mV to support
proper SD card voltage signaling
- vreg_l3b_3p3: Add regulator-always-on to keep the regulator enabled
during boot
- vreg_l10a_1p8: Add regulator-system-load of 14000uA for proper USB PHY
PLL operation
Also enable the SD card controller (sdhc_2) which was left disabled.
Signed-off-by: Gianluca Boiano <morf3089@gmail.com>
---
arch/arm64/boot/dts/qcom/sdm660-xiaomi-lavender.dts | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/qcom/sdm660-xiaomi-lavender.dts b/arch/arm64/boot/dts/qcom/sdm660-xiaomi-lavender.dts
index 6467cb4dfd16..9a6dda47941c 100644
--- a/arch/arm64/boot/dts/qcom/sdm660-xiaomi-lavender.dts
+++ b/arch/arm64/boot/dts/qcom/sdm660-xiaomi-lavender.dts
@@ -82,7 +82,7 @@ vreg_l1b_0p925: l1 {
/* SDHCI 3.3V signal doesn't seem to be supported. */
vreg_l2b_2p95: l2 {
regulator-min-microvolt = <1648000>;
- regulator-max-microvolt = <2696000>;
+ regulator-max-microvolt = <3100000>;
regulator-enable-ramp-delay = <250>;
regulator-allow-set-load;
};
@@ -92,6 +92,7 @@ vreg_l3b_3p3: l3 {
regulator-max-microvolt = <3300000>;
regulator-enable-ramp-delay = <250>;
regulator-allow-set-load;
+ regulator-always-on;
};
vreg_l4b_2p95: l4 {
@@ -239,6 +240,7 @@ vreg_l10a_1p8: l10 {
regulator-max-microvolt = <1950000>;
regulator-enable-ramp-delay = <250>;
regulator-allow-set-load;
+ regulator-system-load = <14000>;
};
vreg_l11a_1p8: l11 {
@@ -295,3 +297,7 @@ vreg_l19a_3p3: l19 {
};
};
};
+
+&sdhc_2 {
+ status = "okay";
+};
--
2.52.0
next prev parent reply other threads:[~2026-01-20 18:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 18:00 [PATCH 0/7] arm64: dts: qcom: add support for Xiaomi SDM636/SDM660 devices Gianluca Boiano
2026-01-20 18:00 ` [PATCH 1/7] dt-bindings: arm: qcom: add " Gianluca Boiano
2026-01-21 8:14 ` Krzysztof Kozlowski
2026-01-20 18:00 ` [PATCH 2/7] arm64: dts: qcom: sdm660: add common Xiaomi SDM636/SDM660 include file Gianluca Boiano
2026-01-21 12:35 ` Konrad Dybcio
2026-01-21 20:30 ` Gianluca Boiano
2026-01-20 18:00 ` Gianluca Boiano [this message]
2026-01-21 11:27 ` [PATCH 3/7] arm64: dts: qcom: sdm660-xiaomi-lavender: fix regulator and SD settings Konrad Dybcio
2026-01-21 20:30 ` Gianluca Boiano
2026-01-22 11:40 ` Konrad Dybcio
2026-01-22 16:34 ` Alexey Minnekhanov
2026-01-22 20:47 ` Konrad Dybcio
2026-01-22 16:44 ` Alexey Minnekhanov
2026-01-23 9:26 ` Konrad Dybcio
2026-01-23 20:11 ` Alexey Minnekhanov
2026-01-25 11:10 ` Dmitry Baryshkov
2026-01-28 13:24 ` Konrad Dybcio
2026-01-28 13:52 ` Dmitry Baryshkov
2026-01-21 12:36 ` Konrad Dybcio
2026-01-20 18:00 ` [PATCH 4/7] arm64: dts: qcom: add device tree for Xiaomi Redmi Note 6 Pro (tulip) Gianluca Boiano
2026-01-21 12:42 ` Konrad Dybcio
2026-01-21 20:30 ` Gianluca Boiano
2026-01-22 17:12 ` Alexey Minnekhanov
2026-01-22 20:45 ` Konrad Dybcio
2026-01-20 18:00 ` [PATCH 5/7] arm64: dts: qcom: add device tree for Xiaomi Redmi Note 5 Pro (whyred) Gianluca Boiano
2026-01-20 18:00 ` [PATCH 6/7] arm64: dts: qcom: add device tree for Xiaomi Mi A2 (jasmine) Gianluca Boiano
2026-01-20 18:00 ` [PATCH 7/7] arm64: dts: qcom: add device tree for Xiaomi Mi 8 Lite (platina) Gianluca Boiano
2026-01-21 21:02 ` [PATCH 0/7] arm64: dts: qcom: Add Xiaomi SDM636/SDM660 devices Gianluca Boiano
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=20260120180052.1031231-4-morf3089@gmail.com \
--to=morf3089@gmail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robh@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