linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: Richard Purdie <rpurdie@rpsys.net>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	Andrew Zabolotny <zap@homelink.ru>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: RFC: Backlight Class sysfs attribute behaviour
Date: Mon, 6 Mar 2006 22:44:26 +0100	[thread overview]
Message-ID: <20060306214426.GA4701@elf.ucw.cz> (raw)
In-Reply-To: <440B89AB.3020203@gmail.com>

On Po 06-03-06 09:00:27, Antonino A. Daplas wrote:
> Richard Purdie wrote:
> > At present, the backlight class presents two attributes to sysfs,
> > brightness and power. I'm a little confused as to whether these
> > attributes are currently doing the right things.
> > 
> > Taking brightness, at any one time we have several different brightness
> > values:
> > 
> > * User requested brightness (echo y > /sys/class/backlight/xxx/brightness)
> > * Driver determined brightness which accounts for things like FB 
> >   blanking, low battery backlight limiting (an example from corgi_bl), 
> >   user requested power state, device suspend/resume.
> > 
> > The solution might be to have brightness always return the user
> > requested value y and have a new attribute returning the brightness as
> > determined by the driver once it accounts for all the factors it needs
> > to consider. Naming of such an attribute is tricky - "driver_brightness"
> > perthaps?
> 
> Why not just agree on a normal range of values (ie, 0-255), and let the
> driver "denormalize" them?  Thus, a driver that has only 2 levels of
> brightness, will treat 0-127 as 0 and 128-255 as 1, and will return only
> two possible values 0 and 255.

Does not work... how do you set minimum brightness with backlight on
(so that text is visible)?
								Pavel
-- 
Web maintainer for suspend.sf.net (www.sf.net/projects/suspend) wanted...

      parent reply	other threads:[~2006-03-06 21:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-05 15:08 RFC: Backlight Class sysfs attribute behaviour Richard Purdie
2006-03-05 22:09 ` Andrew Zabolotny
2006-03-06  0:08   ` Richard Purdie
2006-03-06 21:47     ` Pavel Machek
2006-03-06  1:00 ` Antonino A. Daplas
2006-03-06  8:45   ` Richard Purdie
2006-03-06 21:07     ` Andrew Zabolotny
2006-03-06 23:05       ` Richard Purdie
2006-03-08  9:48         ` Andrew Zabolotny
2006-03-06 21:44   ` Pavel Machek [this message]

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=20060306214426.GA4701@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=adaplas@gmail.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    --cc=zap@homelink.ru \
    /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;
as well as URLs for NNTP newsgroup(s).