public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-acpi@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: brightness control on thinkpad t61p
Date: Tue, 8 Jan 2008 10:06:53 -0200	[thread overview]
Message-ID: <20080108120653.GA23216@khazad-dum.debian.net> (raw)
In-Reply-To: <20080108004559.GA27177@srcf.ucam.org>

On Tue, 08 Jan 2008, Matthew Garrett wrote:
> On Mon, Jan 07, 2008 at 10:32:46PM -0200, Henrique de Moraes Holschuh wrote:
> 
> > Should we?  Why?  We lose information doing that.  Instead of a nice linear
> > 0-100% brightness scale, you are now back to an 8 or 16-level non-linear
> > brightness scale.
> 
> The spec makes no guarantees about what that 0-100 range means - it may 
> be brightness, power consumption or bonghits. It's really not guaranteed 
> to be meaningful, and the backlight class doesn't provide that guarantee 
> either.

True.  But it is still a step backwards for firmware that do better.

And, frankly, the backlight class is so spartan, I don't consider missing
features in it anything but a "time to fix it" issue.  It is just like the
LED class, it is too spartan to actually do all we need it to in some cases.

Is there a *real* technical reason why we can't just round to the nearest?
That will work well with any firmware, and it will not remove functionality
from any box, while at the same time plugging the current issues nicely.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  reply	other threads:[~2008-01-08 12:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-23  8:00 brightness control on thinkpad t61p Andrew Morton
2007-12-23 12:16 ` Rafael J. Wysocki
2007-12-24  7:34 ` Matthew Garrett
2007-12-24 17:14   ` Henrique de Moraes Holschuh
2007-12-26 22:10   ` Andrew Morton
2007-12-26 22:23     ` Matthew Garrett
2007-12-27 12:33       ` Henrique de Moraes Holschuh
2008-01-07  1:36         ` Henrique de Moraes Holschuh
2008-01-07 19:48           ` Matthew Garrett
2008-01-08  0:32             ` Henrique de Moraes Holschuh
2008-01-08  0:45               ` Matthew Garrett
2008-01-08 12:06                 ` Henrique de Moraes Holschuh [this message]
2008-01-08 12:18                   ` Matthew Garrett
2008-01-08 12:48                     ` Henrique de Moraes Holschuh
2008-01-08 15:17                       ` Matthew Garrett
2008-01-08 15:45                       ` Richard Purdie
2008-01-08 15:54                         ` Matthew Garrett
2008-01-08 16:29                           ` Richard Purdie
2008-01-08 16:49                             ` Henrique de Moraes Holschuh
2008-01-08 16:56                               ` Richard Purdie
2008-01-08 17:36                                 ` Henrique de Moraes Holschuh
2007-12-27 12:31     ` Henrique de Moraes Holschuh
2007-12-24 17:08 ` Henrique de Moraes Holschuh
2007-12-26 22:10   ` Andrew Morton
2007-12-27 13:15     ` Henrique de Moraes Holschuh

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=20080108120653.GA23216@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=akpm@linux-foundation.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=rjw@sisk.pl \
    /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