Kconfig 17 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564
  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_LM3533
  45. tristate "LED support for LM3533"
  46. depends on LEDS_CLASS
  47. depends on MFD_LM3533
  48. help
  49. This option enables support for the LEDs on National Semiconductor /
  50. TI LM3533 Lighting Power chips.
  51. The LEDs can be controlled directly, through PWM input, or by the
  52. ambient-light-sensor interface. The chip supports
  53. hardware-accelerated blinking with maximum on and off periods of 9.8
  54. and 77 seconds respectively.
  55. config LEDS_LM3642
  56. tristate "LED support for LM3642 Chip"
  57. depends on LEDS_CLASS && I2C
  58. select REGMAP_I2C
  59. help
  60. This option enables support for LEDs connected to LM3642.
  61. The LM3642 is a 4MHz fixed-frequency synchronous boost
  62. converter plus 1.5A constant current driver for a high-current
  63. white LED.
  64. config LEDS_LOCOMO
  65. tristate "LED Support for Locomo device"
  66. depends on LEDS_CLASS
  67. depends on SHARP_LOCOMO
  68. help
  69. This option enables support for the LEDs on Sharp Locomo.
  70. Zaurus models SL-5500 and SL-5600.
  71. config LEDS_MIKROTIK_RB532
  72. tristate "LED Support for Mikrotik Routerboard 532"
  73. depends on LEDS_CLASS
  74. depends on MIKROTIK_RB532
  75. help
  76. This option enables support for the so called "User LED" of
  77. Mikrotik's Routerboard 532.
  78. config LEDS_S3C24XX
  79. tristate "LED Support for Samsung S3C24XX GPIO LEDs"
  80. depends on LEDS_CLASS
  81. depends on ARCH_S3C24XX
  82. help
  83. This option enables support for LEDs connected to GPIO lines
  84. on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440.
  85. config LEDS_NET48XX
  86. tristate "LED Support for Soekris net48xx series Error LED"
  87. depends on LEDS_CLASS
  88. depends on SCx200_GPIO
  89. help
  90. This option enables support for the Soekris net4801 and net4826 error
  91. LED.
  92. config LEDS_FSG
  93. tristate "LED Support for the Freecom FSG-3"
  94. depends on LEDS_CLASS
  95. depends on MACH_FSG
  96. help
  97. This option enables support for the LEDs on the Freecom FSG-3.
  98. config LEDS_WRAP
  99. tristate "LED Support for the WRAP series LEDs"
  100. depends on LEDS_CLASS
  101. depends on SCx200_GPIO
  102. help
  103. This option enables support for the PCEngines WRAP programmable LEDs.
  104. config LEDS_COBALT_QUBE
  105. tristate "LED Support for the Cobalt Qube series front LED"
  106. depends on LEDS_CLASS
  107. depends on MIPS_COBALT
  108. help
  109. This option enables support for the front LED on Cobalt Qube series
  110. config LEDS_COBALT_RAQ
  111. bool "LED Support for the Cobalt Raq series"
  112. depends on LEDS_CLASS=y && MIPS_COBALT
  113. select LEDS_TRIGGERS
  114. help
  115. This option enables support for the Cobalt Raq series LEDs.
  116. config LEDS_SUNFIRE
  117. tristate "LED support for SunFire servers."
  118. depends on LEDS_CLASS
  119. depends on SPARC64
  120. select LEDS_TRIGGERS
  121. help
  122. This option enables support for the Left, Middle, and Right
  123. LEDs on the I/O and CPU boards of SunFire UltraSPARC servers.
  124. config LEDS_HP6XX
  125. tristate "LED Support for the HP Jornada 6xx"
  126. depends on LEDS_CLASS
  127. depends on SH_HP6XX
  128. help
  129. This option enables LED support for the handheld
  130. HP Jornada 620/660/680/690.
  131. config LEDS_PCA9532
  132. tristate "LED driver for PCA9532 dimmer"
  133. depends on LEDS_CLASS
  134. depends on I2C && INPUT && EXPERIMENTAL
  135. help
  136. This option enables support for NXP pca9532
  137. LED controller. It is generally only useful
  138. as a platform driver
  139. config LEDS_PCA9532_GPIO
  140. bool "Enable GPIO support for PCA9532"
  141. depends on LEDS_PCA9532
  142. depends on GPIOLIB
  143. help
  144. Allow unused pins on PCA9532 to be used as gpio.
  145. To use a pin as gpio pca9532_type in pca9532_platform data needs to
  146. set to PCA9532_TYPE_GPIO.
  147. config LEDS_GPIO
  148. tristate "LED Support for GPIO connected LEDs"
  149. depends on LEDS_CLASS
  150. depends on GENERIC_GPIO
  151. help
  152. This option enables support for the LEDs connected to GPIO
  153. outputs. To be useful the particular board must have LEDs
  154. and they must be connected to the GPIO lines. The LEDs must be
  155. defined as platform devices and/or OpenFirmware platform devices.
  156. The code to use these bindings can be selected below.
  157. config LEDS_LP3944
  158. tristate "LED Support for N.S. LP3944 (Fun Light) I2C chip"
  159. depends on LEDS_CLASS
  160. depends on I2C
  161. help
  162. This option enables support for LEDs connected to the National
  163. Semiconductor LP3944 Lighting Management Unit (LMU) also known as
  164. Fun Light Chip.
  165. To compile this driver as a module, choose M here: the
  166. module will be called leds-lp3944.
  167. config LEDS_LP5521
  168. tristate "LED Support for N.S. LP5521 LED driver chip"
  169. depends on LEDS_CLASS && I2C
  170. help
  171. If you say yes here you get support for the National Semiconductor
  172. LP5521 LED driver. It is 3 channel chip with programmable engines.
  173. Driver provides direct control via LED class and interface for
  174. programming the engines.
  175. config LEDS_LP5523
  176. tristate "LED Support for TI/National LP5523/55231 LED driver chip"
  177. depends on LEDS_CLASS && I2C
  178. help
  179. If you say yes here you get support for TI/National Semiconductor
  180. LP5523/55231 LED driver.
  181. It is 9 channel chip with programmable engines.
  182. Driver provides direct control via LED class and interface for
  183. programming the engines.
  184. config LEDS_LP8788
  185. tristate "LED support for the TI LP8788 PMIC"
  186. depends on LEDS_CLASS
  187. depends on MFD_LP8788
  188. help
  189. This option enables support for the Keyboard LEDs on the LP8788 PMIC.
  190. config LEDS_CLEVO_MAIL
  191. tristate "Mail LED on Clevo notebook"
  192. depends on LEDS_CLASS
  193. depends on X86 && SERIO_I8042 && DMI
  194. help
  195. This driver makes the mail LED accessible from userspace
  196. programs through the leds subsystem. This LED have three
  197. known mode: off, blink at 0.5Hz and blink at 1Hz.
  198. The driver supports two kinds of interface: using ledtrig-timer
  199. or through /sys/class/leds/clevo::mail/brightness. As this LED
  200. cannot change it's brightness it blinks instead. The brightness
  201. value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
  202. blink at 1Hz.
  203. This module can drive the mail LED for the following notebooks:
  204. Clevo D400P
  205. Clevo D410J
  206. Clevo D410V
  207. Clevo D400V/D470V (not tested, but might work)
  208. Clevo M540N
  209. Clevo M5x0N (not tested, but might work)
  210. Positivo Mobile (Clevo M5x0V)
  211. If your model is not listed here you can try the "nodetect"
  212. module parameter.
  213. To compile this driver as a module, choose M here: the
  214. module will be called leds-clevo-mail.
  215. config LEDS_PCA955X
  216. tristate "LED Support for PCA955x I2C chips"
  217. depends on LEDS_CLASS
  218. depends on I2C
  219. help
  220. This option enables support for LEDs connected to PCA955x
  221. LED driver chips accessed via the I2C bus. Supported
  222. devices include PCA9550, PCA9551, PCA9552, and PCA9553.
  223. config LEDS_PCA9633
  224. tristate "LED support for PCA9633 I2C chip"
  225. depends on LEDS_CLASS
  226. depends on I2C
  227. help
  228. This option enables support for LEDs connected to the PCA9633
  229. LED driver chip accessed via the I2C bus.
  230. config LEDS_WM831X_STATUS
  231. tristate "LED support for status LEDs on WM831x PMICs"
  232. depends on LEDS_CLASS
  233. depends on MFD_WM831X
  234. help
  235. This option enables support for the status LEDs of the WM831x
  236. series of PMICs.
  237. config LEDS_WM8350
  238. tristate "LED Support for WM8350 AudioPlus PMIC"
  239. depends on LEDS_CLASS
  240. depends on MFD_WM8350
  241. help
  242. This option enables support for LEDs driven by the Wolfson
  243. Microelectronics WM8350 AudioPlus PMIC.
  244. config LEDS_DA903X
  245. tristate "LED Support for DA9030/DA9034 PMIC"
  246. depends on LEDS_CLASS
  247. depends on PMIC_DA903X
  248. help
  249. This option enables support for on-chip LED drivers found
  250. on Dialog Semiconductor DA9030/DA9034 PMICs.
  251. config LEDS_DA9052
  252. tristate "Dialog DA9052/DA9053 LEDS"
  253. depends on LEDS_CLASS
  254. depends on PMIC_DA9052
  255. help
  256. This option enables support for on-chip LED drivers found
  257. on Dialog Semiconductor DA9052-BC and DA9053-AA/Bx PMICs.
  258. config LEDS_DAC124S085
  259. tristate "LED Support for DAC124S085 SPI DAC"
  260. depends on LEDS_CLASS
  261. depends on SPI
  262. help
  263. This option enables support for DAC124S085 SPI DAC from NatSemi,
  264. which can be used to control up to four LEDs.
  265. config LEDS_PWM
  266. tristate "PWM driven LED Support"
  267. depends on LEDS_CLASS
  268. depends on HAVE_PWM
  269. help
  270. This option enables support for pwm driven LEDs
  271. config LEDS_REGULATOR
  272. tristate "REGULATOR driven LED support"
  273. depends on LEDS_CLASS
  274. depends on REGULATOR
  275. help
  276. This option enables support for regulator driven LEDs.
  277. config LEDS_BD2802
  278. tristate "LED driver for BD2802 RGB LED"
  279. depends on LEDS_CLASS
  280. depends on I2C
  281. help
  282. This option enables support for BD2802GU RGB LED driver chips
  283. accessed via the I2C bus.
  284. config LEDS_INTEL_SS4200
  285. tristate "LED driver for Intel NAS SS4200 series"
  286. depends on LEDS_CLASS
  287. depends on PCI && DMI
  288. help
  289. This option enables support for the Intel SS4200 series of
  290. Network Attached Storage servers. You may control the hard
  291. drive or power LEDs on the front panel. Using this driver
  292. can stop the front LED from blinking after startup.
  293. config LEDS_LT3593
  294. tristate "LED driver for LT3593 controllers"
  295. depends on LEDS_CLASS
  296. depends on GENERIC_GPIO
  297. help
  298. This option enables support for LEDs driven by a Linear Technology
  299. LT3593 controller. This controller uses a special one-wire pulse
  300. coding protocol to set the brightness.
  301. config LEDS_ADP5520
  302. tristate "LED Support for ADP5520/ADP5501 PMIC"
  303. depends on LEDS_CLASS
  304. depends on PMIC_ADP5520
  305. help
  306. This option enables support for on-chip LED drivers found
  307. on Analog Devices ADP5520/ADP5501 PMICs.
  308. To compile this driver as a module, choose M here: the module will
  309. be called leds-adp5520.
  310. config LEDS_DELL_NETBOOKS
  311. tristate "External LED on Dell Business Netbooks"
  312. depends on LEDS_CLASS
  313. depends on X86 && ACPI_WMI
  314. help
  315. This adds support for the Latitude 2100 and similar
  316. notebooks that have an external LED.
  317. config LEDS_MC13783
  318. tristate "LED Support for MC13783 PMIC"
  319. depends on LEDS_CLASS
  320. depends on MFD_MC13783
  321. help
  322. This option enable support for on-chip LED drivers found
  323. on Freescale Semiconductor MC13783 PMIC.
  324. config LEDS_NS2
  325. tristate "LED support for Network Space v2 GPIO LEDs"
  326. depends on LEDS_CLASS
  327. depends on MACH_NETSPACE_V2 || MACH_INETSPACE_V2 || \
  328. MACH_NETSPACE_MAX_V2 || MACH_D2NET_V2 || \
  329. MACH_NETSPACE_V2_DT || MACH_INETSPACE_V2_DT || \
  330. MACH_NETSPACE_MAX_V2_DT || MACH_NETSPACE_MINI_V2_DT
  331. default y
  332. help
  333. This option enable support for the dual-GPIO LED found on the
  334. Network Space v2 board (and parents). This include Internet Space v2,
  335. Network Space (Max) v2 and d2 Network v2 boards.
  336. config LEDS_NETXBIG
  337. tristate "LED support for Big Network series LEDs"
  338. depends on MACH_NET2BIG_V2 || MACH_NET5BIG_V2
  339. depends on LEDS_CLASS
  340. default y
  341. help
  342. This option enable support for LEDs found on the LaCie 2Big
  343. and 5Big Network v2 boards. The LEDs are wired to a CPLD and are
  344. controlled through a GPIO extension bus.
  345. config LEDS_ASIC3
  346. bool "LED support for the HTC ASIC3"
  347. depends on LEDS_CLASS=y
  348. depends on MFD_ASIC3
  349. default y
  350. help
  351. This option enables support for the LEDs on the HTC ASIC3. The HTC
  352. ASIC3 LED GPIOs are inputs, not outputs, thus the leds-gpio driver
  353. cannot be used. This driver supports hardware blinking with an on+off
  354. period from 62ms to 125s. Say Y to enable LEDs on the HP iPAQ hx4700.
  355. config LEDS_RENESAS_TPU
  356. bool "LED support for Renesas TPU"
  357. depends on LEDS_CLASS=y && HAVE_CLK && GENERIC_GPIO
  358. help
  359. This option enables build of the LED TPU platform driver,
  360. suitable to drive any TPU channel on newer Renesas SoCs.
  361. The driver controls the GPIO pin connected to the LED via
  362. the GPIO framework and expects the LED to be connected to
  363. a pin that can be driven in both GPIO mode and using TPU
  364. pin function. The latter to support brightness control.
  365. Brightness control is supported but hardware blinking is not.
  366. config LEDS_TCA6507
  367. tristate "LED Support for TCA6507 I2C chip"
  368. depends on LEDS_CLASS && I2C
  369. help
  370. This option enables support for LEDs connected to TC6507
  371. LED driver chips accessed via the I2C bus.
  372. Driver support brightness control and hardware-assisted blinking.
  373. config LEDS_MAX8997
  374. tristate "LED support for MAX8997 PMIC"
  375. depends on LEDS_CLASS && MFD_MAX8997
  376. help
  377. This option enables support for on-chip LED drivers on
  378. MAXIM MAX8997 PMIC.
  379. config LEDS_LM355x
  380. tristate "LED support for LM355x Chips, LM3554 and LM3556"
  381. depends on LEDS_CLASS && I2C
  382. select REGMAP_I2C
  383. help
  384. This option enables support for LEDs connected to LM355x.
  385. LM355x includes Torch, Flash and Indicator functions.
  386. config LEDS_OT200
  387. tristate "LED support for the Bachmann OT200"
  388. depends on LEDS_CLASS && HAS_IOMEM
  389. help
  390. This option enables support for the LEDs on the Bachmann OT200.
  391. Say Y to enable LEDs on the Bachmann OT200.
  392. config LEDS_BLINKM
  393. tristate "LED support for the BlinkM I2C RGB LED"
  394. depends on LEDS_CLASS
  395. depends on I2C
  396. help
  397. This option enables support for the BlinkM RGB LED connected
  398. through I2C. Say Y to enable support for the BlinkM LED.
  399. config LEDS_TRIGGERS
  400. bool "LED Trigger support"
  401. depends on LEDS_CLASS
  402. help
  403. This option enables trigger support for the leds class.
  404. These triggers allow kernel events to drive the LEDs and can
  405. be configured via sysfs. If unsure, say Y.
  406. comment "LED Triggers"
  407. config LEDS_TRIGGER_TIMER
  408. tristate "LED Timer Trigger"
  409. depends on LEDS_TRIGGERS
  410. help
  411. This allows LEDs to be controlled by a programmable timer
  412. via sysfs. Some LED hardware can be programmed to start
  413. blinking the LED without any further software interaction.
  414. For more details read Documentation/leds/leds-class.txt.
  415. If unsure, say Y.
  416. config LEDS_TRIGGER_ONESHOT
  417. tristate "LED One-shot Trigger"
  418. depends on LEDS_TRIGGERS
  419. help
  420. This allows LEDs to blink in one-shot pulses with parameters
  421. controlled via sysfs. It's useful to notify the user on
  422. sporadic events, when there are no clear begin and end trap points,
  423. or on dense events, where this blinks the LED at constant rate if
  424. rearmed continuously.
  425. It also shows how to use the led_blink_set_oneshot() function.
  426. If unsure, say Y.
  427. config LEDS_TRIGGER_IDE_DISK
  428. bool "LED IDE Disk Trigger"
  429. depends on IDE_GD_ATA
  430. depends on LEDS_TRIGGERS
  431. help
  432. This allows LEDs to be controlled by IDE disk activity.
  433. If unsure, say Y.
  434. config LEDS_TRIGGER_HEARTBEAT
  435. tristate "LED Heartbeat Trigger"
  436. depends on LEDS_TRIGGERS
  437. help
  438. This allows LEDs to be controlled by a CPU load average.
  439. The flash frequency is a hyperbolic function of the 1-minute
  440. load average.
  441. If unsure, say Y.
  442. config LEDS_TRIGGER_BACKLIGHT
  443. tristate "LED backlight Trigger"
  444. depends on LEDS_TRIGGERS
  445. help
  446. This allows LEDs to be controlled as a backlight device: they
  447. turn off and on when the display is blanked and unblanked.
  448. If unsure, say N.
  449. config LEDS_TRIGGER_CPU
  450. bool "LED CPU Trigger"
  451. depends on LEDS_TRIGGERS
  452. help
  453. This allows LEDs to be controlled by active CPUs. This shows
  454. the active CPUs across an array of LEDs so you can see which
  455. CPUs are active on the system at any given moment.
  456. If unsure, say N.
  457. config LEDS_TRIGGER_GPIO
  458. tristate "LED GPIO Trigger"
  459. depends on LEDS_TRIGGERS
  460. depends on GPIOLIB
  461. help
  462. This allows LEDs to be controlled by gpio events. It's good
  463. when using gpios as switches and triggering the needed LEDs
  464. from there. One use case is n810's keypad LEDs that could
  465. be triggered by this trigger when user slides up to show
  466. keypad.
  467. If unsure, say N.
  468. config LEDS_TRIGGER_DEFAULT_ON
  469. tristate "LED Default ON Trigger"
  470. depends on LEDS_TRIGGERS
  471. help
  472. This allows LEDs to be initialised in the ON state.
  473. If unsure, say Y.
  474. comment "iptables trigger is under Netfilter config (LED target)"
  475. depends on LEDS_TRIGGERS
  476. config LEDS_TRIGGER_TRANSIENT
  477. tristate "LED Transient Trigger"
  478. depends on LEDS_TRIGGERS
  479. help
  480. This allows one time activation of a transient state on
  481. GPIO/PWM based hardware.
  482. If unsure, say Y.
  483. endif # NEW_LEDS