Kconfig 12 KB

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