5 # This one has to live outside of the MISC_DEVICES conditional,
6 # because it may be selected by drivers/platform/x86/hp_accel.
7 config SENSORS_LIS3LV02D
13 menuconfig MISC_DEVICES
16 Say Y here to get to see options for device drivers from various
17 different categories. This option alone does not add any kernel code.
19 If you say N, all options in this submenu will be skipped and disabled.
24 tristate "Analog Devices Digital Potentiometers"
25 depends on (I2C || SPI) && SYSFS
27 If you say yes here, you get support for the Analog Devices
28 AD5258, AD5259, AD5251, AD5252, AD5253, AD5254, AD5255
29 AD5160, AD5161, AD5162, AD5165, AD5200, AD5201, AD5203,
30 AD5204, AD5206, AD5207, AD5231, AD5232, AD5233, AD5235,
31 AD5260, AD5262, AD5263, AD5290, AD5291, AD5292, AD5293,
32 AD7376, AD8400, AD8402, AD8403, ADN2850, AD5241, AD5242,
33 AD5243, AD5245, AD5246, AD5247, AD5248, AD5280, AD5282,
34 ADN2860, AD5273, AD5171, AD5170, AD5172, AD5173, AD5270,
35 AD5271, AD5272, AD5274
36 digital potentiometer chips.
38 See Documentation/misc-devices/ad525x_dpot.txt for the
41 This driver can also be built as a module. If so, the module
42 will be called ad525x_dpot.
44 config AD525X_DPOT_I2C
45 tristate "support I2C bus connection"
46 depends on AD525X_DPOT && I2C
48 Say Y here if you have a digital potentiometers hooked to an I2C bus.
50 To compile this driver as a module, choose M here: the
51 module will be called ad525x_dpot-i2c.
53 config AD525X_DPOT_SPI
54 tristate "support SPI bus connection"
55 depends on AD525X_DPOT && SPI_MASTER
57 Say Y here if you have a digital potentiometers hooked to an SPI bus.
59 If unsure, say N (but it's safe to say "Y").
61 To compile this driver as a module, choose M here: the
62 module will be called ad525x_dpot-spi.
65 bool "Android pmem allocator"
69 tristate "Atmel AT32/AT91 PWM support"
70 depends on AVR32 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9
72 This option enables device driver support for the PWM channels
73 on certain Atmel processors. Pulse Width Modulation is used for
74 purposes including software controlled power-efficient backlights
75 on LCD displays, motor control, and waveform generation.
78 bool "AB8500 PWM support"
79 depends on AB8500_CORE && ARCH_U8500
82 This driver exports functions to enable/disble/config/free Pulse
83 Width Modulation in the Analog Baseband Chip AB8500.
84 It is used by led and backlight driver to control the intensity.
87 bool "Atmel AT32/AT91 Timer/Counter Library"
88 depends on (AVR32 || ARCH_AT91)
90 Select this if you want a library to allocate the Timer/Counter
91 blocks found on many Atmel processors. This facilitates using
92 these blocks by different drivers despite processor differences.
94 config ATMEL_TCB_CLKSRC
95 bool "TC Block Clocksource"
96 depends on ATMEL_TCLIB
99 Select this to get a high precision clocksource based on a
100 TC block with a 5+ MHz base clock rate. Two timer channels
101 are combined to make a single 32-bit timer.
103 When GENERIC_CLOCKEVENTS is defined, the third timer channel
104 may be used as a clock event device supporting oneshot mode
105 (delays of up to two seconds) based on the 32 KiHz clock.
107 config ATMEL_TCB_CLKSRC_BLOCK
109 depends on ATMEL_TCB_CLKSRC
110 prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X
114 Some chips provide more than one TC block, so you have the
115 choice of which one to use for the clock framework. The other
116 TC can be used for other purposes, such as PWM generation and
120 tristate "Device driver for IBM RSA service processor"
121 depends on X86 && PCI && INPUT && EXPERIMENTAL
123 This option enables device driver support for in-band access to the
124 IBM RSA (Condor) service processor in eServer xSeries systems.
125 The ibmasm device driver allows user space application to access
126 ASM (Advanced Systems Management) functions on the service
127 processor. The driver is meant to be used in conjunction with
129 The ibmasm driver also enables the OS to use the UART on the
130 service processor board as a regular serial port. To make use of
131 this feature serial driver support (CONFIG_SERIAL_8250) must be
134 WARNING: This software may not be supported or function
135 correctly on your IBM server. Please consult the IBM ServerProven
136 website <http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>
137 for information on the specific driver level and support statement
141 tristate "Sensable PHANToM (PCI)"
144 Say Y here if you want to build a driver for Sensable PHANToM device.
146 This driver is only for PCI PHANToMs.
148 If you choose to build module, its name will be phantom. If unsure,
152 tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard"
155 The PTI (Parallel Trace Interface) driver directs
156 trace data routed from various parts in the system out
157 through an Intel Penwell PTI port and out of the mobile
158 device for analysis with a debugging tool (Lauterbach or Fido).
160 You should select this driver if the target kernel is meant for
161 an Intel Atom (non-netbook) mobile device containing a MIPI
162 P1149.7 standard implementation.
165 tristate "SGI IOC4 Base IO support"
168 This option enables basic support for the IOC4 chip on certain
169 SGI IO controller cards (IO9, IO10, and PCI-RT). This option
170 does not enable any specific functions on such a card, but provides
171 necessary infrastructure for other drivers to utilize.
173 If you have an SGI Altix with an IOC4-based card say Y.
177 tristate "TI Flash Media interface support (EXPERIMENTAL)"
178 depends on EXPERIMENTAL && PCI
180 If you want support for Texas Instruments(R) Flash Media adapters
181 you should select this option and then also choose an appropriate
182 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
183 support', if you have a TI PCI74xx compatible card reader, for
185 You will also have to select some flash card format drivers. MMC/SD
186 cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
187 Interface support (MMC_TIFM_SD)'.
189 To compile this driver as a module, choose M here: the module will
193 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support (EXPERIMENTAL)"
194 depends on PCI && TIFM_CORE && EXPERIMENTAL
197 This option enables support for Texas Instruments(R) PCI74xx and
198 PCI76xx families of Flash Media adapters, found in many laptops.
199 To make actual use of the device, you will have to select some
200 flash card format drivers, as outlined in the TIFM_CORE Help.
202 To compile this driver as a module, choose M here: the module will
206 tristate "Integrated Circuits ICS932S401"
207 depends on I2C && EXPERIMENTAL
209 If you say yes here you get support for the Integrated Circuits
210 ICS932S401 clock control chips.
212 This driver can also be built as a module. If so, the module
213 will be called ics932s401.
216 tristate "Device driver for Atmel SSC peripheral"
217 depends on AVR32 || ARCH_AT91
219 This option enables device driver support for Atmel Synchronized
220 Serial Communication peripheral (SSC).
222 The SSC peripheral supports a wide variety of serial frame based
223 communications, i.e. I2S, SPI, etc.
227 config ENCLOSURE_SERVICES
228 tristate "Enclosure Services"
231 Provides support for intelligent enclosures (bays which
232 contain storage devices). You also need either a host
233 driver (SCSI/ATA) which supports enclosures
234 or a SCSI enclosure device (SES) to use these services.
236 config KERNEL_DEBUGGER_CORE
237 bool "Kernel Debugger Core"
240 Generic kernel debugging command processor used by low level
241 (interrupt context) platform-specific debuggers.
244 tristate "Support communication between SGI SSIs"
246 depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
247 select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
248 select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
249 select SGI_GRU if X86_64 && SMP
251 An SGI machine can be divided into multiple Single System
252 Images which act independently of each other and have
253 hardware based memory protection from the others. Enabling
254 this feature will allow for direct communication between SSIs
255 based on a network adapter and DMA messaging.
258 tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
263 This driver provides access to MFGPT functionality for other
264 drivers that need timers. MFGPTs are available in the CS5535 and
265 CS5536 companion chips that are found in AMD Geode and several
266 other platforms. They have a better resolution and max interval
267 than the generic PIT, and are suitable for use as high-res timers.
268 You probably don't want to enable this manually; other drivers that
269 make use of it should enable it.
271 config CS5535_MFGPT_DEFAULT_IRQ
273 depends on CS5535_MFGPT
276 MFGPTs on the CS5535 require an interrupt. The selected IRQ
277 can be overridden as a module option as well as by driver that
278 use the cs5535_mfgpt_ API; however, different architectures might
279 want to use a different IRQ by default. This is here for
280 architectures to set as necessary.
282 config CS5535_CLOCK_EVENT_SRC
283 tristate "CS5535/CS5536 high-res timer (MFGPT) events"
284 depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
286 This driver provides a clock event source based on the MFGPT
287 timer(s) in the CS5535 and CS5536 companion chips.
288 MFGPTs have a better resolution and max interval than the
289 generic PIT, and are suitable for use as high-res timers.
292 tristate "Channel interface driver for the HP iLO processor"
296 The channel interface driver allows applications to communicate
297 with iLO management processors present on HP ProLiant servers.
298 Upon loading, the driver creates /dev/hpilo/dXccbN files, which
299 can be used to gather data from the management processor, via
300 read and write system calls.
302 To compile this driver as a module, choose M here: the
303 module will be called hpilo.
306 tristate "SGI GRU driver"
307 depends on X86_UV && SMP
311 The GRU is a hardware resource located in the system chipset. The GRU
312 contains memory that can be mmapped into the user address space. This memory is
313 used to communicate with the GRU to perform functions such as load/store,
314 scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
315 instructions using user virtual addresses. GRU instructions (ex., bcopy) use
316 user virtual addresses for operands.
318 If you are not running on a SGI UV system, say N.
321 bool "SGI GRU driver debug"
325 This option enables addition debugging code for the SGI GRU driver. If
326 you are unsure, say N.
329 tristate "Medfield Avago APDS9802 ALS Sensor module"
332 If you say yes here you get support for the ALS APDS9802 ambient
335 This driver can also be built as a module. If so, the module
336 will be called apds9802als.
339 tristate "Intersil ISL29003 ambient light sensor"
340 depends on I2C && SYSFS
342 If you say yes here you get support for the Intersil ISL29003
343 ambient light sensor.
345 This driver can also be built as a module. If so, the module
346 will be called isl29003.
349 tristate "Intersil ISL29020 ambient light sensor"
352 If you say yes here you get support for the Intersil ISL29020
353 ambient light sensor.
355 This driver can also be built as a module. If so, the module
356 will be called isl29020.
358 config SENSORS_TSL2550
359 tristate "Taos TSL2550 ambient light sensor"
360 depends on I2C && SYSFS
362 If you say yes here you get support for the Taos TSL2550
363 ambient light sensor.
365 This driver can also be built as a module. If so, the module
366 will be called tsl2550.
368 config SENSORS_BH1780
369 tristate "ROHM BH1780GLI ambient light sensor"
370 depends on I2C && SYSFS
372 If you say yes here you get support for the ROHM BH1780GLI
373 ambient light sensor.
375 This driver can also be built as a module. If so, the module
376 will be called bh1780gli.
378 config SENSORS_BH1770
379 tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
382 Say Y here if you want to build a driver for BH1770GLC (ROHM) or
383 SFH7770 (Osram) combined ambient light and proximity sensor chip.
385 To compile this driver as a module, choose M here: the
386 module will be called bh1770glc. If unsure, say N here.
388 config SENSORS_APDS990X
389 tristate "APDS990X combined als and proximity sensors"
393 Say Y here if you want to build a driver for Avago APDS990x
394 combined ambient light and proximity sensor chip.
396 To compile this driver as a module, choose M here: the
397 module will be called apds990x. If unsure, say N here.
400 tristate "Honeywell HMC6352 compass"
403 This driver provides support for the Honeywell HMC6352 compass,
404 providing configuration and heading data via sysfs.
407 tristate "EP93xx PWM support"
408 depends on ARCH_EP93XX
410 This option enables device driver support for the PWM channels
411 on the Cirrus EP93xx processors. The EP9307 chip only has one
412 PWM channel all the others have two, the second channel is an
413 alternate function of the EGPIO14 pin. A sysfs interface is
414 provided to control the PWM channels.
416 To compile this driver as a module, choose M here: the module will
417 be called ep93xx_pwm.
420 tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
421 depends on I2C && EXPERIMENTAL
423 If you say yes here you get support for Dallas Semiconductor
424 DS1682 Total Elapsed Time Recorder.
426 This driver can also be built as a module. If so, the module
427 will be called ds1682.
429 config SPEAR13XX_PCIE_GADGET
430 bool "PCIe gadget support for SPEAr13XX platform"
431 depends on ARCH_SPEAR13XX
434 This option enables gadget support for PCIe controller. If
435 board file defines any controller as PCIe endpoint then a sysfs
436 entry will be created for that controller. User can use these
437 sysfs node to configure PCIe EP as per his requirements.
440 tristate "Texas Instruments DAC7512"
441 depends on SPI && SYSFS
443 If you say yes here you get support for the Texas Instruments
444 DAC7512 16-bit digital-to-analog converter.
446 This driver can also be built as a module. If so, the module
447 will be called ti_dac7512.
450 bool "UID based statistics tracking exported to /proc/uid_stat"
453 config VMWARE_BALLOON
454 tristate "VMware Balloon Driver"
457 This is VMware physical memory management driver which acts
458 like a "balloon" that can be inflated to reclaim physical pages
459 by reserving them in the guest and invalidating them in the
460 monitor, freeing up the underlying machine pages so they can
461 be allocated to other guests. The balloon can also be deflated
462 to allow the guest to use more physical memory.
466 To compile this driver as a module, choose M here: the
467 module will be called vmw_balloon.
470 bool "ARM Ltd. Character LCD Driver"
471 depends on PLAT_VERSATILE
473 This is a driver for the character LCD found on the ARM Ltd.
474 Versatile and RealView Platform Baseboards. It doesn't do
475 very much more than display the text "ARM Linux" on the first
476 line and the Linux version on the second line, but that's
480 tristate "BMP085 digital pressure sensor"
481 depends on I2C && SYSFS
483 If you say yes here you get support for the Bosch Sensortec
484 BMP085 digital pressure sensor.
486 To compile this driver as a module, choose M here: the
487 module will be called bmp085.
490 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR IOH(ML7213/ML7223) PHUB"
493 This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
494 Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
495 processor. The Topcliff has MAC address and Option ROM data in SROM.
496 This driver can access MAC address and Option ROM data in SROM.
498 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
499 Output Hub), ML7213 and ML7223.
500 ML7213 IOH is for IVI(In-Vehicle Infotainment) use and ML7223 IOH is
501 for MP(Media Phone) use.
502 ML7213/ML7223 is companion chip for Intel Atom E6xx series.
503 ML7213/ML7223 is completely compatible for Intel EG20T PCH.
505 To compile this driver as a module, choose M here: the module will
509 tristate "Bluetooth power control driver for TI wl127x"
513 Creates an rfkill entry in sysfs for power control of Bluetooth
517 bool "Android kernel panic diagnostics driver"
520 Driver which handles kernel panics and attempts to write
521 critical debugging data to flash.
524 string "Android panic dump flash partition label"
528 If your platform uses a different flash partition label for storing
529 crashdumps, enter it here.
531 source "drivers/misc/c2port/Kconfig"
532 source "drivers/misc/eeprom/Kconfig"
533 source "drivers/misc/cb710/Kconfig"
534 source "drivers/misc/iwmc3200top/Kconfig"
535 source "drivers/misc/ti-st/Kconfig"
536 source "drivers/misc/lis3lv02d/Kconfig"
537 source "drivers/misc/carma/Kconfig"