>Sent: Friday, March 21, 2008 1:55 AM >On Thursday 20 March 2008, Felipe Balbi wrote: >> Could it be some >> problem in the ULPI support for omap3 that's preventing musb to wake up >> and switch to host role ? > >Your theory is as good as mine; I don't have that hardware. > >I was just pointing out that this specific area has always >been a significant PITA for the MUSB silicon ... I'm not the >only developer who's ended up losing weeks of time chasing >(undocumented) bogosity in the area of host-side startup. > >The thing is that making it "switch to host role" is the >very black magic that regularly misbehaved. ISTR there was >a chicken/egg thing going on: it couldn't know it needed to >switch to "host role" unless the oddball Mentor "session" >was already active, but it couldn't be activated unless you >somehow knew it should be in host role... The right way then to debug would be to do an LA probe of ULPI signals on re-attach. To get around this problem, I have heard of implementations having a separate GPIO implemented to wakeup the system on cable attaches. Don't remember which implementation though. I will see if I get time to work on this and will keep posted. > > >-- >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 -- 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
