From: Pavel Machek <pavel@ucw.cz>
To: david@lang.hm
Cc: Arjan van de Ven <arjan@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-pm <linux-pm@lists.linux-foundation.org>
Subject: Re: Power Management framework proposal
Date: Fri, 27 Jul 2007 11:46:38 +0000 [thread overview]
Message-ID: <20070727114637.GC11895@ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.64.0707222105310.6350@asgard.lang.hm>
Hi!
> >>example 1: a laptop screen
> >>
> >>mode capacity power description
> >>0 0 0 off
> >>1 100 100 full brightness
> >>2 70 60 half power to the backlight
> >>3 50 35 quarter power to the backlight
> >>4 30 25 eighth power to the backlight
> >>5 5 10 backlight off.
> >>
> >>example 2: a front-panel display on a server (no
> >>variable backlight
> >>control)
> >>
> >>mode capacity power description
> >>0 0 0 off
> >>1 100 100 backlight on
> >>2 50 10 backlight off
> >
> >
> >the problem is: the person who SETS these needs to know
> >what they mean.
>
> that's what the description is for. this info can be
> provided by the driver as part of the list_modes()
> function.
That's what /sys/class/backlight/ is for :-).
> >as someone who wrote (part of) a power policy manager;
> >sorry but you
> >take away information I need, and in addition the
> >different API's are
> >absolutely no big deal.
>
> assuming that nobody else chimes in to disagree with you
> I'll accept your judgement and drop the issue.
Just for the record, I agree with Arjan here.
--
(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:[~2007-07-27 18:09 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 6:49 david
2007-07-22 7:57 ` [linux-pm] " Igor Stoppa
2007-07-22 8:58 ` david
2007-07-22 12:05 ` Igor Stoppa
2007-07-22 21:21 ` david
2007-07-22 23:09 ` Arjan van de Ven
2007-07-23 2:45 ` david
2007-07-23 3:50 ` Arjan van de Ven
2007-07-23 4:04 ` david
2007-07-23 4:19 ` Arjan van de Ven
2007-07-23 5:25 ` david
2007-07-23 14:12 ` Arjan van de Ven
2007-07-23 18:19 ` david
2007-07-23 8:56 ` Ondrej Zajicek
2007-07-23 17:33 ` david
2007-07-27 12:04 ` Pavel Machek
2007-07-23 10:48 ` Igor Stoppa
2007-07-23 18:14 ` david
2007-07-24 8:43 ` Jerome Glisse
2007-07-24 14:18 ` Igor Stoppa
2007-07-24 20:13 ` david
2007-07-24 20:06 ` david
2007-07-24 23:14 ` Jerome Glisse
2007-07-25 0:40 ` david
2007-07-25 12:49 ` Jerome Glisse
2007-07-29 21:56 ` david
2007-07-22 17:26 ` Arjan van de Ven
2007-07-22 18:56 ` david
2007-07-22 22:27 ` Arjan van de Ven
2007-07-23 3:51 ` david
2007-07-23 4:00 ` Arjan van de Ven
2007-07-23 4:09 ` david
2007-07-27 11:46 ` Pavel Machek [this message]
2007-07-29 22:00 ` david
2007-07-30 1:05 ` Matthew Garrett
2007-07-23 22:23 ` Benjamin Herrenschmidt
2007-07-24 20:14 ` david
2007-07-24 21:38 ` Benjamin Herrenschmidt
2007-07-24 23:02 ` david
2007-07-24 23:47 ` Benjamin Herrenschmidt
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=20070727114637.GC11895@ucw.cz \
--to=pavel@ucw.cz \
--cc=arjan@infradead.org \
--cc=david@lang.hm \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.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
all inboxes | Powered by JetHome®