From: Dennis Gilmore <dgilmore@redhat.com>
To: linux-rockchip@lists.infradead.org
Cc: dgilmore@redhat.com, "Rob Herring" <robh+dt@kernel.org>,
"Heiko Stuebner" <heiko@sntech.de>,
"Uwe Kleine-König" <uwe@kleine-koenig.org>,
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
FLATTENED DEVICE TREE BINDINGS),
linux-arm-kernel@lists.infradead.org (moderated
list:ARM/Rockchip SoC support),
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH 1/4] arm64: dts: rockchip: helios64: fixup USB setup
Date: Wed, 30 Jun 2021 19:40:36 -0500 [thread overview]
Message-ID: <20210701004043.18585-1-dgilmore@redhat.com> (raw)
Without the usbdrd_dwc3_1 node defined u-boot will throw an error and
reset the system. All other rk3399 systems use this format
Signed-off-by: Dennis Gilmore <dgilmore@redhat.com>
---
arch/arm64/boot/dts/rockchip/rk3399-kobol-helios64.dts | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-kobol-helios64.dts b/arch/arm64/boot/dts/rockchip/rk3399-kobol-helios64.dts
index 738cfd21df3e..aeedf098f67c 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399-kobol-helios64.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3399-kobol-helios64.dts
@@ -490,9 +490,9 @@ &uart2 {
&usbdrd3_1 {
status = "okay";
+};
- usb@fe900000 {
- dr_mode = "host";
- status = "okay";
- };
+&usbdrd_dwc3_1 {
+ dr_mode = "host";
+ status = "okay";
};
--
2.31.1
next reply other threads:[~2021-07-01 0:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 0:40 Dennis Gilmore [this message]
2021-07-01 0:40 ` [PATCH 2/4] arm64: dts: rockchip: helios64: set stdout-path Dennis Gilmore
2021-07-01 0:40 ` [PATCH 3/4] arm64: dts: rockchip: helios64: add SPI support Dennis Gilmore
2021-07-01 0:40 ` [PATCH 4/4] arm64: dts: rockchip: helios64: enable tsadc on helios64 Dennis Gilmore
2021-07-01 9:31 ` [PATCH 1/4] arm64: dts: rockchip: helios64: fixup USB setup Uwe Kleine-König
2021-07-01 12:59 ` Dennis Gilmore
2021-07-01 13:35 ` Uwe Kleine-König
2021-07-01 18:13 ` Dennis Gilmore
2021-07-01 9:32 ` Robin Murphy
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=20210701004043.18585-1-dgilmore@redhat.com \
--to=dgilmore@redhat.com \
--cc=devicetree@vger.kernel.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=robh+dt@kernel.org \
--cc=uwe@kleine-koenig.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).