From: Pavel Machek <pavel@ucw.cz>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: kernel list <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>,
Linux usb mailing list <linux-usb-devel@lists.sourceforge.net>
Subject: Re: [linux-usb-devel] usb still sucks battery in -rc7-mm1
Date: Sun, 24 Sep 2006 23:05:27 +0200 [thread overview]
Message-ID: <20060924210527.GG1873@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0609241647230.14008-100000@netrider.rowland.org>
Hi!
> > I made some quick experiments, and usb still eats 4W of battery
> > power. (With whole machine eating 9W, that's kind of a big deal)...
> >
> > This particular machine has usb bluetooth, but it can be disabled by
> > firmware, and appears unplugged. (I did that). It also has fingerprint
> > scanner, that can't be disabled, but that does not have driver (only
> > driven by useland, and was unused in this experiment).
> >
> > Any ideas?
>
> The USB autosuspend patches are still not entirely in -mm. They contain a
> couple of bugs that have to get fixed first. When they do get merged you
> should see considerable improvement. Note that although they will reduce
> the amount of power being used by the USB controllers and will stop the
> DMA activity (thus allowing your CPU to enter C2), they won't put the
> controllers into D3. For that you'll have to get PCI autosuspend...
> :-)
I have not measured that, but I _hope_ drain by controller itself will
not be big enough.
> In the meantime, if all you care about is power consumption there are
> some things you can do. The easiest is simply to rmmod ehci-hcd,
> ohci-hcd, and uhci-hcd. After all, if you're not using USB there's no
> reason to let the drivers eat up memory, CPU time, and power.
Are autosuspend patches available somewhere? (Relative to -mm, or
relative to 2.6.18?) I'd like to play with them...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2006-09-24 21:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 9:08 Pavel Machek
2006-09-24 12:18 ` [linux-usb-devel] " Theodoros V. Kalamatianos
2006-09-24 20:20 ` Pavel Machek
2006-09-27 22:46 ` David Brownell
2006-09-24 14:49 ` Alexander Gran
2006-09-24 16:21 ` Pavel Machek
2006-09-24 20:54 ` [linux-usb-devel] " Alan Stern
2006-09-24 21:05 ` Pavel Machek [this message]
2006-09-24 21:13 ` Alan Stern
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=20060924210527.GG1873@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--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
all inboxes | Powered by JetHome®