From: Naveen Kumar Goud Arepalli <quic_narepall@quicinc.com>
To: quic_nitirawa@quicinc.com, agross@kernel.org,
andersson@kernel.org, konrad.dybcio@linaro.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Naveen Kumar Goud Arepalli <quic_narepall@quicinc.com>
Subject: [PATCH V1] arm64: dts: qcom: sa8775p-ride: Remove min and max voltages for L8A
Date: Tue, 25 Jul 2023 15:30:07 +0530 [thread overview]
Message-ID: <20230725100007.14775-1-quic_narepall@quicinc.com> (raw)
L8A is the supply for UFS VCC, UFS specification allows different VCC
configurations for UFS devices.
-UFS 2.x devices: 2.70V - 3.60V
-UFS 3.x devices: 2.40V - 2.70V
As sa8775p-ride supports both ufs 2.x and ufs 3.x devices, remove min/max
voltages for L8A regulator. Initial voltage of L8A will be set to 2.504v
or 2.952v during PON depending on the UFS device type. On sa8775, UFS is
the only client in Linux for L8A and this regulator will be voted only
for enabling/disabling.
Signed-off-by: Naveen Kumar Goud Arepalli <quic_narepall@quicinc.com>
---
arch/arm64/boot/dts/qcom/sa8775p-ride.dts | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/sa8775p-ride.dts b/arch/arm64/boot/dts/qcom/sa8775p-ride.dts
index ed76680410b4..6f3891a09e59 100644
--- a/arch/arm64/boot/dts/qcom/sa8775p-ride.dts
+++ b/arch/arm64/boot/dts/qcom/sa8775p-ride.dts
@@ -98,8 +98,6 @@
vreg_l8a: ldo8 {
regulator-name = "vreg_l8a";
- regulator-min-microvolt = <2504000>;
- regulator-max-microvolt = <3300000>;
regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
regulator-allow-set-load;
regulator-allowed-modes = <RPMH_REGULATOR_MODE_LPM
--
2.17.1
next reply other threads:[~2023-07-25 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 10:00 Naveen Kumar Goud Arepalli [this message]
2023-07-25 21:50 ` Andrew Halaney
2023-07-26 12:32 ` Naveen Kumar Goud Arepalli (QUIC)
2023-07-26 13:07 ` Krzysztof Kozlowski
2023-08-04 8:04 ` Naveen Kumar Goud Arepalli (QUIC)
2023-08-04 9:43 ` Krzysztof Kozlowski
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=20230725100007.14775-1-quic_narepall@quicinc.com \
--to=quic_narepall@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_nitirawa@quicinc.com \
--cc=robh+dt@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
all inboxes | Powered by JetHome®