From: Frank Wang <frank.wang@rock-chips.com>
To: Heiko Stuebner <heiko@sntech.de>, Caesar Wang <wxt@rock-chips.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, dianders@chromium.org,
william.wu@rock-chips.com, huangtao@rock-chips.com,
eddie.cai@rock-chips.com, william.wu@rock-chips.com,
frank.wang@rock-chips.com
Subject: Re: [PATCH] arm64: dts: rockchip: support the usb2phy for rk3399 evb
Date: Mon, 11 Jul 2016 15:43:03 +0800 [thread overview]
Message-ID: <cd9056c1-6fff-d02c-3fc0-3d48d9850504@rock-chips.com> (raw)
In-Reply-To: <2150255.RfISFviJKP@phil>
Hi Heiko,
On 2016/7/7 18:11, Heiko Stuebner wrote:
> Hi,
>
> Am Donnerstag, 7. Juli 2016, 12:46:40 schrieb Caesar Wang:
>> From: Frank Wang <frank.wang@rock-chips.com>
>>
>> This patch adds the usb2phy needed dts node information for rk3399.
>>
>> USB2.0 PHY is comprised of one Host port and one OTG port.
>> Host Port is for USB2.0 host controller; OTG port is for USB2.0 part of
>> USB3.0 OTG controller, and as a part to construct a fully feature TypeC
>> subsystem.
>>
>> The USB2.0 vbus gpio is board specific, it's no same with all rk3399
>> boards, so move it into evb voard.
>>
>> Signed-off-by: Frank Wang <frank.wang@rock-chips.com>
>> Signed-off-by: Caesar Wang <wxt@rock-chips.com>
>> ---
>>
>> arch/arm64/boot/dts/rockchip/rk3399-evb.dts | 4 ++++
>> arch/arm64/boot/dts/rockchip/rk3399.dtsi | 19 +++++++++++++++++++
>> 2 files changed, 23 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi
>> b/arch/arm64/boot/dts/rockchip/rk3399.dtsi index 4c84229..21d147f 100644
>> --- a/arch/arm64/boot/dts/rockchip/rk3399.dtsi
>> +++ b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
>> @@ -242,6 +242,25 @@
>> status = "disabled";
>> };
>>
>> + usb2phy: usb2phy {
>> + compatible = "rockchip,rk3399-usb-phy";
>> + rockchip,grf = <&grf>;
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + usb2phy0: usb2-phy0 {
>> + #phy-cells = <0>;
>> + #clock-cells = <0>;
>> + reg = <0xe458>;
>> + };
>> +
>> + usb2phy1: usb2-phy1 {
>> + #phy-cells = <0>;
>> + #clock-cells = <0>;
>> + reg = <0xe468>;
>> + };
>> + };
>> +
> The rk3399 uses the innosilicon usb2 phy and the binding we've come up for
> it looks a lot different than the above. So I'm not sure where this is
> coming from, especially as I haven't seen the driver part for the rk3399 at
> all yet. So far Frank was always working on te rk3366 variant, which seemed
> to be the most complete.
Yeah, rk3399 is ready for using the new driver and the binding which I
have handed out earlier, but it seems that they have not applied yet, so
shall we send out the new patches for rk3399 until they will be applied?
BR.
Frank
> Heiko
>
prev parent reply other threads:[~2016-07-11 7:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 4:46 Caesar Wang
2016-07-07 10:11 ` Heiko Stuebner
2016-07-11 7:43 ` Frank Wang [this message]
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=cd9056c1-6fff-d02c-3fc0-3d48d9850504@rock-chips.com \
--to=frank.wang@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=eddie.cai@rock-chips.com \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=william.wu@rock-chips.com \
--cc=wxt@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
all inboxes | Powered by JetHome®