On Friday 29 August 2008, Felipe Balbi wrote: > > You're talking about some other problem. I'm talking about > > the one where it *OOPSES* while binding to the gadget driver. > > Hmm, that I've never seend. Using musb with omap3 and n810. Right, that's why I thought I'd chase the easier host-side issue first. Must have "apt-get install ..." working after all!! > > > Beagle should be sourcing up to 200mA. See if this patch helps: > > > > Just 200 mA? That could explain a lot. Though looking > > at the Beagle TRM, it says "100mA" (as with TUSB) ... > > some version of this patch seems necessary. (I have some > > others to usb-musb.c, will send them all.) > > Yeah, the TRM says 100mA but I could use 200mA storage devices with > heavy transfers without any problems. Were those self-powered devices, or bus-powered? Descriptors are not entirely trustworthy about current usage. Sometimes they represent worst-case; sometimes it's best-case. > Do you have the BLACKLIST_HUB set? (just to be sure). No, that's not set. > > > I think I recall seeing this with my sniffer, but as it seemed not be > > > generating much problems, I let it be since I had other stuff to check. > > > Looks like I was wrong... :-s > > > > The ep3in/status stuff is no problem. The problem is the VBUS_ERR irq. > > That irq is buggy, we had to put a retry since musb was rasing that > interrupt durring enumeration for a few usb devices (bad capacitors?). IMO it's the silicon that's buggy. The specific window I kept seeing was between VBUS_ON and the 100msec later where it's expected to be stable. During that window, VBUS is allowed to not be stable ... which is good, because that's when current spikes happen while charging the various capacitances involved. (Cable, caps at either end, etc.) I saw TUSB6010 reporting VBUS_ERR during that 100msec window ... and same thing with DaVinci. Both needed retry logic to cope with the inappropriate VBUS fault reports. The thing in common is the silicon IP, not the hardware. - 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
