Re: [PATCH] OMAP3: PM: Ensure MUSB is accessible before we attempt to reset it

Hi Jon, Jon Hunter jon-hun...@ti.com writes: From: Jon Hunter jon-hun...@ti.com Depending on the OMAP3 boot mode the MUSB peripheral may or may not be accessible when the kernel starts. The OMAP3 can boot from several devices including USB. The sequence of the devices the OMAP will

Re: [PATCH] OMAP3: PM: Ensure MUSB is accessible before we attempt to reset it

Kevin Hilman wrote: Thanks for this fix. I'll consider this another vote for switching to omap_hwmod. To be honest, I am not too familiar with omap_hwmod. Only what I have seen here: http://patchwork.kernel.org/patch/28171/ Anyway, sounds like a good idea. I am not a fan of the current

Re: [PATCH] OMAP3: PM: Ensure MUSB is accessible before we attempt to reset it

Jon Hunter jon-hun...@ti.com writes: Kevin Hilman wrote: Thanks for this fix. I'll consider this another vote for switching to omap_hwmod. To be honest, I am not too familiar with omap_hwmod. Only what I have seen here: http://patchwork.kernel.org/patch/28171/ Anyway, sounds like a

RE: [PATCH] OMAP3: PM: Ensure MUSB is accessible before we attempt to reset it

From: Jon Hunter jon-hun...@ti.com Depending on the OMAP3 boot mode the MUSB peripheral may or may not be accessible when the kernel starts. The OMAP3 can boot from several devices including USB. The sequence of the devices the OMAP will attempt to boot from is configured via the sys_boot

[PATCH] OMAP3: PM: Ensure MUSB is accessible before we attempt to reset it

From: Jon Hunter jon-hun...@ti.com Depending on the OMAP3 boot mode the MUSB peripheral may or may not be accessible when the kernel starts. The OMAP3 can boot from several devices including USB. The sequence of the devices the OMAP will attempt to boot from is configured via the sys_boot pins