On Fri, Nov 14, 2014 at 02:41:57PM +0530, George Cherian wrote: > > On 11/14/2014 02:12 PM, Sebastian Andrzej Siewior wrote: > >On 11/14/2014 09:24 AM, George Cherian wrote: > >>Disable the MUSB interrupts till MUSB is recovered fully from BABBLE > >>condition. There are chances that we could get multiple interrupts > >>till the time the babble recover work gets scheduled. Sometimes > >>this could even end up in an endless loop making MUSB itself unusable. > >How do you trigger the babble error? Is this something that happens > >during suspend resume, plugging / unplugging a device or randomly while > >the device is used? > I have never seen this error while device is successfully enumerated and > while working fine. > Mostly u get it when we connect/disconnect devices to HOST port. > Normally I use the following for testing BABBLE > - Especially when a fully loaded USB HUB getting connected to HOST port. > - Or repeatedly load and unload musb_hdrc.ko with some device connected. > > If nothing of the above work you might be the lucky one to have a good > board!!!! if you have a BBB, connect host port to device port, load g_zero and run any of testusb test cases. -- balbi
Attachment:
signature.asc
Description: Digital signature