Kconfig 9.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307
  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_MIKROTIK_RB532
  28. tristate "LED Support for Mikrotik Routerboard 532"
  29. depends on LEDS_CLASS && MIKROTIK_RB532
  30. help
  31. This option enables support for the so called "User LED" of
  32. Mikrotik's Routerboard 532.
  33. config LEDS_S3C24XX
  34. tristate "LED Support for Samsung S3C24XX GPIO LEDs"
  35. depends on LEDS_CLASS && ARCH_S3C2410
  36. help
  37. This option enables support for LEDs connected to GPIO lines
  38. on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440.
  39. config LEDS_AMS_DELTA
  40. tristate "LED Support for the Amstrad Delta (E3)"
  41. depends on LEDS_CLASS && MACH_AMS_DELTA
  42. help
  43. This option enables support for the LEDs on Amstrad Delta (E3).
  44. config LEDS_NET48XX
  45. tristate "LED Support for Soekris net48xx series Error LED"
  46. depends on LEDS_CLASS && SCx200_GPIO
  47. help
  48. This option enables support for the Soekris net4801 and net4826 error
  49. LED.
  50. config LEDS_FSG
  51. tristate "LED Support for the Freecom FSG-3"
  52. depends on LEDS_CLASS && MACH_FSG
  53. help
  54. This option enables support for the LEDs on the Freecom FSG-3.
  55. config LEDS_WRAP
  56. tristate "LED Support for the WRAP series LEDs"
  57. depends on LEDS_CLASS && SCx200_GPIO
  58. help
  59. This option enables support for the PCEngines WRAP programmable LEDs.
  60. config LEDS_ALIX2
  61. tristate "LED Support for ALIX.2 and ALIX.3 series"
  62. depends on LEDS_CLASS && X86 && EXPERIMENTAL
  63. help
  64. This option enables support for the PCEngines ALIX.2 and ALIX.3 LEDs.
  65. You have to set leds-alix2.force=1 for boards with Award BIOS.
  66. config LEDS_H1940
  67. tristate "LED Support for iPAQ H1940 device"
  68. depends on LEDS_CLASS && ARCH_H1940
  69. help
  70. This option enables support for the LEDs on the h1940.
  71. config LEDS_COBALT_QUBE
  72. tristate "LED Support for the Cobalt Qube series front LED"
  73. depends on LEDS_CLASS && MIPS_COBALT
  74. help
  75. This option enables support for the front LED on Cobalt Qube series
  76. config LEDS_COBALT_RAQ
  77. bool "LED Support for the Cobalt Raq series"
  78. depends on LEDS_CLASS=y && MIPS_COBALT
  79. select LEDS_TRIGGERS
  80. help
  81. This option enables support for the Cobalt Raq series LEDs.
  82. config LEDS_SUNFIRE
  83. tristate "LED support for SunFire servers."
  84. depends on LEDS_CLASS && SPARC64
  85. select LEDS_TRIGGERS
  86. help
  87. This option enables support for the Left, Middle, and Right
  88. LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
  89. config LEDS_HP6XX
  90. tristate "LED Support for the HP Jornada 6xx"
  91. depends on LEDS_CLASS && SH_HP6XX
  92. help
  93. This option enables LED support for the handheld
  94. HP Jornada 620/660/680/690.
  95. config LEDS_PCA9532
  96. tristate "LED driver for PCA9532 dimmer"
  97. depends on LEDS_CLASS && I2C && INPUT && EXPERIMENTAL
  98. help
  99. This option enables support for NXP pca9532
  100. LED controller. It is generally only useful
  101. as a platform driver
  102. config LEDS_GPIO
  103. tristate "LED Support for GPIO connected LEDs"
  104. depends on LEDS_CLASS && GENERIC_GPIO
  105. help
  106. This option enables support for the LEDs connected to GPIO
  107. outputs. To be useful the particular board must have LEDs
  108. and they must be connected to the GPIO lines. The LEDs must be
  109. defined as platform devices and/or OpenFirmware platform devices.
  110. The code to use these bindings can be selected below.
  111. config LEDS_GPIO_PLATFORM
  112. bool "Platform device bindings for GPIO LEDs"
  113. depends on LEDS_GPIO
  114. default y
  115. help
  116. Let the leds-gpio driver drive LEDs which have been defined as
  117. platform devices. If you don't know what this means, say yes.
  118. config LEDS_GPIO_OF
  119. bool "OpenFirmware platform device bindings for GPIO LEDs"
  120. depends on LEDS_GPIO && OF_DEVICE
  121. default y
  122. help
  123. Let the leds-gpio driver drive LEDs which have been defined as
  124. of_platform devices. For instance, LEDs which are listed in a "dts"
  125. file.
  126. config LEDS_LP3944
  127. tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip"
  128. depends on LEDS_CLASS && I2C
  129. help
  130. This option enables support for LEDs connected to the National
  131. Semiconductor LP3944 Lighting Management Unit (LMU) also known as
  132. Fun Light Chip.
  133. To compile this driver as a module, choose M here: the
  134. module will be called leds-lp3944.
  135. config LEDS_CLEVO_MAIL
  136. tristate "Mail LED on Clevo notebook"
  137. depends on LEDS_CLASS && X86 && SERIO_I8042 && DMI
  138. help
  139. This driver makes the mail LED accessible from userspace
  140. programs through the leds subsystem. This LED have three
  141. known mode: off, blink at 0.5Hz and blink at 1Hz.
  142. The driver supports two kinds of interface: using ledtrig-timer
  143. or through /sys/class/leds/clevo::mail/brightness. As this LED
  144. cannot change it's brightness it blinks instead. The brightness
  145. value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
  146. blink at 1Hz.
  147. This module can drive the mail LED for the following notebooks:
  148. Clevo D400P
  149. Clevo D410J
  150. Clevo D410V
  151. Clevo D400V/D470V (not tested, but might work)
  152. Clevo M540N
  153. Clevo M5x0N (not tested, but might work)
  154. Positivo Mobile (Clevo M5x0V)
  155. If your model is not listed here you can try the "nodetect"
  156. module parameter.
  157. To compile this driver as a module, choose M here: the
  158. module will be called leds-clevo-mail.
  159. config LEDS_PCA955X
  160. tristate "LED Support for PCA955x I2C chips"
  161. depends on LEDS_CLASS && I2C
  162. help
  163. This option enables support for LEDs connected to PCA955x
  164. LED driver chips accessed via the I2C bus. Supported
  165. devices include PCA9550, PCA9551, PCA9552, and PCA9553.
  166. config LEDS_WM831X_STATUS
  167. tristate "LED support for status LEDs on WM831x PMICs"
  168. depends on LEDS_CLASS && MFD_WM831X
  169. help
  170. This option enables support for the status LEDs of the WM831x
  171. series of PMICs.
  172. config LEDS_WM8350
  173. tristate "LED Support for WM8350 AudioPlus PMIC"
  174. depends on LEDS_CLASS && MFD_WM8350
  175. help
  176. This option enables support for LEDs driven by the Wolfson
  177. Microelectronics WM8350 AudioPlus PMIC.
  178. config LEDS_DA903X
  179. tristate "LED Support for DA9030/DA9034 PMIC"
  180. depends on LEDS_CLASS && PMIC_DA903X
  181. help
  182. This option enables support for on-chip LED drivers found
  183. on Dialog Semiconductor DA9030/DA9034 PMICs.
  184. config LEDS_DAC124S085
  185. tristate "LED Support for DAC124S085 SPI DAC"
  186. depends on LEDS_CLASS && SPI
  187. help
  188. This option enables support for DAC124S085 SPI DAC from NatSemi,
  189. which can be used to control up to four LEDs.
  190. config LEDS_PWM
  191. tristate "PWM driven LED Support"
  192. depends on LEDS_CLASS && HAVE_PWM
  193. help
  194. This option enables support for pwm driven LEDs
  195. config LEDS_BD2802
  196. tristate "LED driver for BD2802 RGB LED"
  197. depends on LEDS_CLASS && I2C
  198. help
  199. This option enables support for BD2802GU RGB LED driver chips
  200. accessed via the I2C bus.
  201. comment "LED Triggers"
  202. config LEDS_TRIGGERS
  203. bool "LED Trigger support"
  204. help
  205. This option enables trigger support for the leds class.
  206. These triggers allow kernel events to drive the LEDs and can
  207. be configured via sysfs. If unsure, say Y.
  208. config LEDS_TRIGGER_TIMER
  209. tristate "LED Timer Trigger"
  210. depends on LEDS_TRIGGERS
  211. help
  212. This allows LEDs to be controlled by a programmable timer
  213. via sysfs. Some LED hardware can be programmed to start
  214. blinking the LED without any further software interaction.
  215. For more details read Documentation/leds-class.txt.
  216. If unsure, say Y.
  217. config LEDS_TRIGGER_IDE_DISK
  218. bool "LED IDE Disk Trigger"
  219. depends on LEDS_TRIGGERS && IDE_GD_ATA
  220. help
  221. This allows LEDs to be controlled by IDE disk activity.
  222. If unsure, say Y.
  223. config LEDS_TRIGGER_HEARTBEAT
  224. tristate "LED Heartbeat Trigger"
  225. depends on LEDS_TRIGGERS
  226. help
  227. This allows LEDs to be controlled by a CPU load average.
  228. The flash frequency is a hyperbolic function of the 1-minute
  229. load average.
  230. If unsure, say Y.
  231. config LEDS_TRIGGER_BACKLIGHT
  232. tristate "LED backlight Trigger"
  233. depends on LEDS_TRIGGERS
  234. help
  235. This allows LEDs to be controlled as a backlight device: they
  236. turn off and on when the display is blanked and unblanked.
  237. If unsure, say N.
  238. config LEDS_TRIGGER_GPIO
  239. tristate "LED GPIO Trigger"
  240. depends on LEDS_TRIGGERS
  241. depends on GPIOLIB
  242. help
  243. This allows LEDs to be controlled by gpio events. It's good
  244. when using gpios as switches and triggering the needed LEDs
  245. from there. One use case is n810's keypad LEDs that could
  246. be triggered by this trigger when user slides up to show
  247. keypad.
  248. If unsure, say N.
  249. config LEDS_TRIGGER_DEFAULT_ON
  250. tristate "LED Default ON Trigger"
  251. depends on LEDS_TRIGGERS
  252. help
  253. This allows LEDs to be initialised in the ON state.
  254. If unsure, say Y.
  255. comment "iptables trigger is under Netfilter config (LED target)"
  256. depends on LEDS_TRIGGERS
  257. endif # NEW_LEDS