linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Peter Geis <pgwipeout@gmail.com>
To: Alex Bee <knaerzche@gmail.com>
Cc: "Felipe Balbi" <balbi@kernel.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Heiko Stuebner" <heiko@sntech.de>,
	王明成 <frank.wang@rock-chips.com>, zyw <zyw@rock-chips.com>,
	linux-usb@vger.kernel.org,
	"Kever Yang" <kever.yang@rock-chips.com>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>,
	吴良峰 <william.wu@rock-chips.com>, wulf <wulf@rock-chips.com>,
	arm-mail-list <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/4] phy: rockchip: add rockchip usb3 innosilicon phy driver
Date: Mon, 19 Jul 2021 19:19:07 -0400	[thread overview]
Message-ID: <CAMdYzYqUgd_uPOPCnGUvU7kxPDGNnoN+_1RmO_AyY6oUtpkfGw@mail.gmail.com> (raw)
In-Reply-To: <6e7a5a02-cd3c-81d3-a473-f87385c41e5a@gmail.com>

On Mon, Jul 19, 2021 at 10:29 AM Alex Bee <knaerzche@gmail.com> wrote:
>
> Hi Peter,
>
> thanks for working on this (I hope to have picked the latest version of
> your series).
>
> It's pretty obvious that the quirky innosilicon phy Rockchip decided for
> in RK3328 needs a additional glue layer. Even if this version isn't
> perfect yet (usb3 devices "sometimes" do net get detected if detached
> and attached again) - it makes thing *a lot* better than it is now (IIRC
> its about the same in vendor tree)

Yes, it certainly is broken.

>
> So: are you going to rebase this on current upstream?

Honestly I hadn't planned on it, mostly because my board started
exhibiting stability issues.
This series had been tagged as an RFC as I was hoping to resolve the
issues with it.
Unfortunately either the documentation provided was insufficient to
fix the problem, or the hardware doesn't behave as the documentation
suggests.
Also the way we have to tie into the usb core makes me really uncomfortable.

Perhaps once the rk3566 is in good shape I can poke at this again.
There's a number of other issues with older boards that have come to
light that need attention.

>
> Regards,
>
> Alex
>
> Am 16.11.20 um 16:17 schrieb Peter Geis:
> > The innosilicon based usb3 phy used in rockchip devices such as the rk3328 is bugged, requiring special handling.
> > The following erata have been observed:
> >   - usb3 device disconnect events are not detected by the controller
> >   - usb2 hubs with no devices attached do not trigger disconnect events when removed
> >   - interrupts are not reliable
> >
> > To work around these issue we implement polling of the usb2 and usb3 status.
> > On usb3 disconnection we reset the usb3 phy which triggers the disconnect event.
> > On usb2 disconnection we have to force reset the whole controller.
> > This requires a handoff to a special dwc3 device driver.
> >
> > This has been tested on the rk3328-roc-cc board with the following devices:
> >   - usb2 only device
> >   - usb3 only device
> >   - usb2 only hub without devices
> >   - usb3 hub without devices
> >   - usb2 hub with devices
> >   - usb3 hub with devices
> >
> > Signed-off-by: Peter Geis <pgwipeout@gmail.com>

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-07-19 23:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-16 15:17 [PATCH 0/4] [RFC] rk3328 usb3 phy driver Peter Geis
2020-11-16 15:17 ` [PATCH 1/4] phy: rockchip: add rockchip usb3 innosilicon " Peter Geis
2021-07-19 14:29   ` Alex Bee
2021-07-19 23:19     ` Peter Geis [this message]
2020-11-16 15:17 ` [PATCH 2/4] usb: dwc3: add rockchip innosilicon usb3 glue layer Peter Geis
2020-11-16 15:17 ` [PATCH 3/4] arm64: dts: rockchip: add rk3328 usb3 and usb3phy nodes Peter Geis
2020-11-16 16:07   ` Johan Jonker
2020-11-16 16:25     ` Peter Geis
2020-11-16 15:17 ` [PATCH 4/4] arm64: dts: rockchip: enable usb3 on rk3328-roc-cc board Peter Geis

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=CAMdYzYqUgd_uPOPCnGUvU7kxPDGNnoN+_1RmO_AyY6oUtpkfGw@mail.gmail.com \
    --to=pgwipeout@gmail.com \
    --cc=balbi@kernel.org \
    --cc=frank.wang@rock-chips.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heiko@sntech.de \
    --cc=kever.yang@rock-chips.com \
    --cc=knaerzche@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=william.wu@rock-chips.com \
    --cc=wulf@rock-chips.com \
    --cc=zyw@rock-chips.com \
    /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).