Kconfig 12 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335
  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 AD525X_DPOT
  13. tristate "Analog Devices AD525x Digital Potentiometers"
  14. depends on I2C && SYSFS
  15. help
  16. If you say yes here, you get support for the Analog Devices
  17. AD5258, AD5259, AD5251, AD5252, AD5253, AD5254 and AD5255
  18. digital potentiometer chips.
  19. See Documentation/misc-devices/ad525x_dpot.txt for the
  20. userspace interface.
  21. This driver can also be built as a module. If so, the module
  22. will be called ad525x_dpot.
  23. config ATMEL_PWM
  24. tristate "Atmel AT32/AT91 PWM support"
  25. depends on AVR32 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9
  26. help
  27. This option enables device driver support for the PWM channels
  28. on certain Atmel processors. Pulse Width Modulation is used for
  29. purposes including software controlled power-efficient backlights
  30. on LCD displays, motor control, and waveform generation.
  31. config ATMEL_TCLIB
  32. bool "Atmel AT32/AT91 Timer/Counter Library"
  33. depends on (AVR32 || ARCH_AT91)
  34. help
  35. Select this if you want a library to allocate the Timer/Counter
  36. blocks found on many Atmel processors. This facilitates using
  37. these blocks by different drivers despite processor differences.
  38. config ATMEL_TCB_CLKSRC
  39. bool "TC Block Clocksource"
  40. depends on ATMEL_TCLIB && GENERIC_TIME
  41. default y
  42. help
  43. Select this to get a high precision clocksource based on a
  44. TC block with a 5+ MHz base clock rate. Two timer channels
  45. are combined to make a single 32-bit timer.
  46. When GENERIC_CLOCKEVENTS is defined, the third timer channel
  47. may be used as a clock event device supporting oneshot mode
  48. (delays of up to two seconds) based on the 32 KiHz clock.
  49. config ATMEL_TCB_CLKSRC_BLOCK
  50. int
  51. depends on ATMEL_TCB_CLKSRC
  52. prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X
  53. default 0
  54. range 0 1
  55. help
  56. Some chips provide more than one TC block, so you have the
  57. choice of which one to use for the clock framework. The other
  58. TC can be used for other purposes, such as PWM generation and
  59. interval timing.
  60. config IBM_ASM
  61. tristate "Device driver for IBM RSA service processor"
  62. depends on X86 && PCI && INPUT && EXPERIMENTAL
  63. ---help---
  64. This option enables device driver support for in-band access to the
  65. IBM RSA (Condor) service processor in eServer xSeries systems.
  66. The ibmasm device driver allows user space application to access
  67. ASM (Advanced Systems Management) functions on the service
  68. processor. The driver is meant to be used in conjunction with
  69. a user space API.
  70. The ibmasm driver also enables the OS to use the UART on the
  71. service processor board as a regular serial port. To make use of
  72. this feature serial driver support (CONFIG_SERIAL_8250) must be
  73. enabled.
  74. WARNING: This software may not be supported or function
  75. correctly on your IBM server. Please consult the IBM ServerProven
  76. website <http://www.pc.ibm.com/ww/eserver/xseries/serverproven> for
  77. information on the specific driver level and support statement
  78. for your IBM server.
  79. config PHANTOM
  80. tristate "Sensable PHANToM (PCI)"
  81. depends on PCI
  82. help
  83. Say Y here if you want to build a driver for Sensable PHANToM device.
  84. This driver is only for PCI PHANToMs.
  85. If you choose to build module, its name will be phantom. If unsure,
  86. say N here.
  87. config SGI_IOC4
  88. tristate "SGI IOC4 Base IO support"
  89. depends on PCI
  90. ---help---
  91. This option enables basic support for the IOC4 chip on certain
  92. SGI IO controller cards (IO9, IO10, and PCI-RT). This option
  93. does not enable any specific functions on such a card, but provides
  94. necessary infrastructure for other drivers to utilize.
  95. If you have an SGI Altix with an IOC4-based card say Y.
  96. Otherwise say N.
  97. config TIFM_CORE
  98. tristate "TI Flash Media interface support (EXPERIMENTAL)"
  99. depends on EXPERIMENTAL && PCI
  100. help
  101. If you want support for Texas Instruments(R) Flash Media adapters
  102. you should select this option and then also choose an appropriate
  103. host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
  104. support', if you have a TI PCI74xx compatible card reader, for
  105. example.
  106. You will also have to select some flash card format drivers. MMC/SD
  107. cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
  108. Interface support (MMC_TIFM_SD)'.
  109. To compile this driver as a module, choose M here: the module will
  110. be called tifm_core.
  111. config TIFM_7XX1
  112. tristate "TI Flash Media PCI74xx/PCI76xx host adapter support (EXPERIMENTAL)"
  113. depends on PCI && TIFM_CORE && EXPERIMENTAL
  114. default TIFM_CORE
  115. help
  116. This option enables support for Texas Instruments(R) PCI74xx and
  117. PCI76xx families of Flash Media adapters, found in many laptops.
  118. To make actual use of the device, you will have to select some
  119. flash card format drivers, as outlined in the TIFM_CORE Help.
  120. To compile this driver as a module, choose M here: the module will
  121. be called tifm_7xx1.
  122. config ICS932S401
  123. tristate "Integrated Circuits ICS932S401"
  124. depends on I2C && EXPERIMENTAL
  125. help
  126. If you say yes here you get support for the Integrated Circuits
  127. ICS932S401 clock control chips.
  128. This driver can also be built as a module. If so, the module
  129. will be called ics932s401.
  130. config ATMEL_SSC
  131. tristate "Device driver for Atmel SSC peripheral"
  132. depends on AVR32 || ARCH_AT91
  133. ---help---
  134. This option enables device driver support for Atmel Synchronized
  135. Serial Communication peripheral (SSC).
  136. The SSC peripheral supports a wide variety of serial frame based
  137. communications, i.e. I2S, SPI, etc.
  138. If unsure, say N.
  139. config ENCLOSURE_SERVICES
  140. tristate "Enclosure Services"
  141. default n
  142. help
  143. Provides support for intelligent enclosures (bays which
  144. contain storage devices). You also need either a host
  145. driver (SCSI/ATA) which supports enclosures
  146. or a SCSI enclosure device (SES) to use these services.
  147. config SGI_XP
  148. tristate "Support communication between SGI SSIs"
  149. depends on NET
  150. depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
  151. select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
  152. select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
  153. select SGI_GRU if X86_64 && SMP
  154. ---help---
  155. An SGI machine can be divided into multiple Single System
  156. Images which act independently of each other and have
  157. hardware based memory protection from the others. Enabling
  158. this feature will allow for direct communication between SSIs
  159. based on a network adapter and DMA messaging.
  160. config CS5535_MFGPT
  161. tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
  162. depends on PCI
  163. depends on X86
  164. default n
  165. help
  166. This driver provides access to MFGPT functionality for other
  167. drivers that need timers. MFGPTs are available in the CS5535 and
  168. CS5536 companion chips that are found in AMD Geode and several
  169. other platforms. They have a better resolution and max interval
  170. than the generic PIT, and are suitable for use as high-res timers.
  171. You probably don't want to enable this manually; other drivers that
  172. make use of it should enable it.
  173. config CS5535_MFGPT_DEFAULT_IRQ
  174. int
  175. depends on CS5535_MFGPT
  176. default 7
  177. help
  178. MFGPTs on the CS5535 require an interrupt. The selected IRQ
  179. can be overridden as a module option as well as by driver that
  180. use the cs5535_mfgpt_ API; however, different architectures might
  181. want to use a different IRQ by default. This is here for
  182. architectures to set as necessary.
  183. config CS5535_CLOCK_EVENT_SRC
  184. tristate "CS5535/CS5536 high-res timer (MFGPT) events"
  185. depends on GENERIC_TIME && GENERIC_CLOCKEVENTS && CS5535_MFGPT
  186. help
  187. This driver provides a clock event source based on the MFGPT
  188. timer(s) in the CS5535 and CS5536 companion chips.
  189. MFGPTs have a better resolution and max interval than the
  190. generic PIT, and are suitable for use as high-res timers.
  191. config HP_ILO
  192. tristate "Channel interface driver for HP iLO/iLO2 processor"
  193. depends on PCI
  194. default n
  195. help
  196. The channel interface driver allows applications to communicate
  197. with iLO/iLO2 management processors present on HP ProLiant
  198. servers. Upon loading, the driver creates /dev/hpilo/dXccbN files,
  199. which can be used to gather data from the management processor,
  200. via read and write system calls.
  201. To compile this driver as a module, choose M here: the
  202. module will be called hpilo.
  203. config SGI_GRU
  204. tristate "SGI GRU driver"
  205. depends on X86_UV && SMP
  206. default n
  207. select MMU_NOTIFIER
  208. ---help---
  209. The GRU is a hardware resource located in the system chipset. The GRU
  210. contains memory that can be mmapped into the user address space. This memory is
  211. used to communicate with the GRU to perform functions such as load/store,
  212. scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
  213. instructions using user virtual addresses. GRU instructions (ex., bcopy) use
  214. user virtual addresses for operands.
  215. If you are not running on a SGI UV system, say N.
  216. config SGI_GRU_DEBUG
  217. bool "SGI GRU driver debug"
  218. depends on SGI_GRU
  219. default n
  220. ---help---
  221. This option enables addition debugging code for the SGI GRU driver. If
  222. you are unsure, say N.
  223. config ISL29003
  224. tristate "Intersil ISL29003 ambient light sensor"
  225. depends on I2C && SYSFS
  226. help
  227. If you say yes here you get support for the Intersil ISL29003
  228. ambient light sensor.
  229. This driver can also be built as a module. If so, the module
  230. will be called isl29003.
  231. config SENSORS_TSL2550
  232. tristate "Taos TSL2550 ambient light sensor"
  233. depends on I2C && SYSFS
  234. help
  235. If you say yes here you get support for the Taos TSL2550
  236. ambient light sensor.
  237. This driver can also be built as a module. If so, the module
  238. will be called tsl2550.
  239. config EP93XX_PWM
  240. tristate "EP93xx PWM support"
  241. depends on ARCH_EP93XX
  242. help
  243. This option enables device driver support for the PWM channels
  244. on the Cirrus EP93xx processors. The EP9307 chip only has one
  245. PWM channel all the others have two, the second channel is an
  246. alternate function of the EGPIO14 pin. A sysfs interface is
  247. provided to control the PWM channels.
  248. To compile this driver as a module, choose M here: the module will
  249. be called ep93xx_pwm.
  250. config DS1682
  251. tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
  252. depends on I2C && EXPERIMENTAL
  253. help
  254. If you say yes here you get support for Dallas Semiconductor
  255. DS1682 Total Elapsed Time Recorder.
  256. This driver can also be built as a module. If so, the module
  257. will be called ds1682.
  258. config TI_DAC7512
  259. tristate "Texas Instruments DAC7512"
  260. depends on SPI && SYSFS
  261. help
  262. If you say yes here you get support for the Texas Instruments
  263. DAC7512 16-bit digital-to-analog converter.
  264. This driver can also be built as a module. If so, the module
  265. will be calles ti_dac7512.
  266. config VMWARE_BALLOON
  267. tristate "VMware Balloon Driver"
  268. depends on X86
  269. help
  270. This is VMware physical memory management driver which acts
  271. like a "balloon" that can be inflated to reclaim physical pages
  272. by reserving them in the guest and invalidating them in the
  273. monitor, freeing up the underlying machine pages so they can
  274. be allocated to other guests. The balloon can also be deflated
  275. to allow the guest to use more physical memory.
  276. If unsure, say N.
  277. To compile this driver as a module, choose M here: the
  278. module will be called vmware_balloon.
  279. source "drivers/misc/c2port/Kconfig"
  280. source "drivers/misc/eeprom/Kconfig"
  281. source "drivers/misc/cb710/Kconfig"
  282. source "drivers/misc/iwmc3200top/Kconfig"
  283. endif # MISC_DEVICES