From mboxrd@z Thu Jan 1 00:00:00 1970 From: balbi@ti.com (Felipe Balbi) Date: Mon, 14 Mar 2011 10:52:49 +0200 Subject: [PATCH] DM644x EVM: register MUSB device earlier In-Reply-To: <201103132306.59986.sshtylyov@ru.mvista.com> References: <201103132306.59986.sshtylyov@ru.mvista.com> Message-ID: <20110314085248.GA2285@legolas.emea.dhcp.ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 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 Kevin feel free to take this into your tree: Acked-by: Felipe Balbi > --- > 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