On Wednesday 19 March 2008, Kevin Hilman wrote: > However, if I then plug the key back in, nothing happens. > > 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? Just for the record ... that's always been a problem. There's some strange side-effect driven magic in the Mentor IP, right in that area, which has always been fragile. For example, it seems to think something other than the state of the ID pin should control whether it's in the A-side state machine (default host) or the B-side one (default peripheral), and it gets fairly twitchey about VBUS levels too ... as in, it doesn't allow the specified 100 msec for it to stabilize, and enters a fault/shutdown mode if voltage drops because of, say, contact bounce or inrush current, while it stabilizes. Needing that "force session start" is a warning flag. The very notion of that kind of "session" is something introduced by Mentor, which is not part of the OTG spec (at least, not in anything like that form). Multiple weeks have been wasted trying to sort out misbehavior in that area, and there seem to be revision-specific issues too. - Dave -- 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
