1. 20 Aug, 2014 1 commit
  2. 18 Jul, 2014 1 commit
  3. 23 Jun, 2014 1 commit
  4. 21 May, 2014 1 commit
  5. 07 May, 2014 1 commit
    • Alexandre Courbot's avatar
      pwm-backlight: switch to gpiod interface · 257462db
      Alexandre Courbot authored
      Switch to the new gpiod interface, which allows to handle GPIO
      properties such as active low transparently and removes a whole bunch of
      There are still a couple of users of this driver that rely on passing
      the enable GPIO number through platform data, so a fallback mechanism
      using a GPIO number is still available to avoid breaking them. It will
      be removed once current users have switched to the GPIO lookup tables
      provided by the gpiod interface.
      Signed-off-by: default avatarAlexandre Courbot <acourbot@nvidia.com>
      Signed-off-by: default avatarThierry Reding <thierry.reding@gmail.com>
  6. 02 May, 2014 1 commit
  7. 17 Dec, 2013 1 commit
  8. 13 Nov, 2013 1 commit
  9. 22 Oct, 2013 2 commits
  10. 18 Oct, 2013 1 commit
  11. 16 Oct, 2013 6 commits
  12. 08 Mar, 2013 1 commit
  13. 22 Feb, 2013 1 commit
  14. 31 Jan, 2013 1 commit
  15. 30 Jan, 2013 1 commit
  16. 05 Oct, 2012 1 commit
  17. 23 Jul, 2012 2 commits
  18. 23 Mar, 2012 1 commit
  19. 11 Jan, 2012 2 commits
  20. 25 Aug, 2011 1 commit
  21. 23 Mar, 2011 2 commits
    • Robert Morell's avatar
      pwm_backlight: add check_fb() hook · ef0a5e80
      Robert Morell authored
      In systems with multiple framebuffer devices, one of the devices might be
      blanked while another is unblanked.  In order for the backlight blanking
      logic to know whether to turn off the backlight for a particular
      framebuffer's blanking notification, it needs to be able to check if a
      given framebuffer device corresponds to the backlight.
      This plumbs the check_fb hook from core backlight through the
      pwm_backlight helper to allow platform code to plug in a check_fb hook.
      Signed-off-by: default avatarRobert Morell <rmorell@nvidia.com>
      Cc: Richard Purdie <rpurdie@rpsys.net>
      Cc: Arun Murthy <arun.murthy@stericsson.com>
      Cc: Linus Walleij <linus.walleij@stericsson.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
    • Matthew Garrett's avatar
      backlight: add backlight type · bb7ca747
      Matthew Garrett authored
      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
      Signed-off-by: default avatarMatthew Garrett <mjg@redhat.com>
      Cc: Richard Purdie <rpurdie@rpsys.net>
      Cc: Chris Wilson <chris@chris-wilson.co.uk>
      Cc: David Airlie <airlied@linux.ie>
      Cc: Alex Deucher <alexdeucher@gmail.com>
      Cc: Ben Skeggs <bskeggs@redhat.com>
      Cc: Zhang Rui <rui.zhang@intel.com>
      Cc: Len Brown <lenb@kernel.org>
      Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
  22. 12 Nov, 2010 1 commit
    • Arun Murthy's avatar
      backlight: add low threshold to pwm backlight · fef7764f
      Arun Murthy authored
      The intensity of the backlight can be varied from a range of
      max_brightness to zero.  Though most, if not all the pwm based backlight
      devices start flickering at lower brightness value.  And also for each
      device there exists a brightness value below which the backlight appears
      to be turned off though the value is not equal to zero.
      If the range of brightness for a device is from zero to max_brightness.  A
      graph is plotted for brightness Vs intensity for the pwm based backlight
      device has to be a linear graph.
      	  |   /
      	  |  /
      	  | /
      	 0	max_brightness
      But pratically on measuring the above we note that the intensity of
      backlight goes to zero(OFF) when the value in not zero almost nearing to
      zero(some x%).  so the graph looks like
      	  |    /
      	  |   /
      	  |  /
      	  |  |
      	 0   x	 max_brightness
      In order to overcome this drawback knowing this x% i.e nothing but the low
      threshold beyond which the backlight is off and will have no effect, the
      brightness value is being offset by the low threshold value(retaining the
      linearity of the graph).  Now the graph becomes
      	  |     /
      	  |    /
      	  |   /
      	  |  /
      	   0	  max_brightness
      With this for each and every digit increment in the brightness from zero
      there is a change in the intensity of backlight.  Devices having this
      behaviour can set the low threshold brightness(lth_brightness) and pass
      the same as platform data else can have it as zero.
      [akpm@linux-foundation.org: coding-style fixes]
      Signed-off-by: default avatarArun Murthy <arun.murthy@stericsson.com>
      Acked-by: default avatarLinus Walleij <linus.walleij@stericsson.com>
      Acked-by: default avatarRichard Purdie <rpurdie@linux.intel.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
  23. 30 Mar, 2010 1 commit
    • Tejun Heo's avatar
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking... · 5a0e3ad6
      Tejun Heo authored
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
      percpu.h is included by sched.h and module.h and thus ends up being
      included when building most .c files.  percpu.h includes slab.h which
      in turn includes gfp.h making everything defined by the two files
      universally available and complicating inclusion dependencies.
      percpu.h -> slab.h dependency is about to be removed.  Prepare for
      this change by updating users of gfp and slab facilities include those
      headers directly instead of assuming availability.  As this conversion
      needs to touch large number of source files, the following script is
      used as the basis of conversion.
      The script does the followings.
      * Scan files for gfp and slab usages and update includes such that
        only the necessary includes are there.  ie. if only gfp is used,
        gfp.h, if slab is used, slab.h.
      * When the script inserts a new include, it looks at the include
        blocks and try to put the new include such that its order conforms
        to its surrounding.  It's put in the include block which contains
        core kernel includes, in the same order that the rest are ordered -
        alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
        doesn't seem to be any matching order.
      * If the script can't find a place to put a new include (mostly
        because the file doesn't have fitting include block), it prints out
        an error message indicating which .h file needs to be added to the
      The conversion was done in the following steps.
      1. The initial automatic conversion of all .c files updated slightly
         over 4000 files, deleting around 700 includes and adding ~480 gfp.h
         and ~3000 slab.h inclusions.  The script emitted errors for ~400
      2. Each error was manually checked.  Some didn't need the inclusion,
         some needed manual addition while adding it to implementation .h or
         embedding .c file was more appropriate for others.  This step added
         inclusions to around 150 files.
      3. The script was run again and the output was compared to the edits
         from #2 to make sure no file was left behind.
      4. Several build tests were done and a couple of problems were fixed.
         e.g. lib/decompress_*.c used malloc/free() wrappers around slab
         APIs requiring slab.h to be added manually.
      5. The script was run on all .h files but without automatically
         editing them as sprinkling gfp.h and slab.h inclusions around .h
         files could easily lead to inclusion dependency hell.  Most gfp.h
         inclusion directives were ignored as stuff from gfp.h was usually
         wildly available and often used in preprocessor macros.  Each
         slab.h inclusion directive was examined and added manually as
      6. percpu.h was updated not to include slab.h.
      7. Build test were done on the following configurations and failures
         were fixed.  CONFIG_GCOV_KERNEL was turned off for all tests (as my
         distributed build env didn't work with gcov compiles) and a few
         more options had to be turned off depending on archs to make things
         build (like ipr on powerpc/64 which failed due to missing writeq).
         * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
         * powerpc and powerpc64 SMP allmodconfig
         * sparc and sparc64 SMP allmodconfig
         * ia64 SMP allmodconfig
         * s390 SMP allmodconfig
         * alpha SMP allmodconfig
         * um on x86_64 SMP allmodconfig
      8. percpu.h modifications were reverted so that it could be applied as
         a separate patch and serve as bisection point.
      Given the fact that I had only a couple of failures from tests on step
      6, I'm fairly confident about the coverage of this conversion patch.
      If there is a breakage, it's likely to be something in one of the arch
      headers which should be easily discoverable easily on most builds of
      the specific arch.
      Signed-off-by: default avatarTejun Heo <tj@kernel.org>
      Guess-its-ok-by: default avatarChristoph Lameter <cl@linux-foundation.org>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
  24. 16 Mar, 2010 1 commit
  25. 17 Dec, 2009 1 commit
  26. 16 Dec, 2009 1 commit
  27. 03 Jul, 2009 1 commit
  28. 06 Apr, 2009 1 commit
  29. 05 Aug, 2008 2 commits
  30. 03 Jul, 2008 1 commit