From: Heiko Stuebner <heiko@sntech.de>
To: Michael Riesch <michael.riesch@wolfvision.net>,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Cc: Heiko Stuebner <heiko@sntech.de>,
Frank Wunderlich <frank-w@public-files.de>,
Peter Geis <pgwipeout@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Liang Chen <cl@rock-chips.com>,
Nicolas Frattaroli <frattaroli.nicolas@gmail.com>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: (subset) [PATCH 1/3] arm64: dts: rockchip: enable otg/drd operation of usb_host0_xhci in rk356x
Date: Sat, 30 Apr 2022 16:05:53 +0200 [thread overview]
Message-ID: <165132754299.647302.7977397851546544762.b4-ty@sntech.de> (raw)
In-Reply-To: <20220425133502.405512-1-michael.riesch@wolfvision.net>
On Mon, 25 Apr 2022 15:35:00 +0200, Michael Riesch wrote:
> This USB 3.0 controller is capable of OTG/DRD operation. Enable it in the
> device tree.
Applied, thanks!
[2/3] arm64: dts: rockchip: add usb3 support to the radxa rock3 model a
commit: 254a1f6a29e7a273adb1a1d032305ec58ef83a69
[3/3] arm64: dts: rockchip: enable usb hub on the radxa rock3 model a
commit: 160f126b89e10bd58491e10067a44c7e3f85fa2c
Best regards,
--
Heiko Stuebner <heiko@sntech.de>
next prev parent reply other threads:[~2022-04-30 14:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 13:35 [PATCH 1/3] arm64: dts: rockchip: enable otg/drd operation of usb_host0_xhci in rk356x Michael Riesch
2022-04-25 13:35 ` [PATCH 2/3] arm64: dts: rockchip: add usb3 support to the radxa rock3 model a Michael Riesch
2022-04-25 13:35 ` [PATCH 3/3] arm64: dts: rockchip: enable usb hub on " Michael Riesch
2022-04-28 11:15 ` [PATCH 1/3] arm64: dts: rockchip: enable otg/drd operation of usb_host0_xhci in rk356x Nicolas Frattaroli
2022-04-28 13:24 ` Michael Riesch
2022-04-30 14:07 ` Heiko Stuebner
2022-05-02 11:22 ` Michael Riesch
2022-04-30 14:05 ` Heiko Stuebner [this message]
2022-05-11 4:14 ` (subset) " 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=165132754299.647302.7977397851546544762.b4-ty@sntech.de \
--to=heiko@sntech.de \
--cc=cl@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=frank-w@public-files.de \
--cc=frattaroli.nicolas@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=michael.riesch@wolfvision.net \
--cc=pgwipeout@gmail.com \
--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).