public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <felipe.balbi@nokia.com>
Cc: ext Felipe Balbi <me@felipebalbi.com>,
	ext David Brownell <david-b@pacbell.net>,
	linux-omap@vger.kernel.org
Subject: Re: pending patch
Date: Fri, 9 May 2008 14:55:15 -0700	[thread overview]
Message-ID: <20080509215515.GG5976@atomide.com> (raw)
In-Reply-To: <20080509091919.GB4326@gandalf.research.nokia.com>

* Felipe Balbi <felipe.balbi@nokia.com> [080509 02:20]:
> On Fri, Apr 25, 2008 at 09:45:43PM +0300, ext Felipe Balbi wrote:
> > On Fri, Apr 25, 2008 at 09:36:44AM -0700, Tony Lindgren wrote:
> > > * Felipe Balbi <felipe.balbi@nokia.com> [080425 03:19]:
> > > > On Fri, Apr 25, 2008 at 02:35:21AM -0700, David Brownell wrote:
> > > > > On Friday 25 April 2008, Felipe Balbi wrote:
> > > > > > Hi Tony and Dave,
> > > > > > 
> > > > > > there's this one pending patch [1]. Do you guys have any comments on that
> > > > > > one?
> > > > > > 
> > > > > > Author: Felipe Balbi <felipe.balbi@nokia.com>
> > > > > > Date:   Thu Apr 17 17:34:20 2008 +0300
> > > > > > 
> > > > > >     USB: MUSB: Don't ignore disconnect on suspend
> > > > > >     
> > > > > >     As soon as a usb device is disconnect we should
> > > > > >     fall into a_wait_bcon state, ignoring disconnect
> > > > > >     irq will prevent this behaviour.
> > > > > 
> > > > > If it passes the OTG tests, fine.  I don't recall how the
> > > > > HNP handoff's disconnect signaling is handled ... presumably
> > > > > it's different from some "real" disconnect.
> > > > 
> > > > No opt available for now...
> > > > The problem is that when you ignore disconnect on suspend you only ack
> > > > the disconnect interrupt after attaching other device. It won't get us
> > > > too much trouble besides the bit will still set in int_src, but still
> > > > musb should ack disconnect as soon as it happens, shouldn't it? And
> > > > right after that start the timer for switching from a_wait_bcon to
> > > > a_wait_vfall and after that a_idle.
> > > > 
> > > > But as soon as I have and opt available, I'll try to run this test and
> > > > report you if I can see any issues with this patch applied.
> > > > 
> > > > For now, let's keep it as pending so.
> > > 
> > > Yeah. I have not applied any musb/tusb patches because of being afraid
> > > of the HS OTG OPT tests breaking.. Still have them all in my l-o mailbox
> > > though. So let's plan on applying things after somebody (Felipe?) gets
> > > to run HS OTG OPT on them for musb and tusb.
> 
> Ok, this patch doesn't break any opt tests. Safe to apply. Tested
> yesterday.

Pushing.

Tony

      reply	other threads:[~2008-05-09 21:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-25  7:52 pending patch Felipe Balbi
2008-04-25  9:35 ` David Brownell
2008-04-25 10:18   ` Felipe Balbi
2008-04-25 16:36     ` Tony Lindgren
2008-04-25 18:45       ` Felipe Balbi
2008-05-09  9:19         ` Felipe Balbi
2008-05-09 21:55           ` Tony Lindgren [this message]

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=20080509215515.GG5976@atomide.com \
    --to=tony@atomide.com \
    --cc=david-b@pacbell.net \
    --cc=felipe.balbi@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=me@felipebalbi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox