Kconfig 14 KB

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