From: Chen-Yu Tsai <wens@kernel.org>
To: Rob Herring <robh+dt@kernel.org>, Heiko Stuebner <heiko@sntech.de>
Cc: Chen-Yu Tsai <wens@csie.org>,
devicetree@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] arm64: dts: rockchip: rk3328: Enable USB3 on some SBCs
Date: Tue, 4 May 2021 16:36:12 +0800 [thread overview]
Message-ID: <20210504083616.9654-1-wens@kernel.org> (raw)
From: Chen-Yu Tsai <wens@csie.org>
Hi everyone,
Here are some patches that enable USB3 on RK3328 SBCs that I own. The
changes are quite straightforward, except for the NanoPi R2S, which
has a USB3 Ethernet chip attached. I am aware that there's already a
patch [1] for that. This is my spin on things using the USB device
binding, with comments on how the USB ports are arranged, that I had
done but couldn't find the time to send out.
The last patch also results in some warnings from checkpatch.pl:
WARNING: DT compatible string "usbbda,8153" appears un-documented --
check ./Documentation/devicetree/bindings/
#88: FILE: arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s.dts:398:
+ compatible = "usbbda,8153";
WARNING: DT compatible string vendor "usbbda" appears un-documented --
check ./Documentation/devicetree/bindings/vendor-prefixes.yaml
#88: FILE: arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s.dts:398:
+ compatible = "usbbda,8153";
At least the first warning should be covered by the USB device binding
Documentation/devicetree/bindings/usb/usb-device.yaml
while we probably should add an exception to vendor-prefixes.yaml for
the second warning.
Please let me know what you think.
Regards
ChenYu
[1] https://lore.kernel.org/linux-rockchip/20210405093423.16149-1-cnsztl@gmail.com/
Cameron Nemo (1):
arm64: dts: rockchip: rk3328: Enable USB3 for Rock64
Chen-Yu Tsai (3):
arm64: dts: rockchip: rk3328: Enable USB3 for ROC-RK3328-CC
arm64: dts: rockchip: rk3328: Enable USB3 for Rock Pi E
arm64: dts: rockchip: rk3328: Enable USB3 Ethernet on NanoPi R2S
.../boot/dts/rockchip/rk3328-nanopi-r2s.dts | 32 +++++++++++++++++++
.../arm64/boot/dts/rockchip/rk3328-roc-cc.dts | 5 +++
.../boot/dts/rockchip/rk3328-rock-pi-e.dts | 5 +++
.../arm64/boot/dts/rockchip/rk3328-rock64.dts | 5 +++
4 files changed, 47 insertions(+)
--
2.31.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-05-04 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 8:36 Chen-Yu Tsai [this message]
2021-05-04 8:36 ` [PATCH 1/4] arm64: dts: rockchip: rk3328: Enable USB3 for Rock64 Chen-Yu Tsai
2021-05-04 8:36 ` [PATCH 2/4] arm64: dts: rockchip: rk3328: Enable USB3 for ROC-RK3328-CC Chen-Yu Tsai
2021-05-04 8:36 ` [PATCH 3/4] arm64: dts: rockchip: rk3328: Enable USB3 for Rock Pi E Chen-Yu Tsai
2021-05-04 8:36 ` [PATCH 4/4] arm64: dts: rockchip: rk3328: Enable USB3 Ethernet on NanoPi R2S Chen-Yu Tsai
2021-05-09 23:55 ` [PATCH 0/4] arm64: dts: rockchip: rk3328: Enable USB3 on some SBCs 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=20210504083616.9654-1-wens@kernel.org \
--to=wens@kernel.org \
--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=wens@csie.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).