On Wednesday 15 April 2009, Sascha Hauer wrote: > > I looked briefly at > > some recent OTG patches on the list, the whole infrastructure seems to be > > still very much experimental and unstable. That was a couple of months ago > > though. > > Ok, that whas the impression I got, too. I suspect there will never be a "completely stable" OTG infrastructure, since the hardware standards aren't all that relevant to what software needs. So it won't be so much "code to interface X and be done", as "support these interfaces, and extend as needed". That said, the (a) peripheral/gadget and (b) host side interfaces to the upper level code shouldn't need changes (except maybe OTG 2.0 exposing the OTG descriptor slightly differently). The problematic parts seem to relate to how things like ID signal detection get handled ... hardware can do stuff like that *very* differently in different designs. Use the otg_transceiver as much as practical; be prepared to extend it; and structurally, make sure your code can handle all three modes: host-only, peripheral-only, and dual-role (OTG). - Dave -- 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
