Kconfig 18 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539
  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 DUMMY_IRQ
  81. tristate "Dummy IRQ handler"
  82. default n
  83. ---help---
  84. This module accepts a single 'irq' parameter, which it should register for.
  85. The sole purpose of this module is to help with debugging of systems on
  86. which spurious IRQs would happen on disabled IRQ vector.
  87. config IBM_ASM
  88. tristate "Device driver for IBM RSA service processor"
  89. depends on X86 && PCI && INPUT
  90. ---help---
  91. This option enables device driver support for in-band access to the
  92. IBM RSA (Condor) service processor in eServer xSeries systems.
  93. The ibmasm device driver allows user space application to access
  94. ASM (Advanced Systems Management) functions on the service
  95. processor. The driver is meant to be used in conjunction with
  96. a user space API.
  97. The ibmasm driver also enables the OS to use the UART on the
  98. service processor board as a regular serial port. To make use of
  99. this feature serial driver support (CONFIG_SERIAL_8250) must be
  100. enabled.
  101. WARNING: This software may not be supported or function
  102. correctly on your IBM server. Please consult the IBM ServerProven
  103. website <http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>
  104. for information on the specific driver level and support statement
  105. for your IBM server.
  106. config PHANTOM
  107. tristate "Sensable PHANToM (PCI)"
  108. depends on PCI
  109. help
  110. Say Y here if you want to build a driver for Sensable PHANToM device.
  111. This driver is only for PCI PHANToMs.
  112. If you choose to build module, its name will be phantom. If unsure,
  113. say N here.
  114. config INTEL_MID_PTI
  115. tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard"
  116. depends on PCI && TTY
  117. default n
  118. help
  119. The PTI (Parallel Trace Interface) driver directs
  120. trace data routed from various parts in the system out
  121. through an Intel Penwell PTI port and out of the mobile
  122. device for analysis with a debugging tool (Lauterbach or Fido).
  123. You should select this driver if the target kernel is meant for
  124. an Intel Atom (non-netbook) mobile device containing a MIPI
  125. P1149.7 standard implementation.
  126. config SGI_IOC4
  127. tristate "SGI IOC4 Base IO support"
  128. depends on PCI
  129. ---help---
  130. This option enables basic support for the IOC4 chip on certain
  131. SGI IO controller cards (IO9, IO10, and PCI-RT). This option
  132. does not enable any specific functions on such a card, but provides
  133. necessary infrastructure for other drivers to utilize.
  134. If you have an SGI Altix with an IOC4-based card say Y.
  135. Otherwise say N.
  136. config TIFM_CORE
  137. tristate "TI Flash Media interface support"
  138. depends on PCI
  139. help
  140. If you want support for Texas Instruments(R) Flash Media adapters
  141. you should select this option and then also choose an appropriate
  142. host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
  143. support', if you have a TI PCI74xx compatible card reader, for
  144. example.
  145. You will also have to select some flash card format drivers. MMC/SD
  146. cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
  147. Interface support (MMC_TIFM_SD)'.
  148. To compile this driver as a module, choose M here: the module will
  149. be called tifm_core.
  150. config TIFM_7XX1
  151. tristate "TI Flash Media PCI74xx/PCI76xx host adapter support"
  152. depends on PCI && TIFM_CORE
  153. default TIFM_CORE
  154. help
  155. This option enables support for Texas Instruments(R) PCI74xx and
  156. PCI76xx families of Flash Media adapters, found in many laptops.
  157. To make actual use of the device, you will have to select some
  158. flash card format drivers, as outlined in the TIFM_CORE Help.
  159. To compile this driver as a module, choose M here: the module will
  160. be called tifm_7xx1.
  161. config ICS932S401
  162. tristate "Integrated Circuits ICS932S401"
  163. depends on I2C
  164. help
  165. If you say yes here you get support for the Integrated Circuits
  166. ICS932S401 clock control chips.
  167. This driver can also be built as a module. If so, the module
  168. will be called ics932s401.
  169. config ATMEL_SSC
  170. tristate "Device driver for Atmel SSC peripheral"
  171. depends on HAS_IOMEM
  172. ---help---
  173. This option enables device driver support for Atmel Synchronized
  174. Serial Communication peripheral (SSC).
  175. The SSC peripheral supports a wide variety of serial frame based
  176. communications, i.e. I2S, SPI, etc.
  177. If unsure, say N.
  178. config ENCLOSURE_SERVICES
  179. tristate "Enclosure Services"
  180. default n
  181. help
  182. Provides support for intelligent enclosures (bays which
  183. contain storage devices). You also need either a host
  184. driver (SCSI/ATA) which supports enclosures
  185. or a SCSI enclosure device (SES) to use these services.
  186. config SGI_XP
  187. tristate "Support communication between SGI SSIs"
  188. depends on NET
  189. depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
  190. select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
  191. select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
  192. select SGI_GRU if X86_64 && SMP
  193. ---help---
  194. An SGI machine can be divided into multiple Single System
  195. Images which act independently of each other and have
  196. hardware based memory protection from the others. Enabling
  197. this feature will allow for direct communication between SSIs
  198. based on a network adapter and DMA messaging.
  199. config CS5535_MFGPT
  200. tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
  201. depends on PCI && X86 && MFD_CS5535
  202. default n
  203. help
  204. This driver provides access to MFGPT functionality for other
  205. drivers that need timers. MFGPTs are available in the CS5535 and
  206. CS5536 companion chips that are found in AMD Geode and several
  207. other platforms. They have a better resolution and max interval
  208. than the generic PIT, and are suitable for use as high-res timers.
  209. You probably don't want to enable this manually; other drivers that
  210. make use of it should enable it.
  211. config CS5535_MFGPT_DEFAULT_IRQ
  212. int
  213. depends on CS5535_MFGPT
  214. default 7
  215. help
  216. MFGPTs on the CS5535 require an interrupt. The selected IRQ
  217. can be overridden as a module option as well as by driver that
  218. use the cs5535_mfgpt_ API; however, different architectures might
  219. want to use a different IRQ by default. This is here for
  220. architectures to set as necessary.
  221. config CS5535_CLOCK_EVENT_SRC
  222. tristate "CS5535/CS5536 high-res timer (MFGPT) events"
  223. depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
  224. help
  225. This driver provides a clock event source based on the MFGPT
  226. timer(s) in the CS5535 and CS5536 companion chips.
  227. MFGPTs have a better resolution and max interval than the
  228. generic PIT, and are suitable for use as high-res timers.
  229. config HP_ILO
  230. tristate "Channel interface driver for the HP iLO processor"
  231. depends on PCI
  232. default n
  233. help
  234. The channel interface driver allows applications to communicate
  235. with iLO management processors present on HP ProLiant servers.
  236. Upon loading, the driver creates /dev/hpilo/dXccbN files, which
  237. can be used to gather data from the management processor, via
  238. read and write system calls.
  239. To compile this driver as a module, choose M here: the
  240. module will be called hpilo.
  241. config SGI_GRU
  242. tristate "SGI GRU driver"
  243. depends on X86_UV && SMP
  244. default n
  245. select MMU_NOTIFIER
  246. ---help---
  247. The GRU is a hardware resource located in the system chipset. The GRU
  248. contains memory that can be mmapped into the user address space. This memory is
  249. used to communicate with the GRU to perform functions such as load/store,
  250. scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
  251. instructions using user virtual addresses. GRU instructions (ex., bcopy) use
  252. user virtual addresses for operands.
  253. If you are not running on a SGI UV system, say N.
  254. config SGI_GRU_DEBUG
  255. bool "SGI GRU driver debug"
  256. depends on SGI_GRU
  257. default n
  258. ---help---
  259. This option enables addition debugging code for the SGI GRU driver. If
  260. you are unsure, say N.
  261. config APDS9802ALS
  262. tristate "Medfield Avago APDS9802 ALS Sensor module"
  263. depends on I2C
  264. help
  265. If you say yes here you get support for the ALS APDS9802 ambient
  266. light sensor.
  267. This driver can also be built as a module. If so, the module
  268. will be called apds9802als.
  269. config ISL29003
  270. tristate "Intersil ISL29003 ambient light sensor"
  271. depends on I2C && SYSFS
  272. help
  273. If you say yes here you get support for the Intersil ISL29003
  274. ambient light sensor.
  275. This driver can also be built as a module. If so, the module
  276. will be called isl29003.
  277. config ISL29020
  278. tristate "Intersil ISL29020 ambient light sensor"
  279. depends on I2C
  280. help
  281. If you say yes here you get support for the Intersil ISL29020
  282. ambient light sensor.
  283. This driver can also be built as a module. If so, the module
  284. will be called isl29020.
  285. config SENSORS_TSL2550
  286. tristate "Taos TSL2550 ambient light sensor"
  287. depends on I2C && SYSFS
  288. help
  289. If you say yes here you get support for the Taos TSL2550
  290. ambient light sensor.
  291. This driver can also be built as a module. If so, the module
  292. will be called tsl2550.
  293. config SENSORS_BH1780
  294. tristate "ROHM BH1780GLI ambient light sensor"
  295. depends on I2C && SYSFS
  296. help
  297. If you say yes here you get support for the ROHM BH1780GLI
  298. ambient light sensor.
  299. This driver can also be built as a module. If so, the module
  300. will be called bh1780gli.
  301. config SENSORS_BH1770
  302. tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
  303. depends on I2C
  304. ---help---
  305. Say Y here if you want to build a driver for BH1770GLC (ROHM) or
  306. SFH7770 (Osram) combined ambient light and proximity sensor chip.
  307. To compile this driver as a module, choose M here: the
  308. module will be called bh1770glc. If unsure, say N here.
  309. config SENSORS_APDS990X
  310. tristate "APDS990X combined als and proximity sensors"
  311. depends on I2C
  312. default n
  313. ---help---
  314. Say Y here if you want to build a driver for Avago APDS990x
  315. combined ambient light and proximity sensor chip.
  316. To compile this driver as a module, choose M here: the
  317. module will be called apds990x. If unsure, say N here.
  318. config HMC6352
  319. tristate "Honeywell HMC6352 compass"
  320. depends on I2C
  321. help
  322. This driver provides support for the Honeywell HMC6352 compass,
  323. providing configuration and heading data via sysfs.
  324. config EP93XX_PWM
  325. tristate "EP93xx PWM support"
  326. depends on ARCH_EP93XX
  327. help
  328. This option enables device driver support for the PWM channels
  329. on the Cirrus EP93xx processors. The EP9307 chip only has one
  330. PWM channel all the others have two, the second channel is an
  331. alternate function of the EGPIO14 pin. A sysfs interface is
  332. provided to control the PWM channels.
  333. To compile this driver as a module, choose M here: the module will
  334. be called ep93xx_pwm.
  335. config DS1682
  336. tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
  337. depends on I2C
  338. help
  339. If you say yes here you get support for Dallas Semiconductor
  340. DS1682 Total Elapsed Time Recorder.
  341. This driver can also be built as a module. If so, the module
  342. will be called ds1682.
  343. config SPEAR13XX_PCIE_GADGET
  344. bool "PCIe gadget support for SPEAr13XX platform"
  345. depends on ARCH_SPEAR13XX && BROKEN
  346. default n
  347. help
  348. This option enables gadget support for PCIe controller. If
  349. board file defines any controller as PCIe endpoint then a sysfs
  350. entry will be created for that controller. User can use these
  351. sysfs node to configure PCIe EP as per his requirements.
  352. config TI_DAC7512
  353. tristate "Texas Instruments DAC7512"
  354. depends on SPI && SYSFS
  355. help
  356. If you say yes here you get support for the Texas Instruments
  357. DAC7512 16-bit digital-to-analog converter.
  358. This driver can also be built as a module. If so, the module
  359. will be called ti_dac7512.
  360. config VMWARE_BALLOON
  361. tristate "VMware Balloon Driver"
  362. depends on X86 && HYPERVISOR_GUEST
  363. help
  364. This is VMware physical memory management driver which acts
  365. like a "balloon" that can be inflated to reclaim physical pages
  366. by reserving them in the guest and invalidating them in the
  367. monitor, freeing up the underlying machine pages so they can
  368. be allocated to other guests. The balloon can also be deflated
  369. to allow the guest to use more physical memory.
  370. If unsure, say N.
  371. To compile this driver as a module, choose M here: the
  372. module will be called vmw_balloon.
  373. config ARM_CHARLCD
  374. bool "ARM Ltd. Character LCD Driver"
  375. depends on PLAT_VERSATILE
  376. help
  377. This is a driver for the character LCD found on the ARM Ltd.
  378. Versatile and RealView Platform Baseboards. It doesn't do
  379. very much more than display the text "ARM Linux" on the first
  380. line and the Linux version on the second line, but that's
  381. still useful.
  382. config BMP085
  383. bool
  384. depends on SYSFS
  385. config BMP085_I2C
  386. tristate "BMP085 digital pressure sensor on I2C"
  387. select BMP085
  388. select REGMAP_I2C
  389. depends on I2C && SYSFS
  390. help
  391. Say Y here if you want to support Bosch Sensortec's digital pressure
  392. sensor hooked to an I2C bus.
  393. To compile this driver as a module, choose M here: the
  394. module will be called bmp085-i2c.
  395. config BMP085_SPI
  396. tristate "BMP085 digital pressure sensor on SPI"
  397. select BMP085
  398. select REGMAP_SPI
  399. depends on SPI_MASTER && SYSFS
  400. help
  401. Say Y here if you want to support Bosch Sensortec's digital pressure
  402. sensor hooked to an SPI bus.
  403. To compile this driver as a module, choose M here: the
  404. module will be called bmp085-spi.
  405. config PCH_PHUB
  406. tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
  407. depends on PCI
  408. help
  409. This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
  410. Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
  411. processor. The Topcliff has MAC address and Option ROM data in SROM.
  412. This driver can access MAC address and Option ROM data in SROM.
  413. This driver also can be used for LAPIS Semiconductor's IOH,
  414. ML7213/ML7223/ML7831.
  415. ML7213 which is for IVI(In-Vehicle Infotainment) use.
  416. ML7223 IOH is for MP(Media Phone) use.
  417. ML7831 IOH is for general purpose use.
  418. ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
  419. ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
  420. To compile this driver as a module, choose M here: the module will
  421. be called pch_phub.
  422. config USB_SWITCH_FSA9480
  423. tristate "FSA9480 USB Switch"
  424. depends on I2C
  425. help
  426. The FSA9480 is a USB port accessory detector and switch.
  427. The FSA9480 is fully controlled using I2C and enables USB data,
  428. stereo and mono audio, video, microphone and UART data to use
  429. a common connector port.
  430. config LATTICE_ECP3_CONFIG
  431. tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
  432. depends on SPI && SYSFS
  433. select FW_LOADER
  434. default n
  435. help
  436. This option enables support for bitstream configuration (programming
  437. or loading) of the Lattice ECP3 FPGA family via SPI.
  438. If unsure, say N.
  439. config SRAM
  440. bool "Generic on-chip SRAM driver"
  441. depends on HAS_IOMEM
  442. select GENERIC_ALLOCATOR
  443. help
  444. This driver allows you to declare a memory region to be managed by
  445. the genalloc API. It is supposed to be used for small on-chip SRAM
  446. areas found on many SoCs.
  447. source "drivers/misc/c2port/Kconfig"
  448. source "drivers/misc/eeprom/Kconfig"
  449. source "drivers/misc/cb710/Kconfig"
  450. source "drivers/misc/ti-st/Kconfig"
  451. source "drivers/misc/lis3lv02d/Kconfig"
  452. source "drivers/misc/carma/Kconfig"
  453. source "drivers/misc/altera-stapl/Kconfig"
  454. source "drivers/misc/mei/Kconfig"
  455. source "drivers/misc/vmw_vmci/Kconfig"
  456. endmenu