From: Paul Sokolovsky <pmiscml@gmail.com>
To: Rodolfo Giometti <giometti@enneenne.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Advice on backlight support
Date: Wed, 21 Feb 2007 18:14:27 +0200 [thread overview]
Message-ID: <5110512908.20070221181427@gmail.com> (raw)
In-Reply-To: <20070221160213.GK4641@enneenne.com>
Hello Rodolfo,
Wednesday, February 21, 2007, 6:02:13 PM, you wrote:
> Hello,
> I'd like to add backlight support for input devices since my custom
> board has a backlighted mini keyboard.
There's already generic indicator API, currently mostly known as
"[new] LED [classdev] API", even though it is already used for things
like buzzers, vibrators, etc. Why wouldn't it be suitable for your
case?
LCD and LCD backlight are special cases, as they actually should
track state of (abstract) FB device, and keeping their states in sync
is pretty important for trivial PM and info accessibility, so worth
doing on kernel level.
As for things like "light up keyboard if key was pressed, then light
down after timeout", or "light up backlight LCD on touchscreen touch,
light down on timeout", that can be pretty well done in userspace, no?
> It could be acceptable to move the code from drivers/video/backlight/
> to drivers/backlight/ renaming the "Backlight & LCD" name into
> "Backlight" and adding two new entries "LCD" and, maybe, "Input" (or
> something like that?).
Yes, the fact that lcd.c (LCD power control) lives under backlight
dir, is a bit confusing. But they still has close relation to FB,
after all.
> Thanks in advance,
> Rodolfo
--
Best regards,
Paul mailto:pmiscml@gmail.com
next prev parent reply other threads:[~2007-02-21 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 16:02 Advice on backlight support Rodolfo Giometti
2007-02-21 16:14 ` Paul Sokolovsky [this message]
2007-02-25 10:43 ` 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=5110512908.20070221181427@gmail.com \
--to=pmiscml@gmail.com \
--cc=giometti@enneenne.com \
--cc=linux-kernel@vger.kernel.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