Kconfig 18 KB

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