From: "William.wu" <William.wu@rock-chips.com>
To: "Heiko Stübner" <heiko@sntech.de>,
"Rob Herring" <robh@kernel.org>,
"Felipe Balbi" <balbi@kernel.org>
Cc: gregkh@linuxfoundation.org, linux-rockchip@lists.infradead.org,
briannorris@google.com, dianders@google.com,
kever.yang@rock-chips.com, huangtao@rock-chips.com,
frank.wang@rock-chips.com, eddie.cai@rock-chips.com,
John.Youn@synopsys.com, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, sergei.shtylyov@cogentembedded.com,
mark.rutland@arm.com, devicetree@vger.kernel.org
Subject: Re: [PATCH v7 3/5] usb: dwc3: make usb2 phy utmi interface configurable in DT
Date: Mon, 25 Jul 2016 00:24:26 +0800 [thread overview]
Message-ID: <f3e38a34-3d7b-8187-0262-d41b23a3c4a9@rock-chips.com> (raw)
In-Reply-To: <1738306.cydkc9Pb90@diego>
Dear Heiko,
On 2016/7/17 18:28, Heiko Stübner wrote:
> Am Samstag, 16. Juli 2016, 17:57:15 schrieb Rob Herring:
>> On Thu, Jul 14, 2016 at 04:59:20PM +0800, William Wu wrote:
>>> Add snps,phyif-utmi-width devicetree property to configure
>>> the UTMI+ PHY with an 8- or 16-bit interface. UTMI+ PHY
>>> interface is a hardware property, and it's platform dependent.
>>> Normally,the PHYIF can be configured during coreconsultant.
>> ^
>> space
>>
>>> But for some specific USB cores(e.g. rk3399 SoC DWC3), the
>>> default PHYIF configuration value is fault, so we need to
>>> reconfigure it by software.
>>>
>>> And refer to the DWC3 databook, the GUSB2PHYCFG.USBTRDTIM
>>> must be set to the corresponding value according to the
>>> UTMI+ PHY interface.
>>>
>>> Signed-off-by: William Wu <william.wu@rock-chips.com>
>>> ---
>>> Changes in v7:
>>> - remove quirk and use only one property to configure utmi (Heiko, Rob
>>> Herring)
>>>
>>> Changes in v6:
>>> - use '-' instead of '_' in dts (Rob Herring)
>>>
>>> Changes in v5:
>>> - None
>>>
>>> Changes in v4:
>>> - rebase on top of balbi testing/next, remove pdata (balbi)
>>>
>>> Changes in v3:
>>> - None
>>>
>>> Changes in v2:
>>> - add a quirk for phyif_utmi (balbi)
>>>
>>> Documentation/devicetree/bindings/usb/dwc3.txt | 3 +++
>>> drivers/usb/dwc3/core.c | 25
>>> +++++++++++++++++++++++++ drivers/usb/dwc3/core.h
>>> | 10 ++++++++++
>>> 3 files changed, 38 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/usb/dwc3.txt
>>> b/Documentation/devicetree/bindings/usb/dwc3.txt index 020b0e9..00cc541
>>> 100644
>>> --- a/Documentation/devicetree/bindings/usb/dwc3.txt
>>> +++ b/Documentation/devicetree/bindings/usb/dwc3.txt
>>>
>>> @@ -47,6 +47,9 @@ Optional properties:
>>> - snps,hird-threshold: HIRD threshold
>>> - snps,hsphy_interface: High-Speed PHY interface selection between
>>> "utmi" for>
>>> UTMI+ and "ulpi" for ULPI when the DWC_USB3_HSPHY_INTERFACE has value
>>> 3.
>>>
>>> + - snps,phyif-utmi-width: the value to configure the core to support a
>>> UTMI+ PHY + with an 8- or 16-bit interface. Value 8 select 8-bit
>>> + interface, value 16 select 16-bit interface.
>> Is 'phy_type = "utmi_wide"' not the same as 16-bit width?
>>
>> Again, I think this should be common.
> after knowing that I need to look for that "utmi_wide", I think I'd agree.
>
> I found mention of that in usb/ci-hdrc-usb2.txt and usb/fsl-usb.txt and from
> the coresponding code, I can see that they really mean the 16bit interface,
> the Rockchip TRM as well as the spec [0] seems to call it UTMI+ but really
> looks the same as utmi_wide.
>
> Interestingly, there is already generic code in drivers/usb/phy/of.c so that
> property should probably move to devicetree/bindings/usb/generic.txt
> as well.
>
>
> Heiko
>
> [0] http://cache.nxp.com/files/corporate/doc/support_info/UTMI-PLUS-SPECIFICATION.pdf
Thank you very much for your kindly help and helpful suggestion.:-D
I quite agree with you about use ‘phy_type’ to config UTMI+ interface
for DWC3 controller, and add the ‘phy_type’ property to
devicetree/bindings/usb/generic.txt.
So I shouldn't add a new dts property ‘snps,phyif-utmi-width’ here, and
just use ‘phy_type’is enough.
BTW, I think rk3399 UTMI+ isn't the same as ‘utmi_wide’. Because UTMI+
support both 8-bit data interface and 16-bit data interface, but refer
to code in drivers/usb/phy/of.c and related driver,‘phy_type =
"utmi_wide"’means 16-bits, 'phy_type = utmi' means 8-bits.
Dear Felipe, how about your opinion about add ‘phy_type’ to config UTMI+
interface?
Best Regards
William wu
>
>
>
>
next prev parent reply other threads:[~2016-07-24 16:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 8:59 [PATCH v7 0/5] support rockchip dwc3 driver William Wu
2016-07-14 8:59 ` [PATCH v7 1/5] usb: dwc3: of-simple: add compatible for rockchip rk3399 William Wu
2016-07-14 8:59 ` [PATCH v7 2/5] usb: dwc3: add dis_u2_freeclk_exists_quirk William Wu
2016-07-16 22:51 ` Rob Herring
2016-07-14 8:59 ` [PATCH v7 3/5] usb: dwc3: make usb2 phy utmi interface configurable in DT William Wu
2016-07-16 22:57 ` Rob Herring
2016-07-17 10:28 ` Heiko Stübner
2016-07-24 16:24 ` William.wu [this message]
2016-07-24 16:05 ` William.wu
2016-07-14 8:59 ` [PATCH v7 4/5] usb: dwc3: add dis_del_phy_power_chg_quirk William Wu
2016-07-16 22:58 ` Rob Herring
2016-07-14 9:02 ` [PATCH v7 5/5] usb: dwc3: rockchip: add devicetree bindings documentation William Wu
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=f3e38a34-3d7b-8187-0262-d41b23a3c4a9@rock-chips.com \
--to=william.wu@rock-chips.com \
--cc=John.Youn@synopsys.com \
--cc=balbi@kernel.org \
--cc=briannorris@google.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@google.com \
--cc=eddie.cai@rock-chips.com \
--cc=frank.wang@rock-chips.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@kernel.org \
--cc=sergei.shtylyov@cogentembedded.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).