From: lindsey.stanpoor@gmail.com
To: linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Cc: gregkh@linuxfoundation.org, robh+dt@kernel.org, heiko@sntech.de,
balbi@kernel.org, cnemo@tutanota.com
Subject: [PATCH v4 4/4] arm64: dts: rockchip: enable rk3328-rock64 usb3 nodes
Date: Wed, 2 Sep 2020 11:12:34 -0700 [thread overview]
Message-ID: <20200902181234.13955-4-lindsey.stanpoor@gmail.com> (raw)
In-Reply-To: <20200902181234.13955-1-lindsey.stanpoor@gmail.com>
From: Cameron Nemo <cnemo@tutanota.com>
Enable USB3 nodes for the rk3328-based PINE Rock64 board.
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Signed-off-by: Cameron Nemo <cnemo@tutanota.com>
---
arch/arm64/boot/dts/rockchip/rk3328-rock64.dts | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts b/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts
index 86cfb5c50a94..0cbf59efcef0 100644
--- a/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3328-rock64.dts
@@ -384,6 +384,15 @@ &usb20_otg {
status = "okay";
};
+&usbdrd3 {
+ status = "okay";
+};
+
+&usbdrd_dwc3 {
+ dr_mode = "host";
+ status = "okay";
+};
+
&usb_host0_ehci {
status = "okay";
};
--
2.28.0
next prev parent reply other threads:[~2020-09-02 18:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 18:12 [PATCH v4 1/4] dt-bindings: usb: add rk3328 dwc3 docs lindsey.stanpoor
2020-09-02 18:12 ` [PATCH v4 2/4] usb: dwc3: of-simple: Add compatible for rk3328 lindsey.stanpoor
2020-09-02 18:12 ` [PATCH v4 3/4] arm64: dts: rockchip: rk3328 usb3 controller node lindsey.stanpoor
2020-09-02 18:12 ` lindsey.stanpoor [this message]
2020-09-14 20:26 ` [PATCH v4 1/4] dt-bindings: usb: add rk3328 dwc3 docs Rob Herring
2020-11-07 2:37 ` Lindsey Stanpoor
2020-11-07 7:42 ` Felipe Balbi
2021-01-21 4:28 ` Lindsey Stanpoor
2021-01-21 4:40 ` Chen-Yu Tsai
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=20200902181234.13955-4-lindsey.stanpoor@gmail.com \
--to=lindsey.stanpoor@gmail.com \
--cc=balbi@kernel.org \
--cc=cnemo@tutanota.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-usb@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).