devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Abel Vesa <abel.vesa@linaro.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: qcom: sm8550-mtp: Add UFS host controller and PHY node
Date: Tue, 22 Nov 2022 22:51:04 +0200	[thread overview]
Message-ID: <Y302OBP1f8W6pr5A@linaro.org> (raw)
In-Reply-To: <22a41a8c-9b4a-ecca-ddd2-5e217d00d20c@linaro.org>

On 22-11-16 13:56:36, Konrad Dybcio wrote:
> 
> 
> On 16/11/2022 13:51, Abel Vesa wrote:
> > Enable UFS host controller and PHY node on SM8550 MTP board.
> > 
> > Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
> > ---
> >   arch/arm64/boot/dts/qcom/sm8550-mtp.dts | 22 ++++++++++++++++++++++
> >   1 file changed, 22 insertions(+)
> > 
> > diff --git a/arch/arm64/boot/dts/qcom/sm8550-mtp.dts b/arch/arm64/boot/dts/qcom/sm8550-mtp.dts
> > index d4c8d5b2497e..fef7793a7dec 100644
> > --- a/arch/arm64/boot/dts/qcom/sm8550-mtp.dts
> > +++ b/arch/arm64/boot/dts/qcom/sm8550-mtp.dts
> > @@ -417,3 +417,25 @@ data-pins {
> >   &uart7 {
> >   	status = "okay";
> >   };
> > +
> > +&ufs_mem_hc {
> > +	status = "okay";
> Status last, please.

Yep. Will do.

> 
> > +
> > +	reset-gpios = <&tlmm 210 GPIO_ACTIVE_LOW>;
> > +
> > +	vcc-supply = <&vreg_l17b_2p5>;
> > +	vcc-max-microamp = <1300000>;
> All these -microamp properties are downstream and do not exist in the
> mainline kernel. Remove them.
> 

Actually, ufshcd-qcom complains if they are missing:

[    3.287836] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: unable
to find vcc-max-microamp
[    3.331904] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: unable
to find vccq-max-microamp
[    3.346766] ufshcd-qcom 1d84000.ufshc: ufshcd_populate_vreg: unable
to find vccq2-max-microamp

> Konrad
> > +	vccq-supply = <&vreg_l1g_1p2>;
> > +	vccq-max-microamp = <1200000>;
> > +	vccq2-supply = <&vreg_l3g_1p2>;
> > +	vccq2-max-microamp = <100>;
> > +};
> > +
> > +&ufs_mem_phy {
> > +	status = "okay";
> > +
> > +	vdda-phy-supply = <&vreg_l1d_0p88>;
> > +	vdda-phy-max-microamp = <188000>;

These ones from PHY I can drop, since the driver won't complain.

> > +	vdda-pll-supply = <&vreg_l3e_1p2>;
> > +	vdda-pll-max-microamp = <18300>;
> > +};

      reply	other threads:[~2022-11-22 20:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16 12:51 [PATCH 0/2] arm64: dts: qcom: sm8550: Add UFS HC and PHY Abel Vesa
2022-11-16 12:51 ` [PATCH 1/2] arm64: dts: qcom: sm8550: Add UFS host controller and phy nodes Abel Vesa
2022-11-16 12:58   ` Konrad Dybcio
2022-11-16 13:31   ` Johan Hovold
2022-11-16 12:51 ` [PATCH 2/2] arm64: dts: qcom: sm8550-mtp: Add UFS host controller and PHY node Abel Vesa
2022-11-16 12:56   ` Konrad Dybcio
2022-11-22 20:51     ` Abel Vesa [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=Y302OBP1f8W6pr5A@linaro.org \
    --to=abel.vesa@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@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=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).