On Wed, Dec 14, 2016 at 04:47:38PM -0800, Brian Norris wrote: > On Wed, Dec 14, 2016 at 04:10:38PM -0800, Doug Anderson wrote: > > On Wed, Dec 14, 2016 at 2:11 AM, Xing Zheng <zhengxing@xxxxxxxxxxxxxx> wrote: > > > From: William wu <wulf@xxxxxxxxxxxxxx> > > > > > > We found that the suspend process was blocked when it run into > > > ehci/ohci module due to clk-480m of usb2-phy was disabled. One more thing: why is the USB2 PHY relevant to the OHCI controller? And if it is relevant, why isn't there a PHY phandle for it in usb_host0_ohci and usb_host1_ohci in rk3399.dtsi? As it stands, your patch is hacking in USB2 clock references for OHCI, but you're not actually managing the PHY there at all. Seems like you'd want to do all-or-nothing if there's a functional dependency between the OHCI controllers and the USB2 PHYs. Brian -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
