From: Varadarajan Narayanan <quic_varada@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: <andersson@kernel.org>, <konradybcio@kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<lumag@kernel.org>, <linux-arm-msm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: qcom: ipq9574: Fix 'l2' regulator min/max voltages
Date: Tue, 24 Jun 2025 11:38:34 +0530 [thread overview]
Message-ID: <aFpA4mk2L/sxlpO1@hu-varada-blr.qualcomm.com> (raw)
In-Reply-To: <465751c4-a45a-41ce-ab65-ebddb71dd916@oss.qualcomm.com>
On Mon, Jun 23, 2025 at 01:34:22PM +0200, Konrad Dybcio wrote:
> On 6/23/25 1:32 PM, Varadarajan Narayanan wrote:
> > The min and max voltages on l2 regulator is 850000uV. This was
> > incorrectly set at 1800000uV earlier and that affected the
> > stability of the networking subsystem.
> >
> > Fixes: d5506524d9d9 ("arm64: dts: qcom: ipq9574: Add LDO regulator node")
> > Signed-off-by: Varadarajan Narayanan <quic_varada@quicinc.com>
> > ---
>
> Shouldn't there be a consumer for it, instead of it being always-on?
The uniphy block is the consumer of this voltage. The PMIC configures it
to 850000uV based on OTP settings and s/w doesn't change it as uniphy
doesn't do scaling.
-Varada
> > arch/arm64/boot/dts/qcom/ipq9574-rdp-common.dtsi | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/arch/arm64/boot/dts/qcom/ipq9574-rdp-common.dtsi b/arch/arm64/boot/dts/qcom/ipq9574-rdp-common.dtsi
> > index bdb396afb992..21b04a2c629d 100644
> > --- a/arch/arm64/boot/dts/qcom/ipq9574-rdp-common.dtsi
> > +++ b/arch/arm64/boot/dts/qcom/ipq9574-rdp-common.dtsi
> > @@ -106,8 +106,8 @@ ipq9574_s1: s1 {
> > };
> >
> > mp5496_l2: l2 {
> > - regulator-min-microvolt = <1800000>;
> > - regulator-max-microvolt = <1800000>;
> > + regulator-min-microvolt = <850000>;
> > + regulator-max-microvolt = <850000>;
> > regulator-always-on;
> > regulator-boot-on;
> > };
> >
> > base-commit: 5d4809e25903ab8e74034c1f23c787fd26d52934
next prev parent reply other threads:[~2025-06-24 6:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 11:32 Varadarajan Narayanan
2025-06-23 11:34 ` Konrad Dybcio
2025-06-24 6:08 ` Varadarajan Narayanan [this message]
2025-06-24 14:38 ` Konrad Dybcio
2025-06-25 10:24 ` Varadarajan Narayanan
2025-06-25 1:26 ` Dmitry Baryshkov
2025-06-25 10:35 ` Varadarajan Narayanan
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=aFpA4mk2L/sxlpO1@hu-varada-blr.qualcomm.com \
--to=quic_varada@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@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
all inboxes | Powered by JetHome®