Kconfig 6.0 KB

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