linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Richard Purdie <rpurdie@rpsys.net>,
	adaplas@pol.net, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: FB_EVENT (blank and unblank?)
Date: Sun, 28 Nov 2004 08:24:00 +0800	[thread overview]
Message-ID: <200411280824.01338.adaplas@hotpop.com> (raw)
In-Reply-To: <027d01c4d4dd$19fe65a0$0f01a8c0@max>

On Sunday 28 November 2004 07:59, Richard Purdie wrote:
> Antonino A. Daplas:
> > On Saturday 27 November 2004 22:53, Richard Purdie wrote:
> >> I have two places where they need to talk. The first is for the touch
> >> screen to query the x resolution (and to know if the screen is
> >> blanked)[1].
> >> The second is to turn the backlight off when the console is blanked.
> >
> > Can you adopt the backlight support infrastructure in powermacs?  See
> > arch/ppc/platforms/pmac_backlight.c  Currently, it's PPC-specific, but it
> > can be extended to other platforms.  A few drivers use this, rivafb is
> > one of
> > them (drivers/video/fbdev.c), and aty.
>
> There are two issues here and this addresses the wrong one.
>
> 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.

> them but I feel that's ugly. Adding a couple of extra events to the
> fb_register_client system would be much neater.
>
> 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.

> levels within the kernel. My feeling on this is that they should appear in
> sysfs as their own class. I need to look into this as I know there has been
> discussion in the past and I don't know what the issues are. I'd welcome
> any comments on this though.

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?

Tony





-------------------------------------------------------
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/

  reply	other threads:[~2004-11-28  0:24 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 [this message]
2004-11-28  0:59                 ` Richard Purdie
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=200411280824.01338.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=adaplas@pol.net \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --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).