public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-pm@lists.osdl.org
Subject: usb suspend (was Re:  So, what's the status on the recent patches here?)
Date: Sun, 27 Aug 2006 01:34:08 +0200	[thread overview]
Message-ID: <20060826233408.GE2551@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0608252215340.32136-100000@netrider.rowland.org>

Hi!

> > > The idea of the patches is that they will autosuspend a USB hub when it
> > > has no active (i.e., unsuspended) children, and autosuspending a root hub
> > > stops the USB controller from doing DMA.  However, non-hub devices are not
> > > yet automatically suspended, so you will have to suspend the fingerprint
> > > scanner by hand.
> > 
> > That is okay, I can do that. It saves 2 hours of battery life on my
> > machine...
> 
> Come to think of it, you don't need the autosuspend patches to turn these 
> devices off.  You can do it right now with your existing kernel, although 
> it's a little easier with -mm.  (The reason is that -mm contains a 
> development patch which ties a USB device's interfaces to the device 
> itself; suspending the device will automatically suspend all its 
> interfaces, and likewise resuming the device will automatically resume all 
> its interfaces.  With a vanilla kernel you must manually suspend the 
> interfaces before you can suspend the device and manually resume them 
> after resuming the device.)
> 
> Anyway, you can use the deprecated 
> 
> 	echo -n 2 >/sys/devices/.../power/state
> 
> mechanism to suspend all the USB interfaces, devices, and controllers you 
> want -- provided you work your way up from the bottom of the device tree.  
> The autosuspend patch just makes it simpler, since it takes care of 
> suspending and resuming all the hubs for you.

Thanks! That works great and gets my power consumption into reasonable
range.. plus allows fan to actually stop.
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      reply	other threads:[~2006-08-26 23:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-25 20:22 So, what's the status on the recent patches here? Woodruff, Richard
2006-08-25 20:34 ` Alan Stern
2006-08-25 21:27   ` Pavel Machek
2006-08-25 21:46     ` Alan Stern
2006-08-25 22:03       ` Pavel Machek
2006-08-26  2:21         ` Alan Stern
2006-08-26 23:34           ` Pavel Machek [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=20060826233408.GE2551@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-pm@lists.osdl.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