[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87ina6vodf.fsf@linux.intel.com>
Date: Thu, 08 Mar 2018 12:43:40 +0200
From: Felipe Balbi <balbi@...nel.org>
To: William Wu <william.wu@...k-chips.com>, gregkh@...uxfoundation.org,
Roger Quadros <rogerq@...com>
Cc: heiko@...ech.de, linux-kernel@...r.kernel.org,
linux-usb@...r.kernel.org, linux-rockchip@...ts.infradead.org,
frank.wang@...k-chips.com, huangtao@...k-chips.com,
dianders@...gle.com, briannorris@...gle.com, groeck@...gle.com,
daniel.meng@...k-chips.com, John.Youn@...opsys.com,
william.wu@...k-chips.com, lin.huang@...k-chips.com
Subject: Re: [PATCH] usb: dwc3: core: power on PHYs before initializing core
Hi Roger,
William Wu <william.wu@...k-chips.com> writes:
> The dwc3_core_init() gets the PHYs and initializes the PHYs with
> the usb_phy_init() and phy_init() functions before initializing
> core, and power on the PHYs after core initialization is done.
>
> However, some platforms (e.g. Rockchip RK3399 DWC3 with Type-C
> USB3 PHY), it needs to do some special operation while power on
> the Type-C PHY before initializing DWC3 core. It's because that
> the RK3399 Type-C PHY requires to hold the DWC3 controller in
> reset state to keep the PIPE power state in P2 while configuring
> the Type-C PHY, otherwise, it may cause waiting for the PIPE ready
> timeout. In this case, if we power on the PHYs after the DWC3 core
> initialization is done, the core will be reset to uninitialized
> state after power on the PHYs.
>
> Fix this by powering on the PHYs before initializing core. And
> because the GUID register may also be reset in this case, so we
> need to configure the GUID register after powering on the PHYs.
>
> Signed-off-by: William Wu <william.wu@...k-chips.com>
does this cause any regressions for your boards?
--
balbi
Download attachment "signature.asc" of type "application/pgp-signature" (833 bytes)
Powered by blists - more mailing lists