> > I'm not sure I follow. What do you call OTG driver ? If it's all that > timer initialization that should be done on drivers/usb/core/ in a > generic manner, so everybody can use. Remember that OTG related to Host > and Device functionality and all those OTG timers should be managed by > the core framework. > If the user has OTG driver, then OTG driver handles all resource management for that controller, like PHY, register mapping, clock. At this OTG driver, it will call phy->init, phy->set_wakeup, phy->suspend and phy->resume, etc. The code routines at device and host is active mode, PHY is active and clocks are on. If the user hasn't OTG driver, the host-only or device-only driver takes the same responsibilities like above OTG driver. >From my point, PHY is the resource, any users can use it. > -- > 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
