Kconfig 5.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195
  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. if NEW_LEDS
  9. config LEDS_CLASS
  10. tristate "LED Class Support"
  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. comment "LED drivers"
  15. config LEDS_ATMEL_PWM
  16. tristate "LED Support using Atmel PWM outputs"
  17. depends on LEDS_CLASS && ATMEL_PWM
  18. help
  19. This option enables support for LEDs driven using outputs
  20. of the dedicated PWM controller found on newer Atmel SOCs.
  21. config LEDS_LOCOMO
  22. tristate "LED Support for Locomo device"
  23. depends on LEDS_CLASS && SHARP_LOCOMO
  24. help
  25. This option enables support for the LEDs on Sharp Locomo.
  26. Zaurus models SL-5500 and SL-5600.
  27. config LEDS_S3C24XX
  28. tristate "LED Support for Samsung S3C24XX GPIO LEDs"
  29. depends on LEDS_CLASS && ARCH_S3C2410
  30. help
  31. This option enables support for LEDs connected to GPIO lines
  32. on Samsung S3C24XX series CPUs, such as the S3C2410 and S3C2440.
  33. config LEDS_AMS_DELTA
  34. tristate "LED Support for the Amstrad Delta (E3)"
  35. depends on LEDS_CLASS && MACH_AMS_DELTA
  36. help
  37. This option enables support for the LEDs on Amstrad Delta (E3).
  38. config LEDS_NET48XX
  39. tristate "LED Support for Soekris net48xx series Error LED"
  40. depends on LEDS_CLASS && SCx200_GPIO
  41. help
  42. This option enables support for the Soekris net4801 and net4826 error
  43. LED.
  44. config LEDS_FSG
  45. tristate "LED Support for the Freecom FSG-3"
  46. depends on LEDS_CLASS && MACH_FSG
  47. help
  48. This option enables support for the LEDs on the Freecom FSG-3.
  49. config LEDS_WRAP
  50. tristate "LED Support for the WRAP series LEDs"
  51. depends on LEDS_CLASS && SCx200_GPIO
  52. help
  53. This option enables support for the PCEngines WRAP programmable LEDs.
  54. config LEDS_H1940
  55. tristate "LED Support for iPAQ H1940 device"
  56. depends on LEDS_CLASS && ARCH_H1940
  57. help
  58. This option enables support for the LEDs on the h1940.
  59. config LEDS_COBALT_QUBE
  60. tristate "LED Support for the Cobalt Qube series front LED"
  61. depends on LEDS_CLASS && MIPS_COBALT
  62. help
  63. This option enables support for the front LED on Cobalt Qube series
  64. config LEDS_COBALT_RAQ
  65. bool "LED Support for the Cobalt Raq series"
  66. depends on LEDS_CLASS && MIPS_COBALT
  67. select LEDS_TRIGGERS
  68. help
  69. This option enables support for the Cobalt Raq series LEDs.
  70. config LEDS_HP6XX
  71. tristate "LED Support for the HP Jornada 6xx"
  72. depends on LEDS_CLASS && SH_HP6XX
  73. help
  74. This option enables led support for the handheld
  75. HP Jornada 620/660/680/690.
  76. config LEDS_PCA9532
  77. tristate "LED driver for PCA9532 dimmer"
  78. depends on LEDS_CLASS && I2C && INPUT && EXPERIMENTAL
  79. help
  80. This option enables support for NXP pca9532
  81. led controller. It is generally only usefull
  82. as a platform driver
  83. config LEDS_GPIO
  84. tristate "LED Support for GPIO connected LEDs"
  85. depends on LEDS_CLASS && GENERIC_GPIO
  86. help
  87. This option enables support for the LEDs connected to GPIO
  88. outputs. To be useful the particular board must have LEDs
  89. and they must be connected to the GPIO lines.
  90. config LEDS_CM_X270
  91. tristate "LED Support for the CM-X270 LEDs"
  92. depends on LEDS_CLASS && MACH_ARMCORE
  93. help
  94. This option enables support for the CM-X270 LEDs.
  95. config LEDS_CLEVO_MAIL
  96. tristate "Mail LED on Clevo notebook (EXPERIMENTAL)"
  97. depends on LEDS_CLASS && X86 && SERIO_I8042 && DMI && EXPERIMENTAL
  98. help
  99. This driver makes the mail LED accessible from userspace
  100. programs through the leds subsystem. This LED have three
  101. known mode: off, blink at 0.5Hz and blink at 1Hz.
  102. The driver supports two kinds of interface: using ledtrig-timer
  103. or through /sys/class/leds/clevo::mail/brightness. As this LED
  104. cannot change it's brightness it blinks instead. The brightness
  105. value 0 means off, 1..127 means blink at 0.5Hz and 128..255 means
  106. blink at 1Hz.
  107. This module can drive the mail LED for the following notebooks:
  108. Clevo D400P
  109. Clevo D410J
  110. Clevo D410V
  111. Clevo D400V/D470V (not tested, but might work)
  112. Clevo M540N
  113. Clevo M5x0N (not tested, but might work)
  114. Positivo Mobile (Clevo M5x0V)
  115. If your model is not listed here you can try the "nodetect"
  116. module paramter.
  117. To compile this driver as a module, choose M here: the
  118. module will be called leds-clevo-mail.
  119. config LEDS_PCA955X
  120. tristate "LED Support for PCA955x I2C chips"
  121. depends on LEDS_CLASS && I2C
  122. help
  123. This option enables support for LEDs connected to PCA955x
  124. LED driver chips accessed via the I2C bus. Supported
  125. devices include PCA9550, PCA9551, PCA9552, and PCA9553.
  126. comment "LED Triggers"
  127. config LEDS_TRIGGERS
  128. bool "LED Trigger support"
  129. help
  130. This option enables trigger support for the leds class.
  131. These triggers allow kernel events to drive the LEDs and can
  132. be configured via sysfs. If unsure, say Y.
  133. config LEDS_TRIGGER_TIMER
  134. tristate "LED Timer Trigger"
  135. depends on LEDS_TRIGGERS
  136. help
  137. This allows LEDs to be controlled by a programmable timer
  138. via sysfs. Some LED hardware can be programmed to start
  139. blinking the LED without any further software interaction.
  140. For more details read Documentation/leds-class.txt.
  141. If unsure, say Y.
  142. config LEDS_TRIGGER_IDE_DISK
  143. bool "LED IDE Disk Trigger"
  144. depends on LEDS_TRIGGERS && BLK_DEV_IDEDISK
  145. help
  146. This allows LEDs to be controlled by IDE disk activity.
  147. If unsure, say Y.
  148. config LEDS_TRIGGER_HEARTBEAT
  149. tristate "LED Heartbeat Trigger"
  150. depends on LEDS_TRIGGERS
  151. help
  152. This allows LEDs to be controlled by a CPU load average.
  153. The flash frequency is a hyperbolic function of the 1-minute
  154. load average.
  155. If unsure, say Y.
  156. config LEDS_TRIGGER_DEFAULT_ON
  157. tristate "LED Default ON Trigger"
  158. depends on LEDS_TRIGGERS
  159. help
  160. This allows LEDs to be initialised in the ON state.
  161. If unsure, say Y.
  162. endif # NEW_LEDS