sysfs-class-backlight 2.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263
  1. What: /sys/class/backlight/<backlight>/bl_power
  2. Date: April 2005
  3. KernelVersion: 2.6.12
  4. Contact: Richard Purdie <rpurdie@rpsys.net>
  5. Description:
  6. Control BACKLIGHT power, values are compatible with
  7. FB_BLANK_* from fb.h
  8. - 0 (FB_BLANK_UNBLANK) : power on.
  9. - 4 (FB_BLANK_POWERDOWN) : power off
  10. Users: HAL
  11. What: /sys/class/backlight/<backlight>/brightness
  12. Date: April 2005
  13. KernelVersion: 2.6.12
  14. Contact: Richard Purdie <rpurdie@rpsys.net>
  15. Description:
  16. Control the brightness for this <backlight>. Values
  17. are between 0 and max_brightness. This file will also
  18. show the brightness level stored in the driver, which
  19. may not be the actual brightness (see actual_brightness).
  20. Users: HAL
  21. What: /sys/class/backlight/<backlight>/actual_brightness
  22. Date: March 2006
  23. KernelVersion: 2.6.17
  24. Contact: Richard Purdie <rpurdie@rpsys.net>
  25. Description:
  26. Show the actual brightness by querying the hardware. Due
  27. to implementation differences in hardware this may not
  28. match the value in 'brightness'. For example some hardware
  29. may treat blanking differently or have custom power saving
  30. features. Userspace should generally use the values in
  31. 'brightness' to make decisions.
  32. Users: HAL
  33. What: /sys/class/backlight/<backlight>/max_brightness
  34. Date: April 2005
  35. KernelVersion: 2.6.12
  36. Contact: Richard Purdie <rpurdie@rpsys.net>
  37. Description:
  38. Maximum brightness for <backlight>.
  39. Users: HAL
  40. What: /sys/class/backlight/<backlight>/type
  41. Date: September 2010
  42. KernelVersion: 2.6.37
  43. Contact: Matthew Garrett <mjg@redhat.com>
  44. Description:
  45. The type of interface controlled by <backlight>.
  46. "firmware": The driver uses a standard firmware interface
  47. "platform": The driver uses a platform-specific interface
  48. "raw": The driver controls hardware registers directly
  49. In the general case, when multiple backlight
  50. interfaces are available for a single device, firmware
  51. control should be preferred to platform control should
  52. be preferred to raw control. Using a firmware
  53. interface reduces the probability of confusion with
  54. the hardware and the OS independently updating the
  55. backlight state. Platform interfaces are mostly a
  56. holdover from pre-standardisation of firmware
  57. interfaces.