On Wed, Dec 24, 2014 at 01:51:32PM +0100, gianluca wrote: > On 12/23/2014 01:12 AM, Peter Chen wrote: > >Ok, then just try to get the working version, and find the difference. > >>From my mind, it should be PLL related. > > > > Here I am again ;-) > > The following log is taken by an automatic-script during bootup (rc.local). > > the smtp_device.c throw a time out, so the imx_ehci logs an error > during bootup: unable to init phy > > >=EE= HW_CLKCTRL_PLL1CTRL0: /dev/mem opened. > >Memory mapped at address 0xb6f30000. > >Value at address 0x80040020 (0xb6f30020): 0x60000 > > >=EE= HW_CLKCTRL_PLL1CTRL1: /dev/mem opened. > >Memory mapped at address 0xb6f34000. > >Value at address 0x80040030 (0xb6f34030): 0x800004B1 > First I would like to confirm, the "USB1" you said is the second USB controller, and will use dedicated PLL1, is it correct? If it is, you may need to print PLL1 at the code once the timeout occurs, since the PLL1 may be normal behavior after some times. You have mentioned, if it is built as module, every thing works ok, correct? > after issuing a soft reboot (invoking reboot command) here is the new log: > > >=WW= HW_CLKCTRL_PLL1CTRL0: /dev/mem opened. > >Memory mapped at address 0xb6f5e000. > >Value at address 0x80040020 (0xb6f5e020): 0x60000 > >=WW= HW_CLKCTRL_PLL1CTRL1: /dev/mem opened. > >Memory mapped at address 0xb6fc9000. > >Value at address 0x80040030 (0xb6fc9030): 0x800004B1 > > So the hardware CLKCTRL_PLL1CTRL[0/1] registers have the same value. > -- Best Regards, Peter Chen -- 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
