Re: FB_EVENT (blank and unblank?)

["Antonino A. Daplas" <adaplas@hotpop.com>]

On Sunday 28 November 2004 08:59, Richard Purdie wrote:
> 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...

Ah, when you explained it like that, then it does sound very reasonable.
Okay, I think that can be added.  I think we will need only 1 event
FB_EVENT_BLANK, then in fb_event.data, the blanking level.

We can do it similarly with the mode switch event, differentiate if the
request is coming from userspace or the kernel.

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/