From: George Cherian <george.cherian@ti.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>, <balbi@ti.com>
Cc: <gregkh@linuxfoundation.org>, <linux-usb@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usb: musb: core: Disable the Interrupts till BABBLE is fully handled
Date: Fri, 14 Nov 2014 14:41:57 +0530 [thread overview]
Message-ID: <5465C75D.4070909@ti.com> (raw)
In-Reply-To: <5465C06C.90705@linutronix.de>
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!!!!
>
> Sebastian
>
next prev parent reply other threads:[~2014-11-14 9:14 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 [this message]
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
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=5465C75D.4070909@ti.com \
--to=george.cherian@ti.com \
--cc=balbi@ti.com \
--cc=bigeasy@linutronix.de \
--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.