Hi Balbi, yes, I'm working on a marvell's platform and there is an otg controller. For the otg controller, there are there drivers for host, udc and otg device. And it will register relative devices in the process of init_machine(). In the probe function of host driver (named ehci-mv.c, not an open source code, just like ehci-fsl.c), it will call otg_get_transceiver() if CONFIG_USB_OTG is defined. But at this time, the otg driver has not been inited and there is no transceiver been setted. I find that patch (commit id:4661ffc91befc8c5ee080720120da1d53851060a) will let the host driver init before than otg driver and which cause the problem I met. Thanks. Neil 2011/7/29 Felipe Balbi <balbi@xxxxxx>: > Hi, > > On Fri, Jul 29, 2011 at 02:24:40PM +0800, Neil Zhang wrote: >> I find that there is a patch (commit >> id:4661ffc91befc8c5ee080720120da1d53851060a) >> has changed the usb initialization sequence. But I encountered a problem that >> otg_get_transceiver() can not get the transceiver during Host driver's >> probe function >> because otg has not been inited yet. >> >> Does any one else encountered this problem too? > > can you show some stack dump or some better description of when the > problem happens ? > > -- > 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
