23 Mar, 2011

1 commit

  • There may be multiple ways of controlling the backlight on a given
    machine. Allow drivers to expose the type of interface they are
    providing, making it possible for userspace to make appropriate policy
    decisions.

    Signed-off-by: Matthew Garrett
    Cc: Richard Purdie
    Cc: Chris Wilson
    Cc: David Airlie
    Cc: Alex Deucher
    Cc: Ben Skeggs
    Cc: Zhang Rui
    Cc: Len Brown
    Cc: Jesse Barnes
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Matthew Garrett
     

17 Mar, 2010

3 commits


16 Dec, 2009

1 commit


22 Sep, 2009

1 commit

  • Certain hardware will send us events when the backlight brightness
    changes. Add a function to update the value in the core, and
    additionally send a uevent so that userspace can pop up appropriate
    UI. The uevents are flagged depending on whether the update originated
    in the kernel or from userspace, making it easier to only display UI
    at the appropriate time.

    Signed-off-by: Matthew Garrett
    Signed-off-by: Richard Purdie

    Matthew Garrett
     

08 Jan, 2009

1 commit


12 Oct, 2007

1 commit


16 Jul, 2007

1 commit

  • Convert the backlight and LCD classes from struct class_device
    to struct device since class_device is scheduled for removal.

    One nasty API break is the backlight power attribute has had to be
    renamed to bl_power and the LCD power attribute has had to be renamed
    to lcd_power since the original names clash with the core. I can't see
    a way around this.

    Signed-off-by: Richard Purdie
    Acked-by: Greg Kroah-Hartman

    Richard Purdie
     

20 Feb, 2007

4 commits

  • Per device data such as brightness belongs to the indivdual device
    and should therefore be separate from the the backlight operation
    function pointers. This patch splits the two types of data and
    allows simplifcation of some code.

    Signed-off-by: Richard Purdie

    Richard Purdie
     
  • Convert internal semaphore to a mutex

    Signed-off-by: Richard Purdie

    Richard Purdie
     
  • backlight_device->sem has a very specific use as documented in the
    header file. The external users of this are using it for a different
    reason, to serialise access to the update_status() method.

    backlight users were supposed to implement their own internal
    serialisation of update_status() if needed but everyone is doing
    things differently and incorrectly. Therefore add a global mutex to
    take care of serialisation for everyone, once and for all.

    Locking for get_brightness remains optional since most users don't
    need it.

    Also update the lcd class in a similar way.

    Signed-off-by: Richard Purdie

    Richard Purdie
     
  • Remove uneeded owner field from backlight_properties structure.

    Nothing uses it and it is unlikely that it will ever be used. The
    backlight class uses other means to ensure that nothing references
    unloaded code.

    Based on a patch from Dmitry Torokhov

    Signed-off-by: Richard Purdie

    Richard Purdie
     

20 Dec, 2006

1 commit

  • This patch set adds generic abstract layer support for acpi video driver to
    have generic user interface to control backlight and output switch control by
    leveraging the existing backlight sysfs class driver, and by adding a new
    video output sysfs class driver.

    This patch:

    Add dev argument for backlight_device_register to link the class device to
    real device object. The platform specific driver should find a way to get the
    real device object for their video device.

    [akpm@osdl.org: build fix]
    [akpm@osdl.org: fix msi-laptop.c]
    Signed-off-by: Luming Yu
    Cc: "Antonino A. Daplas"
    Cc: Greg KH
    Signed-off-by: Andrew Morton
    Signed-off-by: Len Brown

    Yu Luming
     

01 Apr, 2006

1 commit

  • Backlight class attributes are currently easy to implement incorrectly.
    Moving certain handling into the backlight core prevents this whilst at the
    same time makes the drivers simpler and consistent. The following changes are
    included:

    The brightness attribute only sets and reads the brightness variable in the
    backlight_properties structure.

    The power attribute only sets and reads the power variable in the
    backlight_properties structure.

    Any framebuffer blanking events change a variable fb_blank in the
    backlight_properties structure.

    The backlight driver has only two functions to implement. One function is
    called when any of the above properties change (to update the backlight
    brightness), the second is called to return the current backlight brightness
    value. A new attribute "actual_brightness" is added to return this brightness
    as determined by the driver having combined all the above factors (and any
    driver/device specific factors).

    Additionally, the backlight core takes care of checking the maximum brightness
    is not exceeded and of turning off the backlight before device removal.

    The corgi backlight driver is updated to reflect these changes.

    Signed-off-by: Richard Purdie
    Signed-off-by: Antonino Daplas
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Richard Purdie
     

17 Apr, 2005

1 commit

  • Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds