The switching modules path may prove productive for our purposes, but I think actual otg drivers dont do this, as theres a state machine that drives mode changing automatically, so they keep both drivers resident and enable/disable them.
The more I look into actual otg however, I'm less intetested than I originally was. I think for user purposes it may actually be better to have manual switching not unlike the enabling of mass storage mode, particularly as a lot of people are likely to be using cobbled together cable & adapter assemblies that wouldnt put a compliant otg device into host mode. On Feb 17, 2010 6:49 PM, "Andrew de Quincey" <a...@lidskialf.net> wrote: Hi, quick status update before I go to sleep. I've just fixed the msm72k_udc.ko gadget driver so it can be unloaded/loaded properly. I've tested it by repeatedly loading/unloading the msm72k_udc.ko gadget and the ehci-hcd.ko host drivers one after another and it seems fairly stable (I'd bet there are a number of bugs remaining though :). Next up, I need to replace the "usb function notifier" and msm_hsusb_set_vbus_state() stuff and we ought to have fully functioning device and host drivers that can be rmmoded/insmodded in order to switch usb "modes". I should have this done sometime this week, and I'll send an updated patch then. (right now, the gadget driver can't detect when the USB cable is plugged in because of these missing calls). After that, we can investigate "proper" USB OTG support (ala the Droid) and whether the phone can output power on VBUS. I also wonder what Google's stance on this is; is there a chance of getting it into the mainline android-MSM tree? I suppose I should also try and get it into the vanilla kernel tree to help out people porting to this platform in future. -- unsubscribe: android-kernel+unsubscr...@googlegroups.com<android-kernel%2bunsubscr...@googlegroups.com> website: http://groups.google.com/grou... -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
