From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: Evan Green <evgreen@chromium.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Kishon Vijay Abraham <kishon@ti.com>
Cc: Andy Gross <andy.gross@linaro.org>,
Lee Jones <lee.jones@linaro.org>,
Jeffrey Hugo <jhugo@codeaurora.org>,
MSM <linux-arm-msm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH v2 1/2] arm64: dts: msm8998: Add UFS phy reset
Date: Mon, 1 Apr 2019 16:38:37 +0200 [thread overview]
Message-ID: <57ba143d-eea5-4f8c-10b8-9f45fc9a8001@free.fr> (raw)
In-Reply-To: <CAE=gft710gv2+k86pwVhucJFxAcN-AUZhGnT9Hm2gLutV+PCpg@mail.gmail.com>
Fixup MSM8998 UFS DT nodes now that Evan's reset series has landed.
https://lore.kernel.org/lkml/20190321171800.104681-1-evgreen@chromium.org/
Signed-off-by: Marc Gonzalez <marc.w.gonzalez@free.fr>
---
arch/arm64/boot/dts/qcom/msm8998.dtsi | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8998.dtsi b/arch/arm64/boot/dts/qcom/msm8998.dtsi
index 893eeaaaedec..1cffa706c909 100644
--- a/arch/arm64/boot/dts/qcom/msm8998.dtsi
+++ b/arch/arm64/boot/dts/qcom/msm8998.dtsi
@@ -1085,6 +1085,7 @@
phy-names = "ufsphy";
lanes-per-direction = <2>;
power-domains = <&gcc UFS_GDSC>;
+ #reset-cells = <1>;
clock-names =
"core_clk",
@@ -1132,6 +1133,9 @@
<&gcc GCC_UFS_CLKREF_CLK>,
<&gcc GCC_UFS_PHY_AUX_CLK>;
+ reset-names = "ufsphy";
+ resets = <&ufshc 0>;
+
ufsphy_lanes: lanes@1da7400 {
reg = <0x01da7400 0x128>,
<0x01da7600 0x1fc>,
--
2.17.1
next prev parent reply other threads:[~2019-04-01 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 17:05 [PATCH] arm64: dts: msm8998: Add UFS phy reset Evan Green
2019-03-26 17:14 ` Marc Gonzalez
2019-03-26 19:39 ` Evan Green
2019-04-01 14:38 ` Marc Gonzalez [this message]
2019-04-01 14:42 ` [PATCH v2 2/2] dt-bindings: phy-qcom-qmp: Tweak qcom,msm8998-qmp-ufs-phy Marc Gonzalez
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=57ba143d-eea5-4f8c-10b8-9f45fc9a8001@free.fr \
--to=marc.w.gonzalez@free.fr \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=evgreen@chromium.org \
--cc=jhugo@codeaurora.org \
--cc=kishon@ti.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.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).