Kconfig 8.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235
  1. #
  2. # Misc strange devices
  3. #
  4. menuconfig MISC_DEVICES
  5. bool "Misc devices"
  6. default y
  7. ---help---
  8. Say Y here to get to see options for device drivers from various
  9. different categories. This option alone does not add any kernel code.
  10. If you say N, all options in this submenu will be skipped and disabled.
  11. if MISC_DEVICES
  12. config ATMEL_PWM
  13. tristate "Atmel AT32/AT91 PWM support"
  14. depends on AVR32 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9
  15. help
  16. This option enables device driver support for the PWM channels
  17. on certain Atmel prcoessors. Pulse Width Modulation is used for
  18. purposes including software controlled power-efficent backlights
  19. on LCD displays, motor control, and waveform generation.
  20. config ATMEL_TCLIB
  21. bool "Atmel AT32/AT91 Timer/Counter Library"
  22. depends on (AVR32 || ARCH_AT91)
  23. help
  24. Select this if you want a library to allocate the Timer/Counter
  25. blocks found on many Atmel processors. This facilitates using
  26. these blocks by different drivers despite processor differences.
  27. config ATMEL_TCB_CLKSRC
  28. bool "TC Block Clocksource"
  29. depends on ATMEL_TCLIB && GENERIC_TIME
  30. default y
  31. help
  32. Select this to get a high precision clocksource based on a
  33. TC block with a 5+ MHz base clock rate. Two timer channels
  34. are combined to make a single 32-bit timer.
  35. When GENERIC_CLOCKEVENTS is defined, the third timer channel
  36. may be used as a clock event device supporting oneshot mode
  37. (delays of up to two seconds) based on the 32 KiHz clock.
  38. config ATMEL_TCB_CLKSRC_BLOCK
  39. int
  40. depends on ATMEL_TCB_CLKSRC
  41. prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X
  42. default 0
  43. range 0 1
  44. help
  45. Some chips provide more than one TC block, so you have the
  46. choice of which one to use for the clock framework. The other
  47. TC can be used for other purposes, such as PWM generation and
  48. interval timing.
  49. config IBM_ASM
  50. tristate "Device driver for IBM RSA service processor"
  51. depends on X86 && PCI && INPUT && EXPERIMENTAL
  52. ---help---
  53. This option enables device driver support for in-band access to the
  54. IBM RSA (Condor) service processor in eServer xSeries systems.
  55. The ibmasm device driver allows user space application to access
  56. ASM (Advanced Systems Management) functions on the service
  57. processor. The driver is meant to be used in conjunction with
  58. a user space API.
  59. The ibmasm driver also enables the OS to use the UART on the
  60. service processor board as a regular serial port. To make use of
  61. this feature serial driver support (CONFIG_SERIAL_8250) must be
  62. enabled.
  63. WARNING: This software may not be supported or function
  64. correctly on your IBM server. Please consult the IBM ServerProven
  65. website <http://www.pc.ibm.com/ww/eserver/xseries/serverproven> for
  66. information on the specific driver level and support statement
  67. for your IBM server.
  68. config PHANTOM
  69. tristate "Sensable PHANToM (PCI)"
  70. depends on PCI
  71. help
  72. Say Y here if you want to build a driver for Sensable PHANToM device.
  73. This driver is only for PCI PHANToMs.
  74. If you choose to build module, its name will be phantom. If unsure,
  75. say N here.
  76. config EEPROM_93CX6
  77. tristate "EEPROM 93CX6 support"
  78. ---help---
  79. This is a driver for the EEPROM chipsets 93c46 and 93c66.
  80. The driver supports both read as well as write commands.
  81. If unsure, say N.
  82. config SGI_IOC4
  83. tristate "SGI IOC4 Base IO support"
  84. depends on PCI
  85. ---help---
  86. This option enables basic support for the IOC4 chip on certain
  87. SGI IO controller cards (IO9, IO10, and PCI-RT). This option
  88. does not enable any specific functions on such a card, but provides
  89. necessary infrastructure for other drivers to utilize.
  90. If you have an SGI Altix with an IOC4-based card say Y.
  91. Otherwise say N.
  92. config TIFM_CORE
  93. tristate "TI Flash Media interface support (EXPERIMENTAL)"
  94. depends on EXPERIMENTAL && PCI
  95. help
  96. If you want support for Texas Instruments(R) Flash Media adapters
  97. you should select this option and then also choose an appropriate
  98. host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
  99. support', if you have a TI PCI74xx compatible card reader, for
  100. example.
  101. You will also have to select some flash card format drivers. MMC/SD
  102. cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
  103. Interface support (MMC_TIFM_SD)'.
  104. To compile this driver as a module, choose M here: the module will
  105. be called tifm_core.
  106. config TIFM_7XX1
  107. tristate "TI Flash Media PCI74xx/PCI76xx host adapter support (EXPERIMENTAL)"
  108. depends on PCI && TIFM_CORE && EXPERIMENTAL
  109. default TIFM_CORE
  110. help
  111. This option enables support for Texas Instruments(R) PCI74xx and
  112. PCI76xx families of Flash Media adapters, found in many laptops.
  113. To make actual use of the device, you will have to select some
  114. flash card format drivers, as outlined in the TIFM_CORE Help.
  115. To compile this driver as a module, choose M here: the module will
  116. be called tifm_7xx1.
  117. config ICS932S401
  118. tristate "Integrated Circuits ICS932S401"
  119. depends on I2C && EXPERIMENTAL
  120. help
  121. If you say yes here you get support for the Integrated Circuits
  122. ICS932S401 clock control chips.
  123. This driver can also be built as a module. If so, the module
  124. will be called ics932s401.
  125. config ATMEL_SSC
  126. tristate "Device driver for Atmel SSC peripheral"
  127. depends on AVR32 || ARCH_AT91
  128. ---help---
  129. This option enables device driver support for Atmel Syncronized
  130. Serial Communication peripheral (SSC).
  131. The SSC peripheral supports a wide variety of serial frame based
  132. communications, i.e. I2S, SPI, etc.
  133. If unsure, say N.
  134. config ENCLOSURE_SERVICES
  135. tristate "Enclosure Services"
  136. default n
  137. help
  138. Provides support for intelligent enclosures (bays which
  139. contain storage devices). You also need either a host
  140. driver (SCSI/ATA) which supports enclosures
  141. or a SCSI enclosure device (SES) to use these services.
  142. config SGI_XP
  143. tristate "Support communication between SGI SSIs"
  144. depends on NET
  145. depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_64) && SMP
  146. select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
  147. select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
  148. select SGI_GRU if (IA64_GENERIC || IA64_SGI_UV || X86_64) && SMP
  149. ---help---
  150. An SGI machine can be divided into multiple Single System
  151. Images which act independently of each other and have
  152. hardware based memory protection from the others. Enabling
  153. this feature will allow for direct communication between SSIs
  154. based on a network adapter and DMA messaging.
  155. config HP_ILO
  156. tristate "Channel interface driver for HP iLO/iLO2 processor"
  157. depends on PCI
  158. default n
  159. help
  160. The channel interface driver allows applications to communicate
  161. with iLO/iLO2 management processors present on HP ProLiant
  162. servers. Upon loading, the driver creates /dev/hpilo/dXccbN files,
  163. which can be used to gather data from the management processor,
  164. via read and write system calls.
  165. To compile this driver as a module, choose M here: the
  166. module will be called hpilo.
  167. config SGI_GRU
  168. tristate "SGI GRU driver"
  169. depends on (X86_64 || IA64_SGI_UV || IA64_GENERIC) && SMP
  170. default n
  171. select MMU_NOTIFIER
  172. ---help---
  173. The GRU is a hardware resource located in the system chipset. The GRU
  174. contains memory that can be mmapped into the user address space. This memory is
  175. used to communicate with the GRU to perform functions such as load/store,
  176. scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
  177. instructions using user virtual addresses. GRU instructions (ex., bcopy) use
  178. user virtual addresses for operands.
  179. If you are not running on a SGI UV system, say N.
  180. config SGI_GRU_DEBUG
  181. bool "SGI GRU driver debug"
  182. depends on SGI_GRU
  183. default n
  184. ---help---
  185. This option enables addition debugging code for the SGI GRU driver. If
  186. you are unsure, say N.
  187. config DELL_LAPTOP
  188. tristate "Dell Laptop Extras (EXPERIMENTAL)"
  189. depends on X86
  190. depends on DCDBAS
  191. depends on EXPERIMENTAL
  192. depends on BACKLIGHT_CLASS_DEVICE
  193. depends on RFKILL
  194. default n
  195. ---help---
  196. This driver adds support for rfkill and backlight control to Dell
  197. laptops.
  198. source "drivers/misc/c2port/Kconfig"
  199. endif # MISC_DEVICES