From: "Richard Purdie" <rpurdie@rpsys.net>
To: adaplas@pol.net, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: FB_EVENT (blank and unblank?)
Date: Sun, 28 Nov 2004 00:59:02 -0000 [thread overview]
Message-ID: <02cc01c4d4e5$75e4e170$0f01a8c0@max> (raw)
In-Reply-To: 200411280824.01338.adaplas@hotpop.com
Antonino A. Daplas:
>> My Issue: I have a backlight driver that shares no code with the
>> framebuffer driver - the hardware is totally separate. I have there
>> written
>> them as two spate drivers which seems to make sense. The problem is that
>> there is no method to communicate blanking to the external backlight
>> driver
>> (which is all it needs to know about). Obviously I can add links between
>
> Of course there is. Your backlight driver does a
> register_backlight_controllers(). Then your fb driver does a
> set_backlight_enable(!blank) in its xxxfb_blank implementation.
Yes, you could do that. I was trying to look for a method than meant no
specific action by the framebuffer driver was required. It shouldn't have to
care if a backlight is present or not...
On the other hand, the console system shouldn't have to either. Hence the
suggestion that blank and unblank events are added. It may be there's a
layer of backlight glue added to the drivers/video directory
drivers/video/backlight? that catches those events and calls
set_backlight_enable(!blank) and provides functions like
register_backlight_controllers().
>> The Other Issue: There is no common method to access and control
>> backlight
>
> Not yet, but if the powermac backlight support is extended, then we
> suddenly
> have a common method. Right now, pmac's backlight support has this as
> exportable symbols:
>
> set_backlight_enable()
> get_backlight_enable()
> set_backlight_level()
> get_backlight_level()
>
> And all of the above calls specific hooks to the backlight driver.
I agree that would go part of the way towards a common method (the other
part being a sysfs representation or similar). That sysfs representation
could even be provided by backlight "core" in drivers/video/backlight?.
> We don't have a common architecture yet for backlight control, and I don't
> know where this is really going. Anyone here have more info?
I'd be interested to know the current position...
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 prev parent reply other threads:[~2004-11-28 0:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 17:04 Default timings in vga16fb driver Martin Wilck
2004-11-24 16:16 ` Antonino A. Daplas
2004-11-25 14:55 ` Martin Wilck
2004-11-25 19:51 ` Antonino A. Daplas
2004-11-26 9:11 ` Geert Uytterhoeven
2004-11-27 14:53 ` FB_EVENT (blank and unblank?) Richard Purdie
2004-11-27 22:43 ` Antonino A. Daplas
2004-11-27 23:59 ` Richard Purdie
2004-11-28 0:24 ` Antonino A. Daplas
2004-11-28 0:59 ` Richard Purdie [this message]
2004-11-28 1:14 ` Antonino A. Daplas
2004-11-29 22:36 ` fbdev: Add FB_EVENT_BLANK to notify listeners of a blanking status change Richard Purdie
2004-11-29 23:29 ` Antonino A. Daplas
2004-11-29 10:53 ` cursor color changes ramprasad
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='02cc01c4d4e5$75e4e170$0f01a8c0@max' \
--to=rpurdie@rpsys.net \
--cc=adaplas@pol.net \
--cc=linux-fbdev-devel@lists.sourceforge.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).