Kconfig 17 KB

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