linux-kernel - Re: [PATCH 3/4] usb: dwc3: make usb2 phy interface configurable in DT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 09 May 2016 21:28:54 +0800
From:	William Wu <william.wu@...k-chips.com>
To:	Felipe Balbi <balbi@...nel.org>, gregkh@...uxfoundation.org,
	heiko@...ech.de
CC:	briannorris@...gle.com, dianders@...gle.com,
	kever.yang@...k-chips.com, huangtao@...k-chips.com,
	frank.wang@...k-chips.com, eddie.cai@...k-chips.com,
	John.Youn@...opsys.com, linux-kernel@...r.kernel.org,
	linux-usb@...r.kernel.org
Subject: Re: [PATCH 3/4] usb: dwc3: make usb2 phy interface configurable in
 DT

On 05/09/2016 08:18 PM, Felipe Balbi wrote:
> Hi,
>
> William Wu <william.wu@...k-chips.com> writes:
>> Add snps,phyif_utmi_16_bits devicetree property. USB2 phy
> this needs a quirk_ prefix...
      Yes, maybe a quirk is more proper. As you mentioned,
      the PHYIf can be configured during coreconsultant.
      But for some specific usb cores(e.g. rk3399 soc dwc3),
      the default PHYIf configuration is error, so we need to
      reconfigure it by software.
>
>> interface is hardware property, and it's platform dependent,
>> so we need to configure it in devicetree to set the core to
>> support a UTMI+ PHY with an 8- or 16-bit interface.
>>
>> And refer to the dwc3 databook, the GUSB2PHYCFG.USBTRDTIM
>> must set to the corresponding value according to the usb2
>> phy interface.
> right, that's fine. But also note on section 8.1.1 Table 8-1 where it
> states:
>
> |-------------+------------------------------------------------------------|
> | GUSB2PHYCFG | Program the following PHY configuration fields: USBTrdTim, |
> |             | FSIntf, PHYIf, TOUTCal, or leave the default values if     |
> |             | the correct power-on values were selected during           |
> |             | coreConsultant configuration.  Note: The PHY must not      |
> |             | be enabled for auto-resume in device mode. Hence the       |
> |             | field GUSB2PHYCFG[15] (ULPIAutoRes) must be written        |
> |             | with '0' during the power-on initialization in case        |
> |             | the reset value is '1'.                                    |
> |             |                                                            |
> |-------------+------------------------------------------------------------|
>
> You only need this because your core was badly configured in
> coreConsultant.
>