Kconfig 15 KB

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