LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org> To: Stephen Boyd <swboyd@chromium.org> Cc: Andy Gross <agross@kernel.org>, Linus Walleij <linus.walleij@linaro.org>, Rob Herring <robh+dt@kernel.org>, Mark Rutland <mark.rutland@arm.com>, Pedro Sousa <pedrom.sousa@synopsys.com>, "James E.J. Bottomley" <jejb@linux.ibm.com>, "Martin K. Petersen" <martin.petersen@oracle.com>, linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org, Evan Green <evgreen@chromium.org> Subject: Re: [PATCH 3/3] arm64: dts: qcom: sdm845-mtp: Specify UFS device-reset GPIO Date: Tue, 4 Jun 2019 15:09:10 -0700 [thread overview] Message-ID: <20190604220910.GA4814@minitux> (raw) In-Reply-To: <5cf69ad2.1c69fb81.216a9.30f8@mx.google.com> On Tue 04 Jun 09:22 PDT 2019, Stephen Boyd wrote: > Quoting Bjorn Andersson (2019-06-04 00:20:01) > > Specify the UFS device-reset gpio, so that the controller will issue a > > reset of the UFS device. > > > > Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org> > > --- > > arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 2 ++ > > 1 file changed, 2 insertions(+) > > > > diff --git a/arch/arm64/boot/dts/qcom/sdm845-mtp.dts b/arch/arm64/boot/dts/qcom/sdm845-mtp.dts > > index 2e78638eb73b..d116a0956a9c 100644 > > --- a/arch/arm64/boot/dts/qcom/sdm845-mtp.dts > > +++ b/arch/arm64/boot/dts/qcom/sdm845-mtp.dts > > @@ -388,6 +388,8 @@ > > &ufs_mem_hc { > > status = "okay"; > > > > + device-reset-gpios = <&tlmm 150 GPIO_ACTIVE_LOW>; > > + > > We had to do something similar on one particular brand of UFS that we had. I > think it was an SK Hynix part that had trouble and wouldn't provision properly. > Either way, we did this with a pinctrl toggle in the DTS where the "init" state > has the UFS_RESET pin asserted and then "default" state has the pin deasserted. > That was good enough to make this work. > Thanks for pointing this out, I forgot to attribute these downstream changes. I can see how this works, but I must say I find it quite hackish. The downstream solution seems to have evolved this into naming these states and jumping between them (with the appropriate sleeps) during a host reset as well. But thanks for the confirmation that there's more than John's memory that needs this. Regards, Bjorn > &ufs_mem_hc { > pinctrl-names = "init", "default"; > pinctrl-0 = <&ufs_dev_reset_assert>; > pinctrl-1 = <&ufs_dev_reset_deassert>; > }; > > ufs_dev_reset_assert: ufs_dev_reset_assert { > config { > pins = "ufs_reset"; > bias-pull-down; /* default: pull down */ > drive-strength = <8>; /* default: 3.1 mA */ > output-low; /* active low reset */ > }; > }; > > ufs_dev_reset_deassert: ufs_dev_reset_deassert { > config { > pins = "ufs_reset"; > bias-pull-down; /* default: pull down */ > drive-strength = <8>; > output-high; /* active low reset */ > }; > };
next prev parent reply other threads:[~2019-06-04 22:09 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-06-04 7:19 [PATCH 0/3] (Qualcomm) UFS device reset support Bjorn Andersson 2019-06-04 7:19 ` [PATCH 1/3] pinctrl: qcom: sdm845: Expose ufs_reset as gpio Bjorn Andersson 2019-06-07 21:26 ` Linus Walleij 2019-06-04 7:20 ` [PATCH 2/3] scsi: ufs: Allow resetting the UFS device Bjorn Andersson 2019-06-04 8:13 ` [EXT] " Bean Huo (beanhuo) 2019-06-04 18:10 ` John Stultz 2019-06-04 22:30 ` Bjorn Andersson 2019-06-05 21:17 ` Bean Huo (beanhuo) 2019-06-04 15:25 ` Stephen Boyd 2019-06-04 22:20 ` Bjorn Andersson 2019-06-04 7:20 ` [PATCH 3/3] arm64: dts: qcom: sdm845-mtp: Specify UFS device-reset GPIO Bjorn Andersson 2019-06-04 16:22 ` Stephen Boyd 2019-06-04 22:09 ` Bjorn Andersson [this message] 2019-06-07 22:20 ` Linus Walleij 2019-06-04 22:00 ` [PATCH 0/3] (Qualcomm) UFS device reset support John Stultz 2019-06-05 5:50 ` Avri Altman 2019-06-05 6:01 ` Bjorn Andersson 2019-06-05 9:32 ` Avri Altman 2019-06-06 0:39 ` Bjorn Andersson 2019-06-06 6:32 ` Avri Altman 2019-06-06 7:09 ` Bjorn Andersson
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=20190604220910.GA4814@minitux \ --to=bjorn.andersson@linaro.org \ --cc=agross@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=evgreen@chromium.org \ --cc=jejb@linux.ibm.com \ --cc=linus.walleij@linaro.org \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-gpio@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-scsi@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=martin.petersen@oracle.com \ --cc=pedrom.sousa@synopsys.com \ --cc=robh+dt@kernel.org \ --cc=swboyd@chromium.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: linkBe 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).