All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@zonque.org>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-usb@vger.kernel.org, Felipe Balbi <balbi@ti.com>,
	linux-omap@vger.kernel.org, george.cherian@ti.com
Subject: Re: Gadget regression with enabling of MUSB babble interrupt handling
Date: Thu, 19 Jun 2014 12:36:36 +0200	[thread overview]
Message-ID: <53A2BD34.1060409@zonque.org> (raw)
In-Reply-To: <20140619103100.GB29055@atomide.com>

Hi Tony,

On 06/19/2014 12:31 PM, Tony Lindgren wrote:
> * Daniel Mack <daniel@zonque.org> [140619 03:10]:
>> 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?
> 
> Not that I noticed of.
>  
>> 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?
> 
> I can confirm that "[PATCH v6 1/5] usb: musb: core: Handle Babble
> condition only in HOST mode" fixes the issue for me. Also the
> explanation in the patch description explains why it breaks, and
> probably for all gadgets too because "BABBLE and RESET share the
> same interrupt" so it's RESET in peripheral mode.

Ok, thanks for testing. I was told Felipe was out for some weeks, so I
don't know when these patches will be reviewed and merged.

> But that also raises a question: Were these patches merged for
> v3.16 ever even tested in peripheral mode?

At the time, I had no such hardware to test this on, so I was hoping for
more testers to give them a try in different environments, which
apparently didn't happen. It fixed a dead USB port condition on
host-mode enabled hardware, though.

We should make sure at least patch 1/5 from the series mentioned above
makes it to 3.16.


Thanks,
Daniel

  reply	other threads:[~2014-06-19 10:36 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
2014-06-19 10:31     ` Tony Lindgren
2014-06-19 10:36       ` Daniel Mack [this message]
     [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=53A2BD34.1060409@zonque.org \
    --to=daniel@zonque.org \
    --cc=balbi@ti.com \
    --cc=george.cherian@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=tony@atomide.com \
    /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.