From: Daniel Mack <daniel-cYrQPVfZoowdnm+yROfE0A@public.gmane.org>
To: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Felipe Balbi <balbi-l0cyMroinI0@public.gmane.org>,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
george.cherian-l0cyMroinI0@public.gmane.org
Subject: Re: Gadget regression with enabling of MUSB babble interrupt handling
Date: Thu, 19 Jun 2014 12:08:48 +0200 [thread overview]
Message-ID: <53A2B6B0.2040804@zonque.org> (raw)
In-Reply-To: <20140619095655.GA29055-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
(+ George)
On 06/19/2014 11:56 AM, Tony Lindgren wrote:
> Looks like commit ca88fc2ef0d7 (usb: musb: add a work_struct
> to recover from babble errors) causes MUSB gadgets to stop
> enumerating at least on omap3. Reverting the the commit fixes
> the issue.
Hmm, so do you see babble errors occuring?
Also, there are some more patches for musb and babble error recovery on
the usb list, namely the ones starting here in v6:
http://marc.info/?l=linux-usb&m=140109627505065&w=4
Care to give them a try?
Thanks,
Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-06-19 10:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 9:56 Gadget regression with enabling of MUSB babble interrupt handling Tony Lindgren
[not found] ` <20140619095655.GA29055-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2014-06-19 10:08 ` Daniel Mack [this message]
2014-06-19 10:31 ` Tony Lindgren
2014-06-19 10:36 ` Daniel Mack
[not found] ` <53A2BD34.1060409-cYrQPVfZoowdnm+yROfE0A@public.gmane.org>
2014-06-19 10:43 ` Tony Lindgren
[not found] ` <20140619104324.GC29055-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2014-06-19 10:50 ` Daniel Mack
2014-06-19 11:24 ` Tony Lindgren
2014-06-20 3:41 ` George Cherian
2014-06-20 6:20 ` Tony Lindgren
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=53A2B6B0.2040804@zonque.org \
--to=daniel-cyrqpvfzoowdnm+yrofe0a@public.gmane.org \
--cc=balbi-l0cyMroinI0@public.gmane.org \
--cc=george.cherian-l0cyMroinI0@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.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.