From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: Adam Belay <abelay-Et1tbQHTxzrQT0dZR+AlfA@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: Mon, 14 Mar 2005 00:11:15 +0100 [thread overview]
Message-ID: <20050313231115.GA26692@elf.ucw.cz> (raw)
In-Reply-To: <1110750912.25040.12.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
On Ne 13-03-05 16:55:11, Adam Belay wrote:
> On Sun, 2005-03-13 at 22:03 +0100, Pavel Machek wrote:
> > > 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.
I meant "I do not think we want to control display brightness by
runtime suspend/resume". It may be a kernel job, but not for runtime
suspend/resume. Backlight is really individual setting as much as
power managment one. Even old monitors had brightness/contrast
buttons, even if it did not spare any energy.
> > Serial ports should not eat energy when not opened; fix it in the
> > driver.
> >
> > What other devices do eat energy?
>
> Sound cards
Yep, hw should power them down when not opened.
> bridges (PCI, PCMCIA, USB, etc.)
Agreed, bridges are interesting. Other stuff seems to be covered.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2005-03-13 23:11 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
[not found] ` <1110750912.25040.12.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-03-13 23:11 ` Pavel Machek [this message]
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=20050313231115.GA26692@elf.ucw.cz \
--to=pavel-+zi9xunit7i@public.gmane.org \
--cc=abelay-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org \
--cc=linux-pm-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=ncunningham-3EexvZdKGZRWk0Htik3J/w@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