On Fri, Dec 19, 2014 at 12:35:49PM +0100, gianluca wrote:
CC linux-usb ML
> Hello Fabio and Peter,
>
> I am suffering some strange behaviour in initializing the smtp reset
> block of the USB1 (host) in iMX28 running kernel 3.12.1 (vanilla) on
> my custom board based on iMX28EVK.
>
> With bootlets I DO NOT TOUCH any register to the USB PHY and family...
> With bootloader (barebox 2013-03) I do not initialize the usbcore,
> and the only stuff I set is the pinmux for USB_ID and USB_OC for
> both ports, but none used.
>
> In the device tree there are both declarations for usb-device role
> and usb-host role.
>
> Sometimes during cold-start or warm-start (due to a reset pressure,
> and/or a reboot command issued) the USB1 (host) is not configured
> because the function:
>
> stmp_reset_block() in the lib/stmp_device.c is exiting due to a TIMEOUT.
>
> The following code is executed correctly:
>
> > /* clear CLKGATE */
> > writel(STMP_MODULE_CLKGATE, reset_addr + STMP_OFFSET_REG_CLR);
> >
> > /* set SFTRST to reset the block */
> > writel(STMP_MODULE_SFTRST, reset_addr + STMP_OFFSET_REG_SET);
> > udelay(1);
>
> And now the problematic part:
>
> > /* poll CLKGATE becoming set */
> > while ((!(readl(reset_addr) & STMP_MODULE_CLKGATE)) && --timeout)
> > /* nothing */;
> > if (unlikely(!timeout
>
> it waits for 0x400 (timeout value counter) read access, then exit
> with a timeout. It looks like the HW_USBPHY_CTRL for USBPHY1
> (0x8007E030) has the following value: 0x80020000 (so no CLKGATE
> high...)
It means the PHY works abnormal, would you please check the related
PLL is configured successfully?
>
> Looks like someone else is driving it low ...
>
> The reference manual says:
>
> >Note this bit can be auto-cleared if there is any wakeup event when USB is suspended while
> >ENAUTOCLR_CLKGATE bit of HW_USBPHY_CTRL is enabled
>
> But looking at the registers all those stuff are DISABLED (or in
> DEFAULT MODE).
>
> WTF is happening?
>
> 99% a powercycle and/or a reset pressure does the trick, but I was
> wondering what is going on... maybe an hardware issue???
>
> Do you know something related to this issue? Eg.: errata or other
> hardware known issues...
> Or what about the bootrom code and initialization (boot pins and
> initializers)??
>
> I hope to be clear enough.
>
> Best regards,
> --
> ,,,
> (o o)
> ======oOO==(_)==OOo======
>
> Gianluca Renzi
> R&D
> phone: +39.0542.609120
> fax: +39.0542.609212
>
> .oooO Oooo.
> ======( )==( )=======
> \ ( ) /
> \_) (_/
>
> ===================
> | I would like to |
> | fix the world, |
> | but they're not |
> | giving me the |
> \ source code! /
> ---------------
> ¯\_(".)_/¯
--
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
