From: Evan Green <evgreen@chromium.org>
To: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Andy Gross <andy.gross@linaro.org>,
David Brown <david.brown@linaro.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
Douglas Anderson <dianders@chromium.org>,
Manu Gautam <mgautam@codeaurora.org>,
Can Guo <cang@codeaurora.org>,
Vivek Gautam <vivek.gautam@codeaurora.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
swboyd@chromium.org
Cc: Evan Green <evgreen@chromium.org>
Subject: [PATCH v2 5/5] arm64: dts: qcom: sdm845: Add USB PHY lane two
Date: Thu, 18 Oct 2018 14:09:33 -0700 [thread overview]
Message-ID: <20181018210933.113592-6-evgreen@chromium.org> (raw)
In-Reply-To: <20181018210933.113592-1-evgreen@chromium.org>
This change adds the second lane registers for the USB PHY, now that the
QMP phy bindings have been updated. This way the driver can stop
reaching beyond its register region to get at the second lane.
Signed-off-by: Evan Green <evgreen@chromium.org>
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi b/arch/arm64/boot/dts/qcom/sdm845.dtsi
index 9c72edb678ec..f28c50e93f5a 100644
--- a/arch/arm64/boot/dts/qcom/sdm845.dtsi
+++ b/arch/arm64/boot/dts/qcom/sdm845.dtsi
@@ -1188,10 +1188,12 @@
<&gcc GCC_USB3_PHY_PRIM_BCR>;
reset-names = "phy", "common";
- usb_1_ssphy: lane@88e9200 {
+ usb_1_ssphy: lanes@88e9200 {
reg = <0x88e9200 0x128>,
<0x88e9400 0x200>,
<0x88e9c00 0x218>,
+ <0x88e9600 0x128>,
+ <0x88e9800 0x200>,
<0x88e9a00 0x100>;
#phy-cells = <0>;
clocks = <&gcc GCC_USB3_PRIM_PHY_PIPE_CLK>;
@@ -1219,10 +1221,12 @@
<&gcc GCC_USB3_PHY_SEC_BCR>;
reset-names = "phy", "common";
- usb_2_ssphy: lane@88eb200 {
+ usb_2_ssphy: lanes@88eb200 {
reg = <0x88eb200 0x128>,
<0x88eb400 0x1fc>,
<0x88eb800 0x218>,
+ <0x88eb600 0x128>,
+ <0x88eb800 0x1fc>,
<0x88e9600 0x70>;
#phy-cells = <0>;
clocks = <&gcc GCC_USB3_SEC_PHY_PIPE_CLK>;
--
2.16.4
next prev parent reply other threads:[~2018-10-18 21:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 21:09 [PATCH v2 0/5] arm64: dts: qcom: sdm845: Add UFS DT nodes Evan Green
2018-10-18 21:09 ` [PATCH v2 1/5] dt-bindings: phy-qcom-qmp: Fix register underspecification Evan Green
2018-10-18 23:50 ` Doug Anderson
2018-10-23 0:29 ` Rob Herring
2018-10-23 16:30 ` Evan Green
2018-10-18 21:09 ` [PATCH v2 2/5] phy: qcom-qmp: Utilize fully-specified DT registers Evan Green
2018-10-18 23:51 ` Doug Anderson
2018-10-18 21:09 ` [PATCH v2 3/5] arm64: dts: qcom: sdm845: add UFS controller Evan Green
2018-10-18 23:52 ` Doug Anderson
2018-10-18 21:09 ` [PATCH v2 4/5] arm64: dts: qcom: sdm845: Add UFS nodes for sdm845-mtp Evan Green
2018-10-18 23:52 ` Doug Anderson
2018-10-18 21:09 ` Evan Green [this message]
2018-10-18 23:53 ` [PATCH v2 5/5] arm64: dts: qcom: sdm845: Add USB PHY lane two Doug Anderson
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=20181018210933.113592-6-evgreen@chromium.org \
--to=evgreen@chromium.org \
--cc=andy.gross@linaro.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=linux-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mgautam@codeaurora.org \
--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.