Kconfig 14 KB

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