On Thu, 20 Mar 2008 18:04:01 +0530, "Pandita, Vikram" <vikram.pandita@xxxxxx> wrote: > Hi Felipe/Kevin > >>To: Kevin Hilman; Linux omap >>Subject: RE: OMAP3430: MUSB host and hot-plugging >> >>> Forcing a session start via "echo 'F' > /proc/driver/musb_hdrc" causes >>> the device to be (re)detected and things look good again. It is not >>> until I force the session start that I see the interrupt and the >>> CONNECT event. >>> >>> Any ideas why this isn't detected on insertion? >> >>You're better than me then, I can't get even the first insertion >>I'm suspecting that twl4030_phy_suspend is somehow >>messing it up. I'm now digging on it and still >>I can't say for sure what's happening. >> >>Maybe somebody else has other comments on that. > > If you can provide us the procedure to enable hot-plugging for MUSB on > OMAP3430, we will look into this issue. As far as musb driver is concerned it should be just a mater of building it with otg support. But as of now, I cannot get id pin status to musb using twl4030. Maybe we still have some missing pieces on linux-omap, which I'm researching on that. -- Best Regards, Felipe Balbi http://felipebalbi.com me@xxxxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
