Kconfig 7.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255
  1. menuconfig NEW_LEDS
  2. bool "LED Support"
  3. help
  4. Say Y to enable Linux LED support. This allows control of supported
  5. LEDs from both userspace and optionally, by kernel events (triggers).
  6. This is not related to standard keyboard LEDs which are controlled
  7. via the input system.
  8. if NEW_LEDS
  9. config LEDS_CLASS
  10. tristate "LED Class Support"
  11. help
  12. This option enables the led sysfs class in /sys/class/leds. You'll
  13. need this to do anything useful with LEDs. If unsure, say N.
  14. comment "LED drivers"
  15. config LEDS_ATMEL_PWM
  16. tristate "LED Support using Atmel PWM outputs"
  17. depends on LEDS_CLASS && ATMEL_PWM
  18. help
  19. This option enables support for LEDs driven using outputs
  20. of the dedicated PWM controller found on newer Atmel SOCs.
  21. config LEDS_LOCOMO
  22. tristate "LED Support for Locomo device"
  23. depends on LEDS_CLASS && SHARP_LOCOMO
  24. help
  25. This option enables support for the LEDs on Sharp Locomo.
  26. Zaurus models SL-5500 and SL-5600.
  27. config LEDS_S3C24XX
  28. tristate "LED Support for Samsung S3C24XX GPIO LEDs"
  29. depends on LEDS_CLASS && ARCH_S3C2410
  30. help
  31. This option enables support for LEDs connected to GPIO lines
  32. on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440.
  33. config LEDS_AMS_DELTA
  34. tristate "LED Support for the Amstrad Delta (E3)"
  35. depends on LEDS_CLASS && MACH_AMS_DELTA
  36. help
  37. This option enables support for the LEDs on Amstrad Delta (E3).
  38. config LEDS_NET48XX
  39. tristate "LED Support for Soekris net48xx series Error LED"
  40. depends on LEDS_CLASS && SCx200_GPIO
  41. help
  42. This option enables support for the Soekris net4801 and net4826 error
  43. LED.
  44. config LEDS_FSG
  45. tristate "LED Support for the Freecom FSG-3"
  46. depends on LEDS_CLASS && MACH_FSG
  47. help
  48. This option enables support for the LEDs on the Freecom FSG-3.
  49. config LEDS_WRAP
  50. tristate "LED Support for the WRAP series LEDs"
  51. depends on LEDS_CLASS && SCx200_GPIO
  52. help
  53. This option enables support for the PCEngines WRAP programmable LEDs.
  54. config LEDS_ALIX2
  55. tristate "LED Support for ALIX.2 and ALIX.3 series"
  56. depends on LEDS_CLASS && X86 && EXPERIMENTAL
  57. help
  58. This option enables support for the PCEngines ALIX.2 and ALIX.3 LEDs.
  59. config LEDS_H1940
  60. tristate "LED Support for iPAQ H1940 device"
  61. depends on LEDS_CLASS && ARCH_H1940
  62. help
  63. This option enables support for the LEDs on the h1940.
  64. config LEDS_COBALT_QUBE
  65. tristate "LED Support for the Cobalt Qube series front LED"
  66. depends on LEDS_CLASS && MIPS_COBALT
  67. help
  68. This option enables support for the front LED on Cobalt Qube series
  69. config LEDS_COBALT_RAQ
  70. bool "LED Support for the Cobalt Raq series"
  71. depends on LEDS_CLASS=y && MIPS_COBALT
  72. select LEDS_TRIGGERS
  73. help
  74. This option enables support for the Cobalt Raq series LEDs.
  75. config LEDS_SUNFIRE
  76. tristate "LED support for SunFire servers."
  77. depends on LEDS_CLASS && SPARC64
  78. select LEDS_TRIGGERS
  79. help
  80. This option enables support for the Left, Middle, and Right
  81. LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
  82. config LEDS_HP6XX
  83. tristate "LED Support for the HP Jornada 6xx"
  84. depends on LEDS_CLASS && SH_HP6XX
  85. help
  86. This option enables LED support for the handheld
  87. HP Jornada 620/660/680/690.
  88. config LEDS_PCA9532
  89. tristate "LED driver for PCA9532 dimmer"
  90. depends on LEDS_CLASS && I2C && INPUT && EXPERIMENTAL
  91. help
  92. This option enables support for NXP pca9532
  93. LED controller. It is generally only useful
  94. as a platform driver
  95. config LEDS_GPIO
  96. tristate "LED Support for GPIO connected LEDs"
  97. depends on LEDS_CLASS && GENERIC_GPIO
  98. help
  99. This option enables support for the LEDs connected to GPIO
  100. outputs. To be useful the particular board must have LEDs
  101. and they must be connected to the GPIO lines. The LEDs must be
  102. defined as platform devices and/or OpenFirmware platform devices.
  103. The code to use these bindings can be selected below.
  104. config LEDS_GPIO_PLATFORM
  105. bool "Platform device bindings for GPIO LEDs"
  106. depends on LEDS_GPIO
  107. default y
  108. help
  109. Let the leds-gpio driver drive LEDs which have been defined as
  110. platform devices. If you don't know what this means, say yes.
  111. config LEDS_GPIO_OF
  112. bool "OpenFirmware platform device bindings for GPIO LEDs"
  113. depends on LEDS_GPIO && OF_DEVICE
  114. default y
  115. help
  116. Let the leds-gpio driver drive LEDs which have been defined as
  117. of_platform devices. For instance, LEDs which are listed in a "dts"
  118. file.
  119. config LEDS_CLEVO_MAIL
  120. tristate "Mail LED on Clevo notebook (EXPERIMENTAL)"
  121. depends on LEDS_CLASS && X86 && SERIO_I8042 && DMI && EXPERIMENTAL
  122. help
  123. This driver makes the mail LED accessible from userspace
  124. programs through the leds subsystem. This LED have three
  125. known mode: off, blink at 0.5Hz and blink at 1Hz.
  126. The driver supports two kinds of interface: using ledtrig-timer
  127. or through /sys/class/leds/clevo::mail/brightness. As this LED
  128. cannot change it's brightness it blinks instead. The brightness
  129. value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
  130. blink at 1Hz.
  131. This module can drive the mail LED for the following notebooks:
  132. Clevo D400P
  133. Clevo D410J
  134. Clevo D410V
  135. Clevo D400V/D470V (not tested, but might work)
  136. Clevo M540N
  137. Clevo M5x0N (not tested, but might work)
  138. Positivo Mobile (Clevo M5x0V)
  139. If your model is not listed here you can try the "nodetect"
  140. module parameter.
  141. To compile this driver as a module, choose M here: the
  142. module will be called leds-clevo-mail.
  143. config LEDS_PCA955X
  144. tristate "LED Support for PCA955x I2C chips"
  145. depends on LEDS_CLASS && I2C
  146. help
  147. This option enables support for LEDs connected to PCA955x
  148. LED driver chips accessed via the I2C bus. Supported
  149. devices include PCA9550, PCA9551, PCA9552, and PCA9553.
  150. config LEDS_WM8350
  151. tristate "LED Support for WM8350 AudioPlus PMIC"
  152. depends on LEDS_CLASS && MFD_WM8350
  153. help
  154. This option enables support for LEDs driven by the Wolfson
  155. Microelectronics WM8350 AudioPlus PMIC.
  156. config LEDS_DA903X
  157. tristate "LED Support for DA9030/DA9034 PMIC"
  158. depends on LEDS_CLASS && PMIC_DA903X
  159. help
  160. This option enables support for on-chip LED drivers found
  161. on Dialog Semiconductor DA9030/DA9034 PMICs.
  162. config LEDS_DAC124S085
  163. tristate "LED Support for DAC124S085 SPI DAC"
  164. depends on LEDS_CLASS && SPI
  165. help
  166. This option enables support for DAC124S085 SPI DAC from NatSemi,
  167. which can be used to control up to four LEDs.
  168. comment "LED Triggers"
  169. config LEDS_TRIGGERS
  170. bool "LED Trigger support"
  171. help
  172. This option enables trigger support for the leds class.
  173. These triggers allow kernel events to drive the LEDs and can
  174. be configured via sysfs. If unsure, say Y.
  175. config LEDS_TRIGGER_TIMER
  176. tristate "LED Timer Trigger"
  177. depends on LEDS_TRIGGERS
  178. help
  179. This allows LEDs to be controlled by a programmable timer
  180. via sysfs. Some LED hardware can be programmed to start
  181. blinking the LED without any further software interaction.
  182. For more details read Documentation/leds-class.txt.
  183. If unsure, say Y.
  184. config LEDS_TRIGGER_IDE_DISK
  185. bool "LED IDE Disk Trigger"
  186. depends on LEDS_TRIGGERS && IDE_GD_ATA
  187. help
  188. This allows LEDs to be controlled by IDE disk activity.
  189. If unsure, say Y.
  190. config LEDS_TRIGGER_HEARTBEAT
  191. tristate "LED Heartbeat Trigger"
  192. depends on LEDS_TRIGGERS
  193. help
  194. This allows LEDs to be controlled by a CPU load average.
  195. The flash frequency is a hyperbolic function of the 1-minute
  196. load average.
  197. If unsure, say Y.
  198. config LEDS_TRIGGER_BACKLIGHT
  199. tristate "LED backlight Trigger"
  200. depends on LEDS_TRIGGERS
  201. help
  202. This allows LEDs to be controlled as a backlight device: they
  203. turn off and on when the display is blanked and unblanked.
  204. If unsure, say N.
  205. config LEDS_TRIGGER_DEFAULT_ON
  206. tristate "LED Default ON Trigger"
  207. depends on LEDS_TRIGGERS
  208. help
  209. This allows LEDs to be initialised in the ON state.
  210. If unsure, say Y.
  211. comment "iptables trigger is under Netfilter config (LED target)"
  212. depends on LEDS_TRIGGERS
  213. endif # NEW_LEDS