public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alan Stern <stern@rowland.harvard.edu>,
	David Brownell <david-b@pacbell.net>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: USB rejecting sleep
Date: Mon, 19 Dec 2005 07:27:21 +1100	[thread overview]
Message-ID: <1134937642.6102.85.camel@gaston> (raw)

Hi David, Alan !

What exactly changed in the recent USB stacks that is causing it to
abort system suspend much more often ? I'm getting lots of user reports
with 2.6.15-rc5 saying that they can't put their internal laptops to
sleep, apparently because a driver doesn't have a suspend method
(internal bluetooth in this case).

It's never been mandatory so far for all drivers of all connected
devices to have a suspend method... didn't we decide back then that
disconneting those was the right way to go ?

Any reason we are rejecting the sleep process for these currently ? A
locking issue that makes disconnecting not yet feasible ? What changed
from the previous version where that worked ?

Cheers,
Ben.


             reply	other threads:[~2005-12-18 20:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-18 20:27 Benjamin Herrenschmidt [this message]
2005-12-18 20:58 ` USB rejecting sleep David Brownell
2005-12-18 21:01   ` Benjamin Herrenschmidt
2005-12-18 22:07     ` Marcel Holtmann
2005-12-18 23:11   ` Alan Stern
2005-12-18 21:50 ` Greg KH
2005-12-18 22:13   ` Benjamin Herrenschmidt
2005-12-18 22:25     ` Greg KH
2005-12-18 23:16       ` Benjamin Herrenschmidt
2005-12-19  2:51       ` Benjamin Herrenschmidt
2005-12-19  3:11         ` Alan Stern
2005-12-19  3:24           ` Benjamin Herrenschmidt
2005-12-19 14:45             ` Alan Stern
2005-12-22 16:02   ` Pavel Machek
2005-12-27  4:19     ` Greg KH

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=1134937642.6102.85.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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