public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Greg KH <gregkh@suse.de>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net,
	Alan Stern <stern@rowland.harvard.edu>,
	Oliver Neukum <oneukum@suse.de>
Subject: Re: [GIT PATCH] USB autosuspend fixes for 2.6.23-rc6
Date: Thu, 13 Sep 2007 16:52:07 +0200	[thread overview]
Message-ID: <20070913145207.GF3563@stusta.de> (raw)
In-Reply-To: <20070913133321.GA6362@kroah.com>

On Thu, Sep 13, 2007 at 06:33:21AM -0700, Greg KH wrote:
> It turns out that USB devices suck when it comes to powermanagement
> issues :(
> 
> A number of patches have been submitted near the end of this kernel
> release cycle that add new device ids to the quirk table in the kernel
> to disable autosuspend for specific devices.  However, a number of
> developers are very worried that even with the testing that has been
> done, once 2.6.23 is released, we are going to get a whole raft of angry
> users when their devices break in nasty ways.
> 
> As an example, it seems that almost 2/3 of all USB printers just can not
> handle autosuspend.  And there's a _lot_ of USB printers out there...
> 
> When researching how other operating systems handle this, it was found
> out that they use a whitelist of devices that are able to properly
> suspend.  So, in the future, that is how we are going to handle this.
> 
> These two patches address the need today to have users machines still
> work, even if they might draw more power than they possibly could (which
> is not any more than they did in 2.6.22.)
> 
> These patches do two things:
>   - disable USB autosuspend on all devices except for USB hubs.  This
>     can be easily overridden by userspace to turn on autosuspend for
>     devices that a user wants to.  HAL will use a whitelist in the
>     future for these types of devices.
>...

Not related to the patch for 2.6.23, but I have a gut feeling that 
something might be done the wrong way later:

If I understand you correctly, you are saying that I will have to 
install HAL for getting a whitelist for in-kernel functionality?

It is a good thing if userspace can add currently missing devices to
whitelists, but the whitelist itself should be in the kernel.

> thanks,
> 
> greg k-h
>...

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2007-09-13 14:52 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13 13:33 [GIT PATCH] USB autosuspend fixes for 2.6.23-rc6 Greg KH
2007-09-13 14:52 ` Adrian Bunk [this message]
2007-09-13 15:20   ` Alan Stern
2007-09-13 15:40     ` Adrian Bunk
2007-09-13 16:07       ` Alan Stern
2007-09-13 16:34         ` Greg KH
2007-09-13 16:43         ` Linus Torvalds
2007-09-13 19:13           ` Alan Stern
2007-09-14  0:24             ` Matthew Dharm
2007-09-14 14:34               ` Alan Stern
2007-09-14  8:55             ` Jiri Kosina
2007-09-14  9:59               ` Greg KH
2007-09-13 19:26           ` Pete Zaitcev
2007-09-13 20:19         ` Adrian Bunk
2007-09-13 20:31           ` Alan Stern
2007-09-13 20:44           ` Linus Torvalds
2007-09-13 21:28             ` Adrian Bunk
2007-09-13 22:05               ` Adrian Bunk
2007-09-14  0:11                 ` Linus Torvalds
2007-09-14 13:21                   ` Mark Lord
2007-09-14 14:15                     ` Adrian Bunk
2007-09-14 14:29                 ` Alan Stern
2007-09-14 14:26               ` Alan Stern
  -- strict thread matches above, loose matches on Subject: below --
2007-09-17 12:56 Hans de Goede
2007-09-18 10:39 Joerg Schilling

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=20070913145207.GF3563@stusta.de \
    --to=bunk@kernel.org \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=oneukum@suse.de \
    --cc=stern@rowland.harvard.edu \
    --cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox