From: Adam Belay <abelay-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
To: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
Cc: Linux-pm mailing list
<linux-pm-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
Nigel Cunningham
<ncunningham-3EexvZdKGZRWk0Htik3J/w@public.gmane.org>
Subject: Re: Devices eating too much power [was Re: Some thoughts on suspend/resume development]
Date: Sun, 13 Mar 2005 16:55:11 -0500 [thread overview]
Message-ID: <1110750912.25040.12.camel@localhost.localdomain> (raw)
In-Reply-To: <20050313210322.GA7016-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2311 bytes --]
On Sun, 2005-03-13 at 22:03 +0100, Pavel Machek wrote:
> Hi!
>
> > > > > What devices is this targetted at? Video should be handled
> > > > > already (or perhaps we want to power down graphics card when screen is
> > > > > blanked?). Disks spin down too. IRDA ports?
> > > >
> > > > - Video
> > >
> > > X/dpms handles these already.
> >
> > Many GPUs will have frequency scaling like processors (e.g. ATI
> > Powerplay). I don't think we currently support this.
>
> Ugh, I did not know about this stuff. Ok.. Anyway that's X problem,
> right?
Well it is now :), but many components of these X drivers should be in
the kernel. (e.g. X does its own pci probing)
>
> > Also we don't really control display brightness.
>
> But display brightness does not really belong here, right?
No, in some cases it's controlled by a separate ACPI device.
>
> > > > Anything you might care to imagine :>
> > >
> > > Well, I meant something that is not already handled. Like... what
> > > power-hungry device do we fail to properly handle today?
> >
> > Wireless cards could be turned off when plugged into a physical media.
> > Many other devices remain on when not used (e.g. serial ports).
> > Probably most of them don't take up much power, but it would be nice to
> > do some experimentation and see.
>
> I do not think wireless can be turned off when physical media is
> present... but it makes sense to be user option... called ifconfig
> wlan0 down. Driver should really power it down on ifconfig down.
Fair enough. In the typical laptop, it may be a good idea though.
>
> Serial ports should not eat energy when not opened; fix it in the
> driver.
>
> What other devices do eat energy?
Sound cards
bridges (PCI, PCMCIA, USB, etc.)
> > I think this question really depends on architecture and hardware.
> > Also, I think we'll see more power management options available to us in
> > the near future.
>
> Designing for hardware not yet available is usually bad idea.
Well, not always. For example there are PCI express specs available, so
even though not every device uses the new power management capabilities
now, we know what to expect and exactly how it will work.
Another example... ACPI spec 3.0 defines a mechanism to throttle the
performance of devices other than processors.
Adam
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2005-03-13 21:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44L0.0503091111470.1117-100000@ida.rowland.org>
[not found] ` <1110403931.8870.6.camel@desktop.cunningham.myip.net.au>
[not found] ` <20050309214416.GG17034@elf.ucw.cz>
[not found] ` <1110405336.8870.22.camel@desktop.cunningham.myip.net.au>
[not found] ` <1110405336.8870.22.camel-r49W/1Cwd2ff0s6lnCXPX/uOuaPYTxhvJwvTLr3MMZM@public.gmane.org>
2005-03-13 18:14 ` Devices eating too much power [was Re: Some thoughts on suspend/resume development] Pavel Machek
[not found] ` <20050313181455.GD1579-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-03-13 19:36 ` Adam Belay
[not found] ` <1110742612.12485.287.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-03-13 21:03 ` Pavel Machek
[not found] ` <20050313210322.GA7016-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-03-13 21:55 ` Adam Belay [this message]
[not found] ` <1110750912.25040.12.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-03-13 23:11 ` Pavel Machek
2005-03-21 12:08 ` Arioch
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=1110750912.25040.12.camel@localhost.localdomain \
--to=abelay-et1tbqhtxzrqt0dzr+alfa@public.gmane.org \
--cc=linux-pm-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=ncunningham-3EexvZdKGZRWk0Htik3J/w@public.gmane.org \
--cc=pavel-+ZI9xUNit7I@public.gmane.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