Kconfig 18 KB

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