Kconfig 16 KB

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