From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Niklas Cassel <niklas.cassel@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
David Brown <david.brown@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: pms405: increase s3 max voltage
Date: Fri, 26 Apr 2019 21:55:43 -0700 [thread overview]
Message-ID: <20190427045543.GG3137@builder> (raw)
In-Reply-To: <20190425121805.GA17362@centauri>
On Thu 25 Apr 05:18 PDT 2019, Niklas Cassel wrote:
> The commit description should be: arm64: dts: qcom: qcs404-evb:
>
> (The s3 regulator node moved during upstreaming.)
>
> Andy/Bjorn, could you please fix this before applying?
>
Picked up with the subject change.
Thanks,
Bjorn
> Kind regards,
> Niklas
>
> On Thu, Apr 25, 2019 at 01:34:29PM +0200, Niklas Cassel wrote:
> > Increase s3 max voltage in accordance to QCS404 CPR Fusing Guide Rev 6.0
> >
> > Signed-off-by: Niklas Cassel <niklas.cassel@linaro.org>
> > ---
> > arch/arm64/boot/dts/qcom/qcs404-evb.dtsi | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/arch/arm64/boot/dts/qcom/qcs404-evb.dtsi b/arch/arm64/boot/dts/qcom/qcs404-evb.dtsi
> > index 2c3127167e3c..6910fc663fe1 100644
> > --- a/arch/arm64/boot/dts/qcom/qcs404-evb.dtsi
> > +++ b/arch/arm64/boot/dts/qcom/qcs404-evb.dtsi
> > @@ -64,7 +64,7 @@
> > regulator-boot-on;
> > regulator-name = "vdd_apc";
> > regulator-min-microvolt = <1048000>;
> > - regulator-max-microvolt = <1352000>;
> > + regulator-max-microvolt = <1384000>;
> > };
> > };
> >
> > --
> > 2.20.1
> >
prev parent reply other threads:[~2019-04-27 4:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 11:34 [PATCH] arm64: dts: pms405: increase s3 max voltage Niklas Cassel
2019-04-25 12:18 ` Niklas Cassel
2019-04-27 4:55 ` Bjorn Andersson [this message]
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=20190427045543.GG3137@builder \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=niklas.cassel@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).