From: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
To: Jack Mitchell <ml-psbXN780rFT10XsdtD+oqA@public.gmane.org>,
linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: rk3399: nanopc-t4 usb otg
Date: Thu, 28 Mar 2019 12:21:38 +0000 [thread overview]
Message-ID: <2458cca9-4209-7658-b4ba-e2067a3fbce5@arm.com> (raw)
In-Reply-To: <a94d70c2-8495-bf91-41c5-bff013ade381-psbXN780rFT10XsdtD+oqA@public.gmane.org>
Hi Jack,
On 28/03/2019 11:34, Jack Mitchell wrote:
> Hi,
>
> Can anyone confirm working operation of USB OTG over a type c phy on an
> RK3399 at commit 8c2ffd9174779014c3fe1f96d9dc3641d9175f00 (tag: v5.1-rc2).
>
> I've got a nanopc-t4 here and when I try to load the g_ether driver I
> receive
>
> [ 6.359280] udc-core: couldn't find an available UDC - added
> [g_ether] to list of pending drivers
>
> I've had a look through the dts and all seems to be in order. USB
> devices work fine in the host ports and I've confirmed otg mode.
>
> root@rk3399:/sys/kernel/debug/fe800000.dwc3# cat mode
> otg
>
> The cable is being detected at plug/unplug as can be seen from
>
> [ 1252.479273] phy phy-ff770000.syscon:usb2-phy@e450.2: charger =
> USB_SDP_CHARGER
>
> My defconfig is the standard arm64 as provided with the addition of
> CONFIG_USB_ETH=m.
>
> Any information would be helpful, especially if this is working on other
> 3399 based boards at the mentioned commit.
I've not tried the type C port since I was playing with the initial dts,
but IIRC not even host mode was working at that point. My vague
understanding is that there was (and probably still is) some
communication missing between the fusb302 driver and the dwc3 driver
(since NanoPC-T4 is using that external chip rather than the RK3399's
internal type C controller).
It's certainly something I've been meaning to come back and take another
look at, so I'll try to have a play over the weekend to see how much I
can make sense of.
Robin.
next prev parent reply other threads:[~2019-03-28 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 11:34 rk3399: nanopc-t4 usb otg Jack Mitchell
[not found] ` <a94d70c2-8495-bf91-41c5-bff013ade381-psbXN780rFT10XsdtD+oqA@public.gmane.org>
2019-03-28 12:21 ` Robin Murphy [this message]
[not found] ` <2458cca9-4209-7658-b4ba-e2067a3fbce5-5wv7dgnIgG8@public.gmane.org>
2019-03-28 13:32 ` Jack Mitchell
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=2458cca9-4209-7658-b4ba-e2067a3fbce5@arm.com \
--to=robin.murphy-5wv7dgnigg8@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=ml-psbXN780rFT10XsdtD+oqA@public.gmane.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