Kconfig 11 KB

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