From: Evan Green <evgreen@chromium.org>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: Stephen Boyd <swboyd@chromium.org>,
Marc Gonzalez <marc.w.gonzalez@free.fr>,
Can Guo <cang@codeaurora.org>,
Vivek Gautam <vivek.gautam@codeaurora.org>,
Douglas Anderson <dianders@chromium.org>,
Asutosh Das <asutoshd@codeaurora.org>,
Evan Green <evgreen@chromium.org>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, Andy Gross <andy.gross@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
David Brown <david.brown@linaro.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: [PATCH v5 4/8] arm64: dts: sdm845: Add UFS PHY reset
Date: Thu, 21 Mar 2019 10:17:56 -0700 [thread overview]
Message-ID: <20190321171800.104681-5-evgreen@chromium.org> (raw)
In-Reply-To: <20190321171800.104681-1-evgreen@chromium.org>
Wire up the reset controller in the Qcom UFS controller for the PHY.
This will be used to toggle PHY reset during initialization of the PHY.
Signed-off-by: Evan Green <evgreen@chromium.org>
Reviewed-by: Stephen Boyd <swboyd@chromium.org>
---
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in v2: None
arch/arm64/boot/dts/qcom/sdm845.dtsi | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi b/arch/arm64/boot/dts/qcom/sdm845.dtsi
index 5308f1671824..66c77146585b 100644
--- a/arch/arm64/boot/dts/qcom/sdm845.dtsi
+++ b/arch/arm64/boot/dts/qcom/sdm845.dtsi
@@ -1033,6 +1033,7 @@
phy-names = "ufsphy";
lanes-per-direction = <2>;
power-domains = <&gcc UFS_PHY_GDSC>;
+ #reset-cells = <1>;
iommus = <&apps_smmu 0x100 0xf>;
@@ -1078,6 +1079,8 @@
clocks = <&gcc GCC_UFS_MEM_CLKREF_CLK>,
<&gcc GCC_UFS_PHY_PHY_AUX_CLK>;
+ resets = <&ufs_mem_hc 0>;
+ reset-names = "ufsphy";
status = "disabled";
ufs_mem_phy_lanes: lanes@1d87400 {
--
2.20.1
next prev parent reply other threads:[~2019-03-21 17:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 17:17 [PATCH v5 0/8] phy: qcom-ufs: Enable regulators to be off in suspend Evan Green
2019-03-21 17:17 ` Evan Green
2019-03-21 17:17 ` [PATCH v5 1/8] dt-bindings: ufs: Add #reset-cells for Qualcomm controllers Evan Green
2019-03-21 17:17 ` [PATCH v5 2/8] dt-bindings: phy-qcom-qmp: Add UFS PHY reset Evan Green
2019-03-21 17:17 ` [PATCH v5 3/8] dt-bindings: phy: qcom-ufs: Add resets property Evan Green
2019-03-21 17:17 ` Evan Green [this message]
2019-03-21 17:17 ` [PATCH v5 5/8] arm64: dts: msm8996: Add UFS PHY reset controller Evan Green
2019-03-21 17:17 ` [PATCH v5 6/8] scsi: ufs: qcom: Expose the reset controller for PHY Evan Green
2019-03-21 17:17 ` [PATCH v5 7/8] phy: qcom: Utilize UFS reset controller Evan Green
2019-03-21 17:18 ` [PATCH v5 8/8] phy: ufs-qcom: Refactor all init steps into phy_poweron Evan Green
2019-03-26 7:48 ` [PATCH v5 0/8] phy: qcom-ufs: Enable regulators to be off in suspend Kishon Vijay Abraham I
2019-03-26 7:48 ` Kishon Vijay Abraham I
2019-03-26 16:17 ` Evan Green
2019-03-26 16:17 ` Evan Green
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=20190321171800.104681-5-evgreen@chromium.org \
--to=evgreen@chromium.org \
--cc=andy.gross@linaro.org \
--cc=asutoshd@codeaurora.org \
--cc=cang@codeaurora.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=kishon@ti.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.w.gonzalez@free.fr \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=swboyd@chromium.org \
--cc=vivek.gautam@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.