Kconfig 18 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531
  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 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. default 0
  65. range 0 1
  66. help
  67. Some chips provide more than one TC block, so you have the
  68. choice of which one to use for the clock framework. The other
  69. TC can be used for other purposes, such as PWM generation and
  70. interval timing.
  71. config DUMMY_IRQ
  72. tristate "Dummy IRQ handler"
  73. default n
  74. ---help---
  75. This module accepts a single 'irq' parameter, which it should register for.
  76. The sole purpose of this module is to help with debugging of systems on
  77. which spurious IRQs would happen on disabled IRQ vector.
  78. config IBM_ASM
  79. tristate "Device driver for IBM RSA service processor"
  80. depends on X86 && PCI && INPUT
  81. depends on SERIAL_8250 || SERIAL_8250=n
  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 IBMVMC
  99. tristate "IBM Virtual Management Channel support"
  100. depends on PPC_PSERIES
  101. help
  102. This is the IBM POWER Virtual Management Channel
  103. This driver is to be used for the POWER Virtual
  104. Management Channel virtual adapter on the PowerVM
  105. platform. It provides both request/response and
  106. async message support through the /dev/ibmvmc node.
  107. To compile this driver as a module, choose M here: the
  108. module will be called ibmvmc.
  109. config PHANTOM
  110. tristate "Sensable PHANToM (PCI)"
  111. depends on PCI
  112. help
  113. Say Y here if you want to build a driver for Sensable PHANToM device.
  114. This driver is only for PCI PHANToMs.
  115. If you choose to build module, its name will be phantom. If unsure,
  116. say N here.
  117. config INTEL_MID_PTI
  118. tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard"
  119. depends on PCI && TTY && (X86_INTEL_MID || COMPILE_TEST)
  120. default n
  121. help
  122. The PTI (Parallel Trace Interface) driver directs
  123. trace data routed from various parts in the system out
  124. through an Intel Penwell PTI port and out of the mobile
  125. device for analysis with a debugging tool (Lauterbach or Fido).
  126. You should select this driver if the target kernel is meant for
  127. an Intel Atom (non-netbook) mobile device containing a MIPI
  128. P1149.7 standard implementation.
  129. config SGI_IOC4
  130. tristate "SGI IOC4 Base IO support"
  131. depends on PCI
  132. ---help---
  133. This option enables basic support for the IOC4 chip on certain
  134. SGI IO controller cards (IO9, IO10, and PCI-RT). This option
  135. does not enable any specific functions on such a card, but provides
  136. necessary infrastructure for other drivers to utilize.
  137. If you have an SGI Altix with an IOC4-based card say Y.
  138. Otherwise say N.
  139. config TIFM_CORE
  140. tristate "TI Flash Media interface support"
  141. depends on PCI
  142. help
  143. If you want support for Texas Instruments(R) Flash Media adapters
  144. you should select this option and then also choose an appropriate
  145. host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
  146. support', if you have a TI PCI74xx compatible card reader, for
  147. example.
  148. You will also have to select some flash card format drivers. MMC/SD
  149. cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
  150. Interface support (MMC_TIFM_SD)'.
  151. To compile this driver as a module, choose M here: the module will
  152. be called tifm_core.
  153. config TIFM_7XX1
  154. tristate "TI Flash Media PCI74xx/PCI76xx host adapter support"
  155. depends on PCI && TIFM_CORE
  156. default TIFM_CORE
  157. help
  158. This option enables support for Texas Instruments(R) PCI74xx and
  159. PCI76xx families of Flash Media adapters, found in many laptops.
  160. To make actual use of the device, you will have to select some
  161. flash card format drivers, as outlined in the TIFM_CORE Help.
  162. To compile this driver as a module, choose M here: the module will
  163. be called tifm_7xx1.
  164. config ICS932S401
  165. tristate "Integrated Circuits ICS932S401"
  166. depends on I2C
  167. help
  168. If you say yes here you get support for the Integrated Circuits
  169. ICS932S401 clock control chips.
  170. This driver can also be built as a module. If so, the module
  171. will be called ics932s401.
  172. config ATMEL_SSC
  173. tristate "Device driver for Atmel SSC peripheral"
  174. depends on HAS_IOMEM && (ARCH_AT91 || COMPILE_TEST)
  175. ---help---
  176. This option enables device driver support for Atmel Synchronized
  177. Serial Communication peripheral (SSC).
  178. The SSC peripheral supports a wide variety of serial frame based
  179. communications, i.e. I2S, SPI, etc.
  180. If unsure, say N.
  181. config ENCLOSURE_SERVICES
  182. tristate "Enclosure Services"
  183. default n
  184. help
  185. Provides support for intelligent enclosures (bays which
  186. contain storage devices). You also need either a host
  187. driver (SCSI/ATA) which supports enclosures
  188. or a SCSI enclosure device (SES) to use these services.
  189. config SGI_XP
  190. tristate "Support communication between SGI SSIs"
  191. depends on NET
  192. depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
  193. select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
  194. select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
  195. select SGI_GRU if X86_64 && SMP
  196. ---help---
  197. An SGI machine can be divided into multiple Single System
  198. Images which act independently of each other and have
  199. hardware based memory protection from the others. Enabling
  200. this feature will allow for direct communication between SSIs
  201. based on a network adapter and DMA messaging.
  202. config CS5535_MFGPT
  203. tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
  204. depends on MFD_CS5535
  205. default n
  206. help
  207. This driver provides access to MFGPT functionality for other
  208. drivers that need timers. MFGPTs are available in the CS5535 and
  209. CS5536 companion chips that are found in AMD Geode and several
  210. other platforms. They have a better resolution and max interval
  211. than the generic PIT, and are suitable for use as high-res timers.
  212. You probably don't want to enable this manually; other drivers that
  213. make use of it should enable it.
  214. config CS5535_MFGPT_DEFAULT_IRQ
  215. int
  216. depends on CS5535_MFGPT
  217. default 7
  218. help
  219. MFGPTs on the CS5535 require an interrupt. The selected IRQ
  220. can be overridden as a module option as well as by driver that
  221. use the cs5535_mfgpt_ API; however, different architectures might
  222. want to use a different IRQ by default. This is here for
  223. architectures to set as necessary.
  224. config CS5535_CLOCK_EVENT_SRC
  225. tristate "CS5535/CS5536 high-res timer (MFGPT) events"
  226. depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
  227. help
  228. This driver provides a clock event source based on the MFGPT
  229. timer(s) in the CS5535 and CS5536 companion chips.
  230. MFGPTs have a better resolution and max interval than the
  231. generic PIT, and are suitable for use as high-res timers.
  232. config HP_ILO
  233. tristate "Channel interface driver for the HP iLO processor"
  234. depends on PCI
  235. default n
  236. help
  237. The channel interface driver allows applications to communicate
  238. with iLO management processors present on HP ProLiant servers.
  239. Upon loading, the driver creates /dev/hpilo/dXccbN files, which
  240. can be used to gather data from the management processor, via
  241. read and write system calls.
  242. To compile this driver as a module, choose M here: the
  243. module will be called hpilo.
  244. config QCOM_COINCELL
  245. tristate "Qualcomm coincell charger support"
  246. depends on MFD_SPMI_PMIC || COMPILE_TEST
  247. help
  248. This driver supports the coincell block found inside of
  249. Qualcomm PMICs. The coincell charger provides a means to
  250. charge a coincell battery or backup capacitor which is used
  251. to maintain PMIC register and RTC state in the absence of
  252. external power.
  253. config SGI_GRU
  254. tristate "SGI GRU driver"
  255. depends on X86_UV && SMP
  256. default n
  257. select MMU_NOTIFIER
  258. ---help---
  259. The GRU is a hardware resource located in the system chipset. The GRU
  260. contains memory that can be mmapped into the user address space. This memory is
  261. used to communicate with the GRU to perform functions such as load/store,
  262. scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
  263. instructions using user virtual addresses. GRU instructions (ex., bcopy) use
  264. user virtual addresses for operands.
  265. If you are not running on a SGI UV system, say N.
  266. config SGI_GRU_DEBUG
  267. bool "SGI GRU driver debug"
  268. depends on SGI_GRU
  269. default n
  270. ---help---
  271. This option enables additional debugging code for the SGI GRU driver.
  272. If you are unsure, say N.
  273. config APDS9802ALS
  274. tristate "Medfield Avago APDS9802 ALS Sensor module"
  275. depends on I2C
  276. help
  277. If you say yes here you get support for the ALS APDS9802 ambient
  278. light sensor.
  279. This driver can also be built as a module. If so, the module
  280. will be called apds9802als.
  281. config ISL29003
  282. tristate "Intersil ISL29003 ambient light sensor"
  283. depends on I2C && SYSFS
  284. help
  285. If you say yes here you get support for the Intersil ISL29003
  286. ambient light sensor.
  287. This driver can also be built as a module. If so, the module
  288. will be called isl29003.
  289. config ISL29020
  290. tristate "Intersil ISL29020 ambient light sensor"
  291. depends on I2C
  292. help
  293. If you say yes here you get support for the Intersil ISL29020
  294. ambient light sensor.
  295. This driver can also be built as a module. If so, the module
  296. will be called isl29020.
  297. config SENSORS_TSL2550
  298. tristate "Taos TSL2550 ambient light sensor"
  299. depends on I2C && SYSFS
  300. help
  301. If you say yes here you get support for the Taos TSL2550
  302. ambient light sensor.
  303. This driver can also be built as a module. If so, the module
  304. will be called tsl2550.
  305. config SENSORS_BH1770
  306. tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
  307. depends on I2C
  308. ---help---
  309. Say Y here if you want to build a driver for BH1770GLC (ROHM) or
  310. SFH7770 (Osram) combined ambient light and proximity sensor chip.
  311. To compile this driver as a module, choose M here: the
  312. module will be called bh1770glc. If unsure, say N here.
  313. config SENSORS_APDS990X
  314. tristate "APDS990X combined als and proximity sensors"
  315. depends on I2C
  316. default n
  317. ---help---
  318. Say Y here if you want to build a driver for Avago APDS990x
  319. combined ambient light and proximity sensor chip.
  320. To compile this driver as a module, choose M here: the
  321. module will be called apds990x. If unsure, say N here.
  322. config HMC6352
  323. tristate "Honeywell HMC6352 compass"
  324. depends on I2C
  325. help
  326. This driver provides support for the Honeywell HMC6352 compass,
  327. providing configuration and heading data via sysfs.
  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 && BROKEN
  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 VMWARE_BALLOON
  346. tristate "VMware Balloon Driver"
  347. depends on VMWARE_VMCI && X86 && HYPERVISOR_GUEST
  348. help
  349. This is VMware physical memory management driver which acts
  350. like a "balloon" that can be inflated to reclaim physical pages
  351. by reserving them in the guest and invalidating them in the
  352. monitor, freeing up the underlying machine pages so they can
  353. be allocated to other guests. The balloon can also be deflated
  354. to allow the guest to use more physical memory.
  355. If unsure, say N.
  356. To compile this driver as a module, choose M here: the
  357. module will be called vmw_balloon.
  358. config PCH_PHUB
  359. tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
  360. select GENERIC_NET_UTILS
  361. depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
  362. help
  363. This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
  364. Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
  365. processor. The Topcliff has MAC address and Option ROM data in SROM.
  366. This driver can access MAC address and Option ROM data in SROM.
  367. This driver also can be used for LAPIS Semiconductor's IOH,
  368. ML7213/ML7223/ML7831.
  369. ML7213 which is for IVI(In-Vehicle Infotainment) use.
  370. ML7223 IOH is for MP(Media Phone) use.
  371. ML7831 IOH is for general purpose use.
  372. ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
  373. ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
  374. To compile this driver as a module, choose M here: the module will
  375. be called pch_phub.
  376. config USB_SWITCH_FSA9480
  377. tristate "FSA9480 USB Switch"
  378. depends on I2C
  379. help
  380. The FSA9480 is a USB port accessory detector and switch.
  381. The FSA9480 is fully controlled using I2C and enables USB data,
  382. stereo and mono audio, video, microphone and UART data to use
  383. a common connector port.
  384. config LATTICE_ECP3_CONFIG
  385. tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
  386. depends on SPI && SYSFS
  387. select FW_LOADER
  388. default n
  389. help
  390. This option enables support for bitstream configuration (programming
  391. or loading) of the Lattice ECP3 FPGA family via SPI.
  392. If unsure, say N.
  393. config SRAM
  394. bool "Generic on-chip SRAM driver"
  395. depends on HAS_IOMEM
  396. select GENERIC_ALLOCATOR
  397. select SRAM_EXEC if ARM
  398. help
  399. This driver allows you to declare a memory region to be managed by
  400. the genalloc API. It is supposed to be used for small on-chip SRAM
  401. areas found on many SoCs.
  402. config SRAM_EXEC
  403. bool
  404. config VEXPRESS_SYSCFG
  405. bool "Versatile Express System Configuration driver"
  406. depends on VEXPRESS_CONFIG
  407. default y
  408. help
  409. ARM Ltd. Versatile Express uses specialised platform configuration
  410. bus. System Configuration interface is one of the possible means
  411. of generating transactions on this bus.
  412. config ASPEED_LPC_CTRL
  413. depends on (ARCH_ASPEED || COMPILE_TEST) && REGMAP && MFD_SYSCON
  414. tristate "Aspeed ast2400/2500 HOST LPC to BMC bridge control"
  415. ---help---
  416. Control Aspeed ast2400/2500 HOST LPC to BMC mappings through
  417. ioctl()s, the driver also provides a read/write interface to a BMC ram
  418. region where the host LPC read/write region can be buffered.
  419. config ASPEED_LPC_SNOOP
  420. tristate "Aspeed ast2500 HOST LPC snoop support"
  421. depends on (ARCH_ASPEED || COMPILE_TEST) && REGMAP && MFD_SYSCON
  422. help
  423. Provides a driver to control the LPC snoop interface which
  424. allows the BMC to listen on and save the data written by
  425. the host to an arbitrary LPC I/O port.
  426. config PCI_ENDPOINT_TEST
  427. depends on PCI
  428. select CRC32
  429. tristate "PCI Endpoint Test driver"
  430. ---help---
  431. Enable this configuration option to enable the host side test driver
  432. for PCI Endpoint.
  433. config MISC_RTSX
  434. tristate
  435. default MISC_RTSX_PCI || MISC_RTSX_USB
  436. source "drivers/misc/c2port/Kconfig"
  437. source "drivers/misc/eeprom/Kconfig"
  438. source "drivers/misc/cb710/Kconfig"
  439. source "drivers/misc/ti-st/Kconfig"
  440. source "drivers/misc/lis3lv02d/Kconfig"
  441. source "drivers/misc/altera-stapl/Kconfig"
  442. source "drivers/misc/mei/Kconfig"
  443. source "drivers/misc/vmw_vmci/Kconfig"
  444. source "drivers/misc/mic/Kconfig"
  445. source "drivers/misc/genwqe/Kconfig"
  446. source "drivers/misc/echo/Kconfig"
  447. source "drivers/misc/cxl/Kconfig"
  448. source "drivers/misc/ocxl/Kconfig"
  449. source "drivers/misc/cardreader/Kconfig"
  450. endmenu