From: Felipe Balbi <balbi@ti.com>
To: Bin Liu <binmlist@gmail.com>
Cc: <balbi@ti.com>, George Cherian <george.cherian@ti.com>,
<gregkh@linuxfoundation.org>, <linux-usb@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <bigeasy@linutronix.de>
Subject: Re: [PATCH] usb: musb: core: Disable the Interrupts till BABBLE is fully handled
Date: Tue, 18 Nov 2014 21:12:11 -0600 [thread overview]
Message-ID: <20141119031211.GC24874@saruman> (raw)
In-Reply-To: <CADYTM3b9zSpP2yO2Lp5WOxBxB0yX=bG_20mFKQNGnyXV0XLOHg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
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@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 <balbi@ti.com>
> >> Signed-off-by: George Cherian <george.cherian@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
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-11-19 3:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 8:24 [PATCH] usb: musb: core: Disable the Interrupts till BABBLE is fully handled George Cherian
2014-11-14 8:42 ` Sebastian Andrzej Siewior
2014-11-14 9:11 ` George Cherian
2014-11-14 21:02 ` Felipe Balbi
2014-11-18 21:17 ` Felipe Balbi
2014-11-19 0:44 ` Bin Liu
2014-11-19 3:12 ` Felipe Balbi [this message]
2014-11-24 17:47 ` Sebastian Andrzej Siewior
2014-11-24 17:49 ` Sebastian Andrzej Siewior
2014-11-24 18:20 ` Felipe Balbi
2014-11-24 20:39 ` Peter Stuge
2014-11-24 20:56 ` Sebastian Andrzej Siewior
2014-11-25 1:09 ` Felipe Balbi
2014-11-25 8:24 ` Sebastian Andrzej Siewior
2014-11-25 14:49 ` Felipe Balbi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141119031211.GC24874@saruman \
--to=balbi@ti.com \
--cc=bigeasy@linutronix.de \
--cc=binmlist@gmail.com \
--cc=george.cherian@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.