From: Andre Przywara <andre.przywara@arm.com>
To: Bin Meng <bmeng.cn@gmail.com>
Cc: Marek Vasut <marex@denx.de>, Samuel Holland <samuel@sholland.org>,
Jagan Teki <jagan@amarulasolutions.com>,
Andre Heider <a.heider@gmail.com>,
Icenowy Zheng <icenowy@aosc.io>, Simon Glass <sjg@chromium.org>,
Kever Yang <kever.yang@rock-chips.com>,
Chen-Yu Tsai <wens@csie.org>, Maxime Ripard <mripard@kernel.org>,
u-boot@lists.denx.de
Subject: Re: [PATCH v2 0/4] Allwinner H6 USB3 support
Date: Mon, 5 Jul 2021 00:09:31 +0100 [thread overview]
Message-ID: <20210705000931.2ae3e868@slackpad.fritz.box> (raw)
In-Reply-To: <3872543e-6e95-4dff-7543-bc0282ed18eb@denx.de>
On Wed, 21 Apr 2021 12:53:42 +0200
Marek Vasut <marex@denx.de> wrote:
Hi,
> On 4/21/21 12:43 PM, Andre Przywara wrote:
> > On Sat, 17 Apr 2021 09:20:55 -0500
> > Samuel Holland <samuel@sholland.org> wrote:
> >
> > Hi,
> >
> >> This series adds PHY and XHCI driver support for the USB3 controller
> >> found in the Allwinner H6 SoC.
> >
> > Thanks for the update!
> >
> >> It has been tested and working on both
> >> boards enabled in patch 4, although some users experience issues[1].
> >>
> >> [1]: https://lists.denx.de/pipermail/u-boot/2021-February/440767.html
> >
> > So I could not reproduce those issues either, it works for me fine on my
> > Pine-H64. I'd suggest we merge those patches, and check for more
> > reports from more users.
> >
> > Bin, Marek: can you push patches 1, 2 and 3 to the USB tree, to get
> > them into the current merge window, still? I would then push 4/4
> > (pending possible fixes) once the first three reached mainline.
> >
> > And btw: the first two patches of the original v1 series (adding the
> > sunxi clocks and reset bits) have been merged into master last week
> > already.
>
> I will pick these once I get ack from Bin.
Bin, did you have a chance to have a look at those patches? I wonder if
we could merge them in the MW, to expose them to a wider audience?
Cheers,
Andre
next prev parent reply other threads:[~2021-07-04 23:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-17 14:20 [PATCH v2 0/4] Allwinner H6 USB3 support Samuel Holland
2021-04-17 14:20 ` [PATCH v2 1/4] phy: sun50i-usb3: Add a driver for the H6 USB3 PHY Samuel Holland
2021-04-17 14:20 ` [PATCH v2 2/4] usb: xhci-pci: Move reset logic out of XHCI core Samuel Holland
2021-04-21 10:36 ` Andre Przywara
2021-04-21 13:36 ` Samuel Holland
2021-04-21 14:58 ` Andre Przywara
2021-07-05 8:04 ` Bin Meng
2021-07-05 8:19 ` Marek Vasut
2021-07-05 8:38 ` Bin Meng
2021-07-05 9:06 ` Andre Przywara
2021-07-05 9:18 ` Bin Meng
2021-07-05 10:45 ` Marek Vasut
2021-07-05 12:12 ` Andre Przywara
2021-07-05 9:20 ` Marek Vasut
2021-04-17 14:20 ` [PATCH v2 3/4] usb: xhci-dwc3: Add support for clocks/resets Samuel Holland
2021-04-21 10:37 ` Andre Przywara
2021-04-17 14:20 ` [PATCH v2 4/4] configs: Enable USB3 on Allwinner H6 boards Samuel Holland
2021-04-21 10:37 ` Andre Przywara
2021-04-21 10:43 ` [PATCH v2 0/4] Allwinner H6 USB3 support Andre Przywara
2021-04-21 10:53 ` Marek Vasut
2021-07-04 23:09 ` Andre Przywara [this message]
2021-07-05 1:18 ` Bin Meng
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=20210705000931.2ae3e868@slackpad.fritz.box \
--to=andre.przywara@arm.com \
--cc=a.heider@gmail.com \
--cc=bmeng.cn@gmail.com \
--cc=icenowy@aosc.io \
--cc=jagan@amarulasolutions.com \
--cc=kever.yang@rock-chips.com \
--cc=marex@denx.de \
--cc=mripard@kernel.org \
--cc=samuel@sholland.org \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--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