From: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Cc: kever.yang-TNX95d0MmH7DzftRWevZcw@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
Subject: [PATCH 3/3] arm64: dts: rockchip: enable usb3 controllers on rk3399-firefly
Date: Tue, 23 May 2017 11:54:27 +0200 [thread overview]
Message-ID: <20170523095427.7421-3-heiko@sntech.de> (raw)
In-Reply-To: <20170523095427.7421-1-heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
This allows basic usage of usb3 devices but no typec specific things yet.
Signed-off-by: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
---
arch/arm64/boot/dts/rockchip/rk3399-firefly.dts | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-firefly.dts b/arch/arm64/boot/dts/rockchip/rk3399-firefly.dts
index ef47360ad286..ba1d9810ad1e 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399-firefly.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3399-firefly.dts
@@ -698,3 +698,21 @@
&usb_host1_ohci {
status = "okay";
};
+
+&usbdrd3_0 {
+ status = "okay";
+};
+
+&usbdrd_dwc3_0 {
+ status = "okay";
+ dr_mode = "otg";
+};
+
+&usbdrd3_1 {
+ status = "okay";
+};
+
+&usbdrd_dwc3_1 {
+ status = "okay";
+ dr_mode = "host";
+};
--
2.11.0
next prev parent reply other threads:[~2017-05-23 9:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 9:54 [PATCH 1/3] arm64: dts: rockchip: bring rk3399-firefly power-tree in line Heiko Stuebner
[not found] ` <20170523095427.7421-1-heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
2017-05-23 9:54 ` [PATCH 2/3] arm64: dts: rockchip: add ethernet alias on rk3399 Heiko Stuebner
2017-05-23 10:15 ` Baruch Siach
2017-05-23 11:12 ` Heiko Stuebner
2017-05-23 9:54 ` Heiko Stuebner [this message]
2017-05-30 10:07 ` [PATCH 1/3] arm64: dts: rockchip: bring rk3399-firefly power-tree in line Heiko Stuebner
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=20170523095427.7421-3-heiko@sntech.de \
--to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
--cc=kever.yang-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.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