From: 4omecha-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
To: Katsuhiro Suzuki <katsuhiro-WKCMddiH/C4xsqv6Oivclw@public.gmane.org>
Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Peter Geis <pgwipeout-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: rk3328 USB3 controller
Date: Thu, 17 Oct 2019 18:21:31 +0200 [thread overview]
Message-ID: <20191017162131.GH14623@think-future.de> (raw)
In-Reply-To: <1b0f65be-51b6-69dd-e204-6d168f17eb7d-ehbYDe70fqD9uQeqpI+JUg@public.gmane.org>
On 2019-10-17 14:07:43, Katsuhiro Suzuki wrote:
>Hello Peter,
>
>USB3 phy driver "rockchip,rk3328-u3phy" has not been implemented on
>upstream linux kernel.
>
>FireflyTeam use the special version of linux that is modified by Rockchip.
>(It seems based on linux-4.4)
>
>rockchip,rk3328-u3phy is provided by
> https://github.com/FireflyTeam/kernel/drivers/phy/rockchip/phy-rockchip-inno-usb3.c
That's a 404 over here.
>
>If you want to use USB 3.0 with upstream linux, we need to port this
>USB3 phy driver from rockchip-linux to upstream kernel, I think.
>
>Best Regards,
>Katsuhiro Suzuki
>
>
>On 2019/10/17 3:54, Peter Geis wrote:
>>Good Afternoon,
>>
>>Is there a particular reason why the USB3 controller on the rk3328 has
>>not been enabled?
>>It's enabled on the TeamFirefly source [0].
>>I pulled it in to my device tree and have been using a USB3 SSD as my
>>boot device for over a year now.
>>
>>If I were to submit the patch, would y'all be open to pulling it in?
>>
>>[0] https://github.com/FireflyTeam/kernel/blob/roc-rk3328-cc/arch/arm64/boot/dts/rockchip/rk3328.dtsi
>>
>>_______________________________________________
>>Linux-rockchip mailing list
>>Linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
>>http://lists.infradead.org/mailman/listinfo/linux-rockchip
>>
>
>
>_______________________________________________
>Linux-rockchip mailing list
>Linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
>http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2019-10-17 16:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 18:54 rk3328 USB3 controller Peter Geis
[not found] ` <1b0f65be-51b6-69dd-e204-6d168f17eb7d@think-future.de>
[not found] ` <1b0f65be-51b6-69dd-e204-6d168f17eb7d-ehbYDe70fqD9uQeqpI+JUg@public.gmane.org>
2019-10-17 16:21 ` 4omecha-Re5JQEeQqe8AvxtiuMwx3w [this message]
[not found] ` <20191017162131.GH14623-ehbYDe70fqD9uQeqpI+JUg@public.gmane.org>
2019-10-18 1:54 ` Katsuhiro Suzuki
[not found] ` <CAMdYzYp9xdtb6eiUs-Tiq4jJ-jr31LTzng2o-qAbOfu_63zXVg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-10-17 5:07 ` Katsuhiro Suzuki
2019-10-17 16:35 ` Robin Murphy
[not found] ` <65610976-8cb9-c0cd-d4a7-b8951b836fd7-5wv7dgnIgG8@public.gmane.org>
2019-10-17 17:11 ` 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=20191017162131.GH14623@think-future.de \
--to=4omecha-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=katsuhiro-WKCMddiH/C4xsqv6Oivclw@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=pgwipeout-Re5JQEeQqe8AvxtiuMwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.