Kconfig 14 KB

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