Kconfig 13 KB

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