On Thursday 16 October 2008, Koen Kooi wrote: > > The MUSB transceiver-level issues I was aware of (mostly > > on Overo, but minor glitches on Beagle) now seem to be > > fixed by the combination of the IRQ patches I sent last > > week, plus the twl4030-usb patch I just sent. > > Does your patch also make OTG cable detect work? I'm not entirely sure what you mean by that ... For an OTG connector there are four states of note: (1) Nothing connected (2) There's a B-connector (2a) with nothing on the other end, same as (1) (2b) with a host on the other end, suppling VBUS (3) There's an A-connector, grounding the ID pin (3a) with nothing on the other end, (3b) with a periphereral pulling up D+ or D- That patch uses the STS_HW_CONDITIONS register to detect those three basic states ... Now, whether the musb_hdrc code handles both (3a) and (3b) correctly is another issue. Recently it only handled the (3b) case, which is what I tend to use. On this go-around I didn't test the (3a) case. If that starts to work, great; but I was focussing on fixing the regresssions. Does it work for you? (So you can plug in a B-device to the other end, "later"?) - 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
