Kconfig 17 KB

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