[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141119031211.GC24874@saruman>
Date: Tue, 18 Nov 2014 21:12:11 -0600
From: Felipe Balbi <balbi@...com>
To: Bin Liu <binmlist@...il.com>
CC: <balbi@...com>, George Cherian <george.cherian@...com>,
<gregkh@...uxfoundation.org>, <linux-usb@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <bigeasy@...utronix.de>
Subject: Re: [PATCH] usb: musb: core: Disable the Interrupts till BABBLE is
fully handled
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 <balbi@...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 <balbi@...com>
> >> Signed-off-by: George Cherian <george.cherian@...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
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists