From: Andrew Zabolotny <zap@homelink.ru>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: adaplas@gmail.com, linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: RFC: Backlight Class sysfs attribute behaviour
Date: Tue, 7 Mar 2006 00:07:18 +0300 [thread overview]
Message-ID: <20060307000718.0e8b8be3.zap@homelink.ru> (raw)
In-Reply-To: <1141634729.6524.14.camel@localhost.localdomain>
On Mon, 06 Mar 2006 08:45:28 +0000
Richard Purdie <rpurdie@rpsys.net> wrote:
> * the user supplied power sysfs attribute
> * the user supplied brightness sysfs attribute
> * the current FB blanking state
> * any other driver specific factors
As far I see the only real concern here is the console blanking. So why
not make it just another device state flag, which doesn't influence the
'power' attribute and which isn't visible from user space (what for?).
And the 'real' power state will be computed as "blank && power"
attributes. The entire logic could be hidden in backlight.c so that no
driver will have to be modified for this. Maybe a 'hw_power' or such
would be needed to see the 'real' hardware state (and possibly
modify, if you really really want to).
Is there any need for a broader-range solution here?
--
Greetings,
Andrew
next prev parent reply other threads:[~2006-03-06 21:07 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 [this message]
2006-03-06 23:05 ` Richard Purdie
2006-03-08 9:48 ` Andrew Zabolotny
2006-03-06 21:44 ` Pavel Machek
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=20060307000718.0e8b8be3.zap@homelink.ru \
--to=zap@homelink.ru \
--cc=adaplas@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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).