Hi Fabio, On 15.12.2014 17:05, Fabio Estevam wrote: > On Tue, Dec 9, 2014 at 11:48 AM, Matthieu CASTET > <matthieu.castet@xxxxxxxxxx> wrote: > >> Is your usb phy ok ? >> >> I saw freeze like that when there was no ulpi communication with the >> usb phy. > > Thanks. I fixed it by passing 'regulator-boot-on' to the USB regulators > > --- a/arch/arm/boot/dts/imx51-babbage.dts > +++ b/arch/arm/boot/dts/imx51-babbage.dts > @@ -137,6 +137,7 @@ > regulator-max-microvolt = <5000000>; > gpio = <&gpio2 5 GPIO_ACTIVE_HIGH>; > enable-active-high; > + regulator-boot-on; > }; > > reg_usbotg_vbus: regulator@1 { > @@ -149,6 +150,7 @@ > regulator-max-microvolt = <5000000>; > gpio = <&gpio1 7 GPIO_ACTIVE_HIGH>; > enable-active-high; > + regulator-boot-on; > }; > }; > Recently I was told by Mark Brown that this is an incorrect hack --- you should either create a regulator consumer or pass "regulator-always-on" property. >From Documentation/devicetree/bindings/regulator/regulator.txt: [snip] - regulator-boot-on: bootloader/firmware enabled regulator -- With best wishes, Vladimir -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html