Hi, On Mon, Aug 08, 2011 at 09:20:38AM +0200, Sascha Hauer wrote: > On Mon, Aug 08, 2011 at 09:21:21AM +0530, Pavan Kondeti wrote: > > How does this work if both gadget and host are active. What name should > > be passed to transceiver? "mxc-ehci" or "mxc-udc" > > Neither of both. There should be a device which handles the ehci > resource and which either registers the otg, host or device part > depending on platform data. This device should also handle the phy. > > Currently we have the situation that host and device driver are > completely unaware of each other, at least on most architectures. > >From what we have in the tree I like the msm usb otg best, apart > from the fact that it's a platform specific solution. It's even > not complicsted to make it work on i.MX and therefore probably > on other architectures aswell. I think these kind of things should be considered after we have the basic phy support separated from otg, so not at this stage. I'm not sure how it would work with Felipe's idea of keeping everything as flexible as possible. I can only point out that there should not be anything preventing something like pci card or sdio card providing a controller and a transceiver to the system, so relying on platform data may not be enough. -- heikki -- 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
