Kconfig 18 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540
  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_TCLIB
  44. bool "Atmel AT32/AT91 Timer/Counter Library"
  45. depends on (AVR32 || ARCH_AT91)
  46. help
  47. Select this if you want a library to allocate the Timer/Counter
  48. blocks found on many Atmel processors. This facilitates using
  49. these blocks by different drivers despite processor differences.
  50. config ATMEL_TCB_CLKSRC
  51. bool "TC Block Clocksource"
  52. depends on ATMEL_TCLIB
  53. default y
  54. help
  55. Select this to get a high precision clocksource based on a
  56. TC block with a 5+ MHz base clock rate. Two timer channels
  57. are combined to make a single 32-bit timer.
  58. When GENERIC_CLOCKEVENTS is defined, the third timer channel
  59. may be used as a clock event device supporting oneshot mode
  60. (delays of up to two seconds) based on the 32 KiHz clock.
  61. config ATMEL_TCB_CLKSRC_BLOCK
  62. int
  63. depends on ATMEL_TCB_CLKSRC
  64. prompt "TC Block" if CPU_AT32AP700X
  65. default 0
  66. range 0 1
  67. help
  68. Some chips provide more than one TC block, so you have the
  69. choice of which one to use for the clock framework. The other
  70. TC can be used for other purposes, such as PWM generation and
  71. interval timing.
  72. config DUMMY_IRQ
  73. tristate "Dummy IRQ handler"
  74. default n
  75. ---help---
  76. This module accepts a single 'irq' parameter, which it should register for.
  77. The sole purpose of this module is to help with debugging of systems on
  78. which spurious IRQs would happen on disabled IRQ vector.
  79. config IBM_ASM
  80. tristate "Device driver for IBM RSA service processor"
  81. depends on X86 && PCI && INPUT
  82. ---help---
  83. This option enables device driver support for in-band access to the
  84. IBM RSA (Condor) service processor in eServer xSeries systems.
  85. The ibmasm device driver allows user space application to access
  86. ASM (Advanced Systems Management) functions on the service
  87. processor. The driver is meant to be used in conjunction with
  88. a user space API.
  89. The ibmasm driver also enables the OS to use the UART on the
  90. service processor board as a regular serial port. To make use of
  91. this feature serial driver support (CONFIG_SERIAL_8250) must be
  92. enabled.
  93. WARNING: This software may not be supported or function
  94. correctly on your IBM server. Please consult the IBM ServerProven
  95. website <http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>
  96. for information on the specific driver level and support statement
  97. for your IBM server.
  98. config PHANTOM
  99. tristate "Sensable PHANToM (PCI)"
  100. depends on PCI
  101. help
  102. Say Y here if you want to build a driver for Sensable PHANToM device.
  103. This driver is only for PCI PHANToMs.
  104. If you choose to build module, its name will be phantom. If unsure,
  105. say N here.
  106. config INTEL_MID_PTI
  107. tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard"
  108. depends on PCI && TTY && (X86_INTEL_MID || COMPILE_TEST)
  109. default n
  110. help
  111. The PTI (Parallel Trace Interface) driver directs
  112. trace data routed from various parts in the system out
  113. through an Intel Penwell PTI port and out of the mobile
  114. device for analysis with a debugging tool (Lauterbach or Fido).
  115. You should select this driver if the target kernel is meant for
  116. an Intel Atom (non-netbook) mobile device containing a MIPI
  117. P1149.7 standard implementation.
  118. config SGI_IOC4
  119. tristate "SGI IOC4 Base IO support"
  120. depends on PCI
  121. ---help---
  122. This option enables basic support for the IOC4 chip on certain
  123. SGI IO controller cards (IO9, IO10, and PCI-RT). This option
  124. does not enable any specific functions on such a card, but provides
  125. necessary infrastructure for other drivers to utilize.
  126. If you have an SGI Altix with an IOC4-based card say Y.
  127. Otherwise say N.
  128. config TIFM_CORE
  129. tristate "TI Flash Media interface support"
  130. depends on PCI
  131. help
  132. If you want support for Texas Instruments(R) Flash Media adapters
  133. you should select this option and then also choose an appropriate
  134. host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
  135. support', if you have a TI PCI74xx compatible card reader, for
  136. example.
  137. You will also have to select some flash card format drivers. MMC/SD
  138. cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
  139. Interface support (MMC_TIFM_SD)'.
  140. To compile this driver as a module, choose M here: the module will
  141. be called tifm_core.
  142. config TIFM_7XX1
  143. tristate "TI Flash Media PCI74xx/PCI76xx host adapter support"
  144. depends on PCI && TIFM_CORE
  145. default TIFM_CORE
  146. help
  147. This option enables support for Texas Instruments(R) PCI74xx and
  148. PCI76xx families of Flash Media adapters, found in many laptops.
  149. To make actual use of the device, you will have to select some
  150. flash card format drivers, as outlined in the TIFM_CORE Help.
  151. To compile this driver as a module, choose M here: the module will
  152. be called tifm_7xx1.
  153. config ICS932S401
  154. tristate "Integrated Circuits ICS932S401"
  155. depends on I2C
  156. help
  157. If you say yes here you get support for the Integrated Circuits
  158. ICS932S401 clock control chips.
  159. This driver can also be built as a module. If so, the module
  160. will be called ics932s401.
  161. config ATMEL_SSC
  162. tristate "Device driver for Atmel SSC peripheral"
  163. depends on HAS_IOMEM && (AVR32 || ARCH_AT91 || COMPILE_TEST)
  164. ---help---
  165. This option enables device driver support for Atmel Synchronized
  166. Serial Communication peripheral (SSC).
  167. The SSC peripheral supports a wide variety of serial frame based
  168. communications, i.e. I2S, SPI, etc.
  169. If unsure, say N.
  170. config ENCLOSURE_SERVICES
  171. tristate "Enclosure Services"
  172. default n
  173. help
  174. Provides support for intelligent enclosures (bays which
  175. contain storage devices). You also need either a host
  176. driver (SCSI/ATA) which supports enclosures
  177. or a SCSI enclosure device (SES) to use these services.
  178. config SGI_XP
  179. tristate "Support communication between SGI SSIs"
  180. depends on NET
  181. depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
  182. select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
  183. select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
  184. select SGI_GRU if X86_64 && SMP
  185. ---help---
  186. An SGI machine can be divided into multiple Single System
  187. Images which act independently of each other and have
  188. hardware based memory protection from the others. Enabling
  189. this feature will allow for direct communication between SSIs
  190. based on a network adapter and DMA messaging.
  191. config CS5535_MFGPT
  192. tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
  193. depends on MFD_CS5535
  194. default n
  195. help
  196. This driver provides access to MFGPT functionality for other
  197. drivers that need timers. MFGPTs are available in the CS5535 and
  198. CS5536 companion chips that are found in AMD Geode and several
  199. other platforms. They have a better resolution and max interval
  200. than the generic PIT, and are suitable for use as high-res timers.
  201. You probably don't want to enable this manually; other drivers that
  202. make use of it should enable it.
  203. config CS5535_MFGPT_DEFAULT_IRQ
  204. int
  205. depends on CS5535_MFGPT
  206. default 7
  207. help
  208. MFGPTs on the CS5535 require an interrupt. The selected IRQ
  209. can be overridden as a module option as well as by driver that
  210. use the cs5535_mfgpt_ API; however, different architectures might
  211. want to use a different IRQ by default. This is here for
  212. architectures to set as necessary.
  213. config CS5535_CLOCK_EVENT_SRC
  214. tristate "CS5535/CS5536 high-res timer (MFGPT) events"
  215. depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
  216. help
  217. This driver provides a clock event source based on the MFGPT
  218. timer(s) in the CS5535 and CS5536 companion chips.
  219. MFGPTs have a better resolution and max interval than the
  220. generic PIT, and are suitable for use as high-res timers.
  221. config HP_ILO
  222. tristate "Channel interface driver for the HP iLO processor"
  223. depends on PCI
  224. default n
  225. help
  226. The channel interface driver allows applications to communicate
  227. with iLO management processors present on HP ProLiant servers.
  228. Upon loading, the driver creates /dev/hpilo/dXccbN files, which
  229. can be used to gather data from the management processor, via
  230. read and write system calls.
  231. To compile this driver as a module, choose M here: the
  232. module will be called hpilo.
  233. config QCOM_COINCELL
  234. tristate "Qualcomm coincell charger support"
  235. depends on MFD_SPMI_PMIC || COMPILE_TEST
  236. help
  237. This driver supports the coincell block found inside of
  238. Qualcomm PMICs. The coincell charger provides a means to
  239. charge a coincell battery or backup capacitor which is used
  240. to maintain PMIC register and RTC state in the absence of
  241. external power.
  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 additional debugging code for the SGI GRU driver.
  261. If 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 DS1682
  326. tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
  327. depends on I2C
  328. help
  329. If you say yes here you get support for Dallas Semiconductor
  330. DS1682 Total Elapsed Time Recorder.
  331. This driver can also be built as a module. If so, the module
  332. will be called ds1682.
  333. config SPEAR13XX_PCIE_GADGET
  334. bool "PCIe gadget support for SPEAr13XX platform"
  335. depends on ARCH_SPEAR13XX && BROKEN
  336. default n
  337. help
  338. This option enables gadget support for PCIe controller. If
  339. board file defines any controller as PCIe endpoint then a sysfs
  340. entry will be created for that controller. User can use these
  341. sysfs node to configure PCIe EP as per his requirements.
  342. config TI_DAC7512
  343. tristate "Texas Instruments DAC7512"
  344. depends on SPI && SYSFS
  345. help
  346. If you say yes here you get support for the Texas Instruments
  347. DAC7512 16-bit digital-to-analog converter.
  348. This driver can also be built as a module. If so, the module
  349. will be called ti_dac7512.
  350. config VMWARE_BALLOON
  351. tristate "VMware Balloon Driver"
  352. depends on VMWARE_VMCI && X86 && HYPERVISOR_GUEST
  353. help
  354. This is VMware physical memory management driver which acts
  355. like a "balloon" that can be inflated to reclaim physical pages
  356. by reserving them in the guest and invalidating them in the
  357. monitor, freeing up the underlying machine pages so they can
  358. be allocated to other guests. The balloon can also be deflated
  359. to allow the guest to use more physical memory.
  360. If unsure, say N.
  361. To compile this driver as a module, choose M here: the
  362. module will be called vmw_balloon.
  363. config ARM_CHARLCD
  364. bool "ARM Ltd. Character LCD Driver"
  365. depends on PLAT_VERSATILE
  366. help
  367. This is a driver for the character LCD found on the ARM Ltd.
  368. Versatile and RealView Platform Baseboards. It doesn't do
  369. very much more than display the text "ARM Linux" on the first
  370. line and the Linux version on the second line, but that's
  371. still useful.
  372. config BMP085
  373. tristate
  374. depends on SYSFS
  375. config BMP085_I2C
  376. tristate "BMP085 digital pressure sensor on I2C"
  377. select BMP085
  378. select REGMAP_I2C
  379. depends on I2C && SYSFS
  380. help
  381. Say Y here if you want to support Bosch Sensortec's digital pressure
  382. sensor hooked to an I2C bus.
  383. To compile this driver as a module, choose M here: the
  384. module will be called bmp085-i2c.
  385. config BMP085_SPI
  386. tristate "BMP085 digital pressure sensor on SPI"
  387. select BMP085
  388. select REGMAP_SPI
  389. depends on SPI_MASTER && SYSFS
  390. help
  391. Say Y here if you want to support Bosch Sensortec's digital pressure
  392. sensor hooked to an SPI bus.
  393. To compile this driver as a module, choose M here: the
  394. module will be called bmp085-spi.
  395. config PCH_PHUB
  396. tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
  397. select GENERIC_NET_UTILS
  398. depends on PCI && (X86_32 || COMPILE_TEST)
  399. help
  400. This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
  401. Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
  402. processor. The Topcliff has MAC address and Option ROM data in SROM.
  403. This driver can access MAC address and Option ROM data in SROM.
  404. This driver also can be used for LAPIS Semiconductor's IOH,
  405. ML7213/ML7223/ML7831.
  406. ML7213 which is for IVI(In-Vehicle Infotainment) use.
  407. ML7223 IOH is for MP(Media Phone) use.
  408. ML7831 IOH is for general purpose use.
  409. ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
  410. ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
  411. To compile this driver as a module, choose M here: the module will
  412. be called pch_phub.
  413. config USB_SWITCH_FSA9480
  414. tristate "FSA9480 USB Switch"
  415. depends on I2C
  416. help
  417. The FSA9480 is a USB port accessory detector and switch.
  418. The FSA9480 is fully controlled using I2C and enables USB data,
  419. stereo and mono audio, video, microphone and UART data to use
  420. a common connector port.
  421. config LATTICE_ECP3_CONFIG
  422. tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
  423. depends on SPI && SYSFS
  424. select FW_LOADER
  425. default n
  426. help
  427. This option enables support for bitstream configuration (programming
  428. or loading) of the Lattice ECP3 FPGA family via SPI.
  429. If unsure, say N.
  430. config SRAM
  431. bool "Generic on-chip SRAM driver"
  432. depends on HAS_IOMEM
  433. select GENERIC_ALLOCATOR
  434. help
  435. This driver allows you to declare a memory region to be managed by
  436. the genalloc API. It is supposed to be used for small on-chip SRAM
  437. areas found on many SoCs.
  438. config VEXPRESS_SYSCFG
  439. bool "Versatile Express System Configuration driver"
  440. depends on VEXPRESS_CONFIG
  441. default y
  442. help
  443. ARM Ltd. Versatile Express uses specialised platform configuration
  444. bus. System Configuration interface is one of the possible means
  445. of generating transactions on this bus.
  446. source "drivers/misc/c2port/Kconfig"
  447. source "drivers/misc/eeprom/Kconfig"
  448. source "drivers/misc/cb710/Kconfig"
  449. source "drivers/misc/ti-st/Kconfig"
  450. source "drivers/misc/lis3lv02d/Kconfig"
  451. source "drivers/misc/altera-stapl/Kconfig"
  452. source "drivers/misc/mei/Kconfig"
  453. source "drivers/misc/vmw_vmci/Kconfig"
  454. source "drivers/misc/mic/Kconfig"
  455. source "drivers/misc/genwqe/Kconfig"
  456. source "drivers/misc/echo/Kconfig"
  457. source "drivers/misc/cxl/Kconfig"
  458. endmenu