public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: Paul Walmsley <paul@booyaka.com>,
	Steve Sakoman <sakoman@gmail.com>,
	Tony Lindgren <tony@atomide.com>,
	me@felipebalbi.com, Jeff Steele <jsteele@coloradocollege.edu>,
	linux-omap <linux-omap@vger.kernel.org>
Subject: Re: status of USB on omap35xx ?
Date: Thu, 11 Dec 2008 18:16:17 -0800	[thread overview]
Message-ID: <200812111816.17860.david-b@pacbell.net> (raw)
In-Reply-To: <6ed0b2680812111452t75b175bdr304e9b1d22ea93de@mail.gmail.com>

On Thursday 11 December 2008, Grazvydas Ignotas wrote:
> Curiously at this point I can plug/unplug to my ext hub any additional
> devices as much as I want, as long as I keep the first device plugged.
> If I unplug all devices from ext hub, I get suspend and kernel no
> longer reacts to any replugs.

Sounds like one issue might be that EHCI isn't waking up the
way it should, when it gets "remote wakeup" signaling from USB.

The USB host drivers go to some effort to put themselves in as
low a runtime power state as practical, and rely on the hardware
to wake up given events like insertion/removal of an external
device, or the downstream device issuing wakeup signaling (e.g.
press a key on a keyboard that went to sleep).

OMAP has been known to need special attention to kick in such
wakeup mechanisms.  Maybe this is another such case.

- Dave


  parent reply	other threads:[~2008-12-12  2:16 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10  0:50 status of USB on omap35xx ? Jeff Steele
2008-12-10 14:46 ` Felipe Balbi
2008-12-10 16:33   ` Jeff Steele
2008-12-10 17:40     ` Felipe Balbi
2008-12-10 18:28       ` David Brownell
2008-12-10 19:01         ` Felipe Balbi
2008-12-10 19:48           ` Pandita, Vikram
2008-12-10 23:02         ` Steve Sakoman
2008-12-11  0:57           ` Tony Lindgren
2008-12-11 10:38             ` Grazvydas Ignotas
2008-12-11 16:49               ` Paul Walmsley
2008-12-11 17:38                 ` Steve Sakoman
2008-12-11 20:41                   ` Grazvydas Ignotas
2008-12-11 21:07                     ` Paul Walmsley
2008-12-11 22:52                       ` Grazvydas Ignotas
2008-12-11 23:09                         ` Paul Walmsley
2008-12-12 20:15                           ` Grazvydas Ignotas
2008-12-12 20:33                             ` Paul Walmsley
2008-12-12 21:01                               ` Pandita, Vikram
2008-12-12 21:12                                 ` Paul Walmsley
2008-12-12 21:21                                   ` Pandita, Vikram
2008-12-21 22:25                                   ` Gadiyar, Anand
2008-12-22 12:21                                     ` Felipe Balbi
2008-12-12 20:35                             ` Steve Sakoman
2008-12-12 22:54                               ` Grazvydas Ignotas
2008-12-12  2:16                         ` David Brownell [this message]
2008-12-11 21:54                     ` Steve Sakoman
2008-12-11 22:32                       ` David Brownell
2008-12-12  1:56                       ` Tony Lindgren
2008-12-11 17:40               ` Steve Sakoman
2008-12-11 18:14                 ` Paul Walmsley
2008-12-11 18:20                   ` Pandita, Vikram

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=200812111816.17860.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=jsteele@coloradocollege.edu \
    --cc=linux-omap@vger.kernel.org \
    --cc=me@felipebalbi.com \
    --cc=notasas@gmail.com \
    --cc=paul@booyaka.com \
    --cc=sakoman@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox