Kconfig 15.6 KB
Newer Older
L
Linus Torvalds 已提交
1 2 3 4
#
# Misc strange devices
#

R
Randy Dunlap 已提交
5
menuconfig MISC_DEVICES
6
	bool "Misc devices"
7 8 9 10 11
	---help---
	  Say Y here to get to see options for device drivers from various
	  different categories. This option alone does not add any kernel code.

	  If you say N, all options in this submenu will be skipped and disabled.
12

R
Randy Dunlap 已提交
13
if MISC_DEVICES
L
Linus Torvalds 已提交
14

15
config AD525X_DPOT
16 17
	tristate "Analog Devices Digital Potentiometers"
	depends on (I2C || SPI) && SYSFS
18 19
	help
	  If you say yes here, you get support for the Analog Devices
20 21 22 23
	  AD5258, AD5259, AD5251, AD5252, AD5253, AD5254, AD5255
	  AD5160, AD5161, AD5162, AD5165, AD5200, AD5201, AD5203,
	  AD5204, AD5206, AD5207, AD5231, AD5232, AD5233, AD5235,
	  AD5260, AD5262, AD5263, AD5290, AD5291, AD5292, AD5293,
24
	  AD7376, AD8400, AD8402, AD8403, ADN2850, AD5241, AD5242,
25
	  AD5243, AD5245, AD5246, AD5247, AD5248, AD5280, AD5282,
26 27
	  ADN2860, AD5273, AD5171, AD5170, AD5172, AD5173, AD5270,
	  AD5271, AD5272, AD5274
28 29 30 31 32 33 34 35
	  digital potentiometer chips.

	  See Documentation/misc-devices/ad525x_dpot.txt for the
	  userspace interface.

	  This driver can also be built as a module.  If so, the module
	  will be called ad525x_dpot.

36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55
config AD525X_DPOT_I2C
	tristate "support I2C bus connection"
	depends on AD525X_DPOT && I2C
	help
	  Say Y here if you have a digital potentiometers hooked to an I2C bus.

	  To compile this driver as a module, choose M here: the
	  module will be called ad525x_dpot-i2c.

config AD525X_DPOT_SPI
	tristate "support SPI bus connection"
	depends on AD525X_DPOT && SPI_MASTER
	help
	  Say Y here if you have a digital potentiometers hooked to an SPI bus.

	  If unsure, say N (but it's safe to say "Y").

	  To compile this driver as a module, choose M here: the
	  module will be called ad525x_dpot-spi.

56 57
config ATMEL_PWM
	tristate "Atmel AT32/AT91 PWM support"
58
	depends on AVR32 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9
59 60
	help
	  This option enables device driver support for the PWM channels
61 62
	  on certain Atmel processors.  Pulse Width Modulation is used for
	  purposes including software controlled power-efficient backlights
63 64
	  on LCD displays, motor control, and waveform generation.

A
Arun Murthy 已提交
65 66 67 68 69 70 71 72 73
config AB8500_PWM
	bool "AB8500 PWM support"
	depends on AB8500_CORE
	select HAVE_PWM
	help
	  This driver exports functions to enable/disble/config/free Pulse
	  Width Modulation in the Analog Baseband Chip AB8500.
	  It is used by led and backlight driver to control the intensity.

D
David Brownell 已提交
74 75 76 77 78 79 80 81
config ATMEL_TCLIB
	bool "Atmel AT32/AT91 Timer/Counter Library"
	depends on (AVR32 || ARCH_AT91)
	help
	  Select this if you want a library to allocate the Timer/Counter
	  blocks found on many Atmel processors.  This facilitates using
	  these blocks by different drivers despite processor differences.

82 83
config ATMEL_TCB_CLKSRC
	bool "TC Block Clocksource"
J
John Stultz 已提交
84
	depends on ATMEL_TCLIB
85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106
	default y
	help
	  Select this to get a high precision clocksource based on a
	  TC block with a 5+ MHz base clock rate.  Two timer channels
	  are combined to make a single 32-bit timer.

	  When GENERIC_CLOCKEVENTS is defined, the third timer channel
	  may be used as a clock event device supporting oneshot mode
	  (delays of up to two seconds) based on the 32 KiHz clock.

config ATMEL_TCB_CLKSRC_BLOCK
	int
	depends on ATMEL_TCB_CLKSRC
	prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X
	default 0
	range 0 1
	help
	  Some chips provide more than one TC block, so you have the
	  choice of which one to use for the clock framework.  The other
	  TC can be used for other purposes, such as PWM generation and
	  interval timing.

L
Linus Torvalds 已提交
107 108
config IBM_ASM
	tristate "Device driver for IBM RSA service processor"
109
	depends on X86 && PCI && INPUT && EXPERIMENTAL
L
Linus Torvalds 已提交
110 111 112 113 114 115 116 117 118 119 120
	---help---
	  This option enables device driver support for in-band access to the
	  IBM RSA (Condor) service processor in eServer xSeries systems.
	  The ibmasm device driver allows user space application to access
	  ASM (Advanced Systems Management) functions on the service
	  processor. The driver is meant to be used in conjunction with
	  a user space API.
	  The ibmasm driver also enables the OS to use the UART on the
	  service processor board as a regular serial port. To make use of
	  this feature serial driver support (CONFIG_SERIAL_8250) must be
	  enabled.
121

L
Linus Torvalds 已提交
122 123
	  WARNING: This software may not be supported or function
	  correctly on your IBM server. Please consult the IBM ServerProven
124 125
	  website <http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>
	  for information on the specific driver level and support statement
L
Linus Torvalds 已提交
126 127
	  for your IBM server.

J
Jiri Slaby 已提交
128
config PHANTOM
J
Jiri Slaby 已提交
129
	tristate "Sensable PHANToM (PCI)"
J
Jiri Slaby 已提交
130 131 132 133
	depends on PCI
	help
	  Say Y here if you want to build a driver for Sensable PHANToM device.

J
Jiri Slaby 已提交
134 135
	  This driver is only for PCI PHANToMs.

J
Jiri Slaby 已提交
136 137 138
	  If you choose to build module, its name will be phantom. If unsure,
	  say N here.

139 140
config SGI_IOC4
	tristate "SGI IOC4 Base IO support"
A
Al Viro 已提交
141
	depends on PCI
142 143 144 145 146 147 148 149 150
	---help---
	  This option enables basic support for the IOC4 chip on certain
	  SGI IO controller cards (IO9, IO10, and PCI-RT).  This option
	  does not enable any specific functions on such a card, but provides
	  necessary infrastructure for other drivers to utilize.

	  If you have an SGI Altix with an IOC4-based card say Y.
	  Otherwise say N.

151 152
config TIFM_CORE
	tristate "TI Flash Media interface support (EXPERIMENTAL)"
153
	depends on EXPERIMENTAL && PCI
154 155 156 157 158 159 160 161 162 163
	help
	  If you want support for Texas Instruments(R) Flash Media adapters
	  you should select this option and then also choose an appropriate
	  host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
	  support', if you have a TI PCI74xx compatible card reader, for
	  example.
	  You will also have to select some flash card format drivers. MMC/SD
	  cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
	  Interface support (MMC_TIFM_SD)'.

164
	  To compile this driver as a module, choose M here: the module will
165
	  be called tifm_core.
L
Linus Torvalds 已提交
166

167 168 169 170 171 172 173 174 175 176
config TIFM_7XX1
	tristate "TI Flash Media PCI74xx/PCI76xx host adapter support (EXPERIMENTAL)"
	depends on PCI && TIFM_CORE && EXPERIMENTAL
	default TIFM_CORE
	help
	  This option enables support for Texas Instruments(R) PCI74xx and
	  PCI76xx families of Flash Media adapters, found in many laptops.
	  To make actual use of the device, you will have to select some
	  flash card format drivers, as outlined in the TIFM_CORE Help.

177
	  To compile this driver as a module, choose M here: the module will
178 179
	  be called tifm_7xx1.

180 181 182 183 184 185 186 187 188 189
config ICS932S401
	tristate "Integrated Circuits ICS932S401"
	depends on I2C && EXPERIMENTAL
	help
	  If you say yes here you get support for the Integrated Circuits
	  ICS932S401 clock control chips.

	  This driver can also be built as a module. If so, the module
	  will be called ics932s401.

190 191 192 193
config ATMEL_SSC
	tristate "Device driver for Atmel SSC peripheral"
	depends on AVR32 || ARCH_AT91
	---help---
194
	  This option enables device driver support for Atmel Synchronized
195 196 197 198 199 200 201
	  Serial Communication peripheral (SSC).

	  The SSC peripheral supports a wide variety of serial frame based
	  communications, i.e. I2S, SPI, etc.

	  If unsure, say N.

202 203 204 205 206 207 208 209 210
config ENCLOSURE_SERVICES
	tristate "Enclosure Services"
	default n
	help
	  Provides support for intelligent enclosures (bays which
	  contain storage devices).  You also need either a host
	  driver (SCSI/ATA) which supports enclosures
	  or a SCSI enclosure device (SES) to use these services.

211 212
config SGI_XP
	tristate "Support communication between SGI SSIs"
213
	depends on NET
N
Nick Piggin 已提交
214
	depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
215 216
	select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
	select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
217
	select SGI_GRU if X86_64 && SMP
218 219 220 221 222 223 224
	---help---
	  An SGI machine can be divided into multiple Single System
	  Images which act independently of each other and have
	  hardware based memory protection from the others.  Enabling
	  this feature will allow for direct communication between SSIs
	  based on a network adapter and DMA messaging.

225 226
config CS5535_MFGPT
	tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
227
	depends on PCI
228 229 230 231 232 233 234 235 236 237 238 239 240
	depends on X86
	default n
	help
	  This driver provides access to MFGPT functionality for other
	  drivers that need timers.  MFGPTs are available in the CS5535 and
	  CS5536 companion chips that are found in AMD Geode and several
	  other platforms.  They have a better resolution and max interval
	  than the generic PIT, and are suitable for use as high-res timers.
	  You probably don't want to enable this manually; other drivers that
	  make use of it should enable it.

config CS5535_MFGPT_DEFAULT_IRQ
	int
241
	depends on CS5535_MFGPT
242 243 244 245 246 247 248 249
	default 7
	help
	  MFGPTs on the CS5535 require an interrupt.  The selected IRQ
	  can be overridden as a module option as well as by driver that
	  use the cs5535_mfgpt_ API; however, different architectures might
	  want to use a different IRQ by default.  This is here for
	  architectures to set as necessary.

R
Randy Dunlap 已提交
250 251
config CS5535_CLOCK_EVENT_SRC
	tristate "CS5535/CS5536 high-res timer (MFGPT) events"
J
John Stultz 已提交
252
	depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
R
Randy Dunlap 已提交
253 254 255 256 257 258
	help
	  This driver provides a clock event source based on the MFGPT
	  timer(s) in the CS5535 and CS5536 companion chips.
	  MFGPTs have a better resolution and max interval than the
	  generic PIT, and are suitable for use as high-res timers.

D
David Altobelli 已提交
259
config HP_ILO
260
	tristate "Channel interface driver for the HP iLO processor"
261
	depends on PCI
D
David Altobelli 已提交
262 263 264
	default n
	help
	  The channel interface driver allows applications to communicate
265 266 267 268
	  with iLO management processors present on HP ProLiant servers.
	  Upon loading, the driver creates /dev/hpilo/dXccbN files, which
	  can be used to gather data from the management processor, via
	  read and write system calls.
D
David Altobelli 已提交
269 270 271 272

	  To compile this driver as a module, choose M here: the
	  module will be called hpilo.

273 274
config SGI_GRU
	tristate "SGI GRU driver"
275
	depends on X86_UV && SMP
276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295
	default n
	select MMU_NOTIFIER
	---help---
	The GRU is a hardware resource located in the system chipset. The GRU
	contains memory that can be mmapped into the user address space. This memory is
	used to communicate with the GRU to perform functions such as load/store,
	scatter/gather, bcopy, AMOs, etc.  The GRU is directly accessed by user
	instructions using user virtual addresses. GRU instructions (ex., bcopy) use
	user virtual addresses for operands.

	If you are not running on a SGI UV system, say N.

config SGI_GRU_DEBUG
	bool  "SGI GRU driver debug"
	depends on SGI_GRU
	default n
	---help---
	This option enables addition debugging code for the SGI GRU driver. If
	you are unsure, say N.

296 297 298 299 300 301 302 303 304 305
config APDS9802ALS
	tristate "Medfield Avago APDS9802 ALS Sensor module"
	depends on I2C
	help
	  If you say yes here you get support for the ALS APDS9802 ambient
	  light sensor.

	  This driver can also be built as a module.  If so, the module
	  will be called apds9802als.

306 307 308 309 310 311 312 313 314 315
config ISL29003
	tristate "Intersil ISL29003 ambient light sensor"
	depends on I2C && SYSFS
	help
	  If you say yes here you get support for the Intersil ISL29003
	  ambient light sensor.

	  This driver can also be built as a module.  If so, the module
	  will be called isl29003.

316 317 318 319 320 321 322 323 324 325
config ISL29020
	tristate "Intersil ISL29020 ambient light sensor"
	depends on I2C
	help
	  If you say yes here you get support for the Intersil ISL29020
	  ambient light sensor.

	  This driver can also be built as a module.  If so, the module
	  will be called isl29020.

326 327 328 329 330 331 332 333 334 335
config SENSORS_TSL2550
	tristate "Taos TSL2550 ambient light sensor"
	depends on I2C && SYSFS
	help
	  If you say yes here you get support for the Taos TSL2550
	  ambient light sensor.

	  This driver can also be built as a module.  If so, the module
	  will be called tsl2550.

336 337 338 339 340 341 342 343 344 345
config SENSORS_BH1780
	tristate "ROHM BH1780GLI ambient light sensor"
	depends on I2C && SYSFS
	help
	  If you say yes here you get support for the ROHM BH1780GLI
	  ambient light sensor.

	  This driver can also be built as a module.  If so, the module
	  will be called bh1780gli.

346 347 348 349 350 351 352 353 354 355
config SENSORS_BH1770
         tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
         depends on I2C
         ---help---
           Say Y here if you want to build a driver for BH1770GLC (ROHM) or
	   SFH7770 (Osram) combined ambient light and proximity sensor chip.

           To compile this driver as a module, choose M here: the
           module will be called bh1770glc. If unsure, say N here.

356 357 358 359 360 361 362 363 364 365 366
config SENSORS_APDS990X
	 tristate "APDS990X combined als and proximity sensors"
	 depends on I2C
	 default n
	 ---help---
	   Say Y here if you want to build a driver for Avago APDS990x
	   combined ambient light and proximity sensor chip.

	   To compile this driver as a module, choose M here: the
	   module will be called apds990x. If unsure, say N here.

367 368 369 370 371 372 373
config HMC6352
	tristate "Honeywell HMC6352 compass"
	depends on I2C
	help
	  This driver provides support for the Honeywell HMC6352 compass,
	  providing configuration and heading data via sysfs.

374 375 376 377 378 379 380 381 382 383 384 385 386
config EP93XX_PWM
	tristate "EP93xx PWM support"
	depends on ARCH_EP93XX
	help
	  This option enables device driver support for the PWM channels
	  on the Cirrus EP93xx processors.  The EP9307 chip only has one
	  PWM channel all the others have two, the second channel is an
	  alternate function of the EGPIO14 pin.  A sysfs interface is
	  provided to control the PWM channels.

	  To compile this driver as a module, choose M here: the module will
	  be called ep93xx_pwm.

387 388 389 390 391 392 393 394 395 396
config DS1682
	tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
	depends on I2C && EXPERIMENTAL
	help
	  If you say yes here you get support for Dallas Semiconductor
	  DS1682 Total Elapsed Time Recorder.

	  This driver can also be built as a module.  If so, the module
	  will be called ds1682.

397 398 399 400 401 402 403 404
config TI_DAC7512
	tristate "Texas Instruments DAC7512"
	depends on SPI && SYSFS
	help
	  If you say yes here you get support for the Texas Instruments
	  DAC7512 16-bit digital-to-analog converter.

	  This driver can also be built as a module. If so, the module
405
	  will be called ti_dac7512.
406

D
Dmitry Torokhov 已提交
407 408 409 410 411 412 413 414 415 416 417 418 419 420
config VMWARE_BALLOON
	tristate "VMware Balloon Driver"
	depends on X86
	help
	  This is VMware physical memory management driver which acts
	  like a "balloon" that can be inflated to reclaim physical pages
	  by reserving them in the guest and invalidating them in the
	  monitor, freeing up the underlying machine pages so they can
	  be allocated to other guests. The balloon can also be deflated
	  to allow the guest to use more physical memory.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the
D
Dmitry Torokhov 已提交
421
	  module will be called vmw_balloon.
D
Dmitry Torokhov 已提交
422

423 424 425 426 427 428 429 430 431 432
config ARM_CHARLCD
	bool "ARM Ltd. Character LCD Driver"
	depends on PLAT_VERSATILE
	help
	  This is a driver for the character LCD found on the ARM Ltd.
	  Versatile and RealView Platform Baseboards. It doesn't do
	  very much more than display the text "ARM Linux" on the first
	  line and the Linux version on the second line, but that's
	  still useful.

433 434 435 436 437
config BMP085
	tristate "BMP085 digital pressure sensor"
	depends on I2C && SYSFS
	help
	  If you say yes here you get support for the Bosch Sensortec
T
Thomas Weber 已提交
438
	  BMP085 digital pressure sensor.
439 440 441 442

	  To compile this driver as a module, choose M here: the
	  module will be called bmp085.

443 444 445 446 447 448 449 450 451 452 453 454
config PCH_PHUB
	tristate "PCH Packet Hub of Intel Topcliff"
	depends on PCI
	help
	  This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
	  Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
	  processor. The Topcliff has MAC address and Option ROM data in SROM.
	  This driver can access MAC address and Option ROM data in SROM.

	  To compile this driver as a module, choose M here: the module will
	  be called pch_phub.

R
Rodolfo Giometti 已提交
455
source "drivers/misc/c2port/Kconfig"
456
source "drivers/misc/eeprom/Kconfig"
457
source "drivers/misc/cb710/Kconfig"
458
source "drivers/misc/iwmc3200top/Kconfig"
459
source "drivers/misc/ti-st/Kconfig"
R
Rodolfo Giometti 已提交
460

R
Randy Dunlap 已提交
461
endif # MISC_DEVICES