On Sun, Mar 13, 2011 at 11:06:59PM +0300, Sergei Shtylyov wrote: > The MUSB driver doesn't see its platform device on DM644x EVM board anymore > since commit 73b089b052a69020b953312a624a6e1eb5b81fab (usb: musb: split davinci > to its own platform_driver) because the new probe is called as subsys_initcall() > now, and the device is registered later than that by the board code. Move the > registration to davinci_evm_init() -- it's safe to do so because the MUSB core > device still gets initialized as fs_initcall() -- which is late enough for the > I2C GPIO expander (which controls VBUS) to be initialized. > > Signed-off-by: Sergei Shtylyov <sshtylyov@xxxxxxxxxxxxx> Kevin feel free to take this into your tree: Acked-by: Felipe Balbi <balbi@xxxxxx> > --- > The patch is against the recent DaVinci tree. > It fixes post 2.6.38-rc1 regression, so should be applied immediately! I wonder how noone has noticed that from -rc1 until now. -- balbi -- 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
