From: "Richard Purdie" <rpurdie@rpsys.net>
To: Russ Dill <russ.dill@gmail.com>,
Steven Scholz <steven.scholz@imc-berlin.de>,
John Lenz <lenz@cs.wisc.edu>,
zap@homelink.ru
Cc: linux-arm-kernel@lists.arm.linux.org.uk,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Backlight support
Date: Tue, 30 Nov 2004 16:28:26 -0000 [thread overview]
Message-ID: <017c01c4d6f9$a34fc010$0f01a8c0@max> (raw)
In-Reply-To: f9d2a5e104112916252c253a2b@mail.gmail.com
John Lenz:
> Perhaps the patch being referred to is the "Backlight and LCD module
> patches" that Andrew Zabolotny and I proposed on lkml?
I think the above patch was nearly there. The issues seemed to be with the
method of associating framebuffer devices with their backlights. I've come
up with a solution to that problem (see below) so that code can be removed
from that patch and that should make it acceptable for mainstream kernel
inclusion.
Russ Dill:
> The driver/bus/device model driver? Probably just no one there with
> the time to spend on it. It be a real help, and would be a good use of
> sysfs (for changing contrast, getting info, etc).
I'm keen to get this sorted out and I agree its an ideal use of sysfs. I'm
still getting up to speed on sysfs though...
Steven Scholz:
> Where can I find the most recent version of your patch?
I've had a discussion with Andrew. I think he's going to find the latest
version of the and post it for inclusion without the problematic parts...
Andrew?
> Excuse me ignorance, but what is "frontlight"?
I think a frontlight shines onto the display and reflects off a reflector at
the back of the LCD. A backlight lights it from the rear. As far as the
sysfs representations go, they'll be essentially identical. You can read a
frontlit display without the light in strong light. The backlit display
always needs the backlight.
My solution for associating backlight drivers with framebuffer drivers is
for the backlight driver to call fb_register_client() and register for fb
events. You can then intercept blanking requests (FB_EVENT_BLANK) which get
passed with an fb_info struct and the new blanking setting. It's entirely up
to the backlight driver how it tells which displays it should be blanking.
For something like my PDA, there is only one framebuffer/LCD to blank but in
other cases you would analyse fb_info. (FB_EVENT_BLANK is destined for
2.6.11)
I propose this discussion should move to linux-fbdev-devel and hopefully
Andrew will provide a sysfs representation we can discuss (maybe with some
comments from lkml).
I have one implementation question though - should backlight drivers be in
the arch folder (arch/arm/mach-pxa in my case) or should
drivers/video/backlights be created? They're all likely to be using
fb_register_client() so maybe the latter would be preferred?
Richard
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next parent reply other threads:[~2004-11-30 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <40ED4FAC.70406@ticino.com>
[not found] ` <1089274696.4740.3.camel@localhost>
[not found] ` <41AB2E71.8080809@imc-berlin.de>
[not found] ` <f9d2a5e104112916252c253a2b@mail.gmail.com>
2004-11-30 16:28 ` Richard Purdie [this message]
2004-11-30 16:44 ` Backlight support Nicolas Pitre
2004-11-30 22:40 ` Russ Dill
2004-12-01 22:34 ` Andrew Zabolotny
2004-12-02 11:08 ` Antonino A. Daplas
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='017c01c4d6f9$a34fc010$0f01a8c0@max' \
--to=rpurdie@rpsys.net \
--cc=lenz@cs.wisc.edu \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=russ.dill@gmail.com \
--cc=steven.scholz@imc-berlin.de \
--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).