On Tue, Nov 18, 2014 at 06:44:39PM -0600, Bin Liu wrote: > Felipe, > > On Tue, Nov 18, 2014 at 3:17 PM, Felipe Balbi <ba...@ti.com> wrote: > > On Fri, Nov 14, 2014 at 01:54:46PM +0530, 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. > >> > >> Reported-by: Felipe Balbi <ba...@ti.com> > >> Signed-off-by: George Cherian <george.cher...@ti.com> > > > > while this helps the situation it doesn't solve the problem I'm having > > with testusb on BBB when host port is connected to peripheral port on > > the same BBB. > > Try to find a BB white (which has rev 1.0 SoC) to see if babble still > happens, this could be PHY hw issue.
it only happens with my BBB when peripheral port is connected straight to host port. If I use another board as g_zero, then tests work just fine. If someone else can confirm this is the case with their board, I'd be happy. -- balbi
signature.asc
Description: Digital signature
