Kconfig 13 KB

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