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 tristate "Atmel AT32/AT91 PWM support"
66 depends on AVR32 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9
68 This option enables device driver support for the PWM channels
69 on certain Atmel processors. Pulse Width Modulation is used for
70 purposes including software controlled power-efficient backlights
71 on LCD displays, motor control, and waveform generation.
74 bool "AB8500 PWM support"
75 depends on AB8500_CORE && ARCH_U8500
78 This driver exports functions to enable/disble/config/free Pulse
79 Width Modulation in the Analog Baseband Chip AB8500.
80 It is used by led and backlight driver to control the intensity.
83 bool "Atmel AT32/AT91 Timer/Counter Library"
84 depends on (AVR32 || ARCH_AT91)
86 Select this if you want a library to allocate the Timer/Counter
87 blocks found on many Atmel processors. This facilitates using
88 these blocks by different drivers despite processor differences.
90 config ATMEL_TCB_CLKSRC
91 bool "TC Block Clocksource"
92 depends on ATMEL_TCLIB
95 Select this to get a high precision clocksource based on a
96 TC block with a 5+ MHz base clock rate. Two timer channels
97 are combined to make a single 32-bit timer.
99 When GENERIC_CLOCKEVENTS is defined, the third timer channel
100 may be used as a clock event device supporting oneshot mode
101 (delays of up to two seconds) based on the 32 KiHz clock.
103 config ATMEL_TCB_CLKSRC_BLOCK
105 depends on ATMEL_TCB_CLKSRC
106 prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X
110 Some chips provide more than one TC block, so you have the
111 choice of which one to use for the clock framework. The other
112 TC can be used for other purposes, such as PWM generation and
116 tristate "Device driver for IBM RSA service processor"
117 depends on X86 && PCI && INPUT && EXPERIMENTAL
119 This option enables device driver support for in-band access to the
120 IBM RSA (Condor) service processor in eServer xSeries systems.
121 The ibmasm device driver allows user space application to access
122 ASM (Advanced Systems Management) functions on the service
123 processor. The driver is meant to be used in conjunction with
125 The ibmasm driver also enables the OS to use the UART on the
126 service processor board as a regular serial port. To make use of
127 this feature serial driver support (CONFIG_SERIAL_8250) must be
130 WARNING: This software may not be supported or function
131 correctly on your IBM server. Please consult the IBM ServerProven
132 website <http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>
133 for information on the specific driver level and support statement
137 tristate "Sensable PHANToM (PCI)"
140 Say Y here if you want to build a driver for Sensable PHANToM device.
142 This driver is only for PCI PHANToMs.
144 If you choose to build module, its name will be phantom. If unsure,
148 tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard"
151 The PTI (Parallel Trace Interface) driver directs
152 trace data routed from various parts in the system out
153 through an Intel Penwell PTI port and out of the mobile
154 device for analysis with a debugging tool (Lauterbach or Fido).
156 You should select this driver if the target kernel is meant for
157 an Intel Atom (non-netbook) mobile device containing a MIPI
158 P1149.7 standard implementation.
161 tristate "SGI IOC4 Base IO support"
164 This option enables basic support for the IOC4 chip on certain
165 SGI IO controller cards (IO9, IO10, and PCI-RT). This option
166 does not enable any specific functions on such a card, but provides
167 necessary infrastructure for other drivers to utilize.
169 If you have an SGI Altix with an IOC4-based card say Y.
173 tristate "TI Flash Media interface support (EXPERIMENTAL)"
174 depends on EXPERIMENTAL && PCI
176 If you want support for Texas Instruments(R) Flash Media adapters
177 you should select this option and then also choose an appropriate
178 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
179 support', if you have a TI PCI74xx compatible card reader, for
181 You will also have to select some flash card format drivers. MMC/SD
182 cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
183 Interface support (MMC_TIFM_SD)'.
185 To compile this driver as a module, choose M here: the module will
189 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support (EXPERIMENTAL)"
190 depends on PCI && TIFM_CORE && EXPERIMENTAL
193 This option enables support for Texas Instruments(R) PCI74xx and
194 PCI76xx families of Flash Media adapters, found in many laptops.
195 To make actual use of the device, you will have to select some
196 flash card format drivers, as outlined in the TIFM_CORE Help.
198 To compile this driver as a module, choose M here: the module will
202 tristate "Integrated Circuits ICS932S401"
203 depends on I2C && EXPERIMENTAL
205 If you say yes here you get support for the Integrated Circuits
206 ICS932S401 clock control chips.
208 This driver can also be built as a module. If so, the module
209 will be called ics932s401.
212 tristate "Device driver for Atmel SSC peripheral"
213 depends on AVR32 || ARCH_AT91
215 This option enables device driver support for Atmel Synchronized
216 Serial Communication peripheral (SSC).
218 The SSC peripheral supports a wide variety of serial frame based
219 communications, i.e. I2S, SPI, etc.
223 config ENCLOSURE_SERVICES
224 tristate "Enclosure Services"
227 Provides support for intelligent enclosures (bays which
228 contain storage devices). You also need either a host
229 driver (SCSI/ATA) which supports enclosures
230 or a SCSI enclosure device (SES) to use these services.
233 tristate "Support communication between SGI SSIs"
235 depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
236 select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
237 select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
238 select SGI_GRU if X86_64 && SMP
240 An SGI machine can be divided into multiple Single System
241 Images which act independently of each other and have
242 hardware based memory protection from the others. Enabling
243 this feature will allow for direct communication between SSIs
244 based on a network adapter and DMA messaging.
247 tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
248 depends on PCI && X86 && MFD_CS5535
251 This driver provides access to MFGPT functionality for other
252 drivers that need timers. MFGPTs are available in the CS5535 and
253 CS5536 companion chips that are found in AMD Geode and several
254 other platforms. They have a better resolution and max interval
255 than the generic PIT, and are suitable for use as high-res timers.
256 You probably don't want to enable this manually; other drivers that
257 make use of it should enable it.
259 config CS5535_MFGPT_DEFAULT_IRQ
261 depends on CS5535_MFGPT
264 MFGPTs on the CS5535 require an interrupt. The selected IRQ
265 can be overridden as a module option as well as by driver that
266 use the cs5535_mfgpt_ API; however, different architectures might
267 want to use a different IRQ by default. This is here for
268 architectures to set as necessary.
270 config CS5535_CLOCK_EVENT_SRC
271 tristate "CS5535/CS5536 high-res timer (MFGPT) events"
272 depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
274 This driver provides a clock event source based on the MFGPT
275 timer(s) in the CS5535 and CS5536 companion chips.
276 MFGPTs have a better resolution and max interval than the
277 generic PIT, and are suitable for use as high-res timers.
280 tristate "Channel interface driver for the HP iLO processor"
284 The channel interface driver allows applications to communicate
285 with iLO management processors present on HP ProLiant servers.
286 Upon loading, the driver creates /dev/hpilo/dXccbN files, which
287 can be used to gather data from the management processor, via
288 read and write system calls.
290 To compile this driver as a module, choose M here: the
291 module will be called hpilo.
294 tristate "SGI GRU driver"
295 depends on X86_UV && SMP
299 The GRU is a hardware resource located in the system chipset. The GRU
300 contains memory that can be mmapped into the user address space. This memory is
301 used to communicate with the GRU to perform functions such as load/store,
302 scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
303 instructions using user virtual addresses. GRU instructions (ex., bcopy) use
304 user virtual addresses for operands.
306 If you are not running on a SGI UV system, say N.
309 bool "SGI GRU driver debug"
313 This option enables addition debugging code for the SGI GRU driver. If
314 you are unsure, say N.
317 tristate "Medfield Avago APDS9802 ALS Sensor module"
320 If you say yes here you get support for the ALS APDS9802 ambient
323 This driver can also be built as a module. If so, the module
324 will be called apds9802als.
327 tristate "Intersil ISL29003 ambient light sensor"
328 depends on I2C && SYSFS
330 If you say yes here you get support for the Intersil ISL29003
331 ambient light sensor.
333 This driver can also be built as a module. If so, the module
334 will be called isl29003.
337 tristate "Intersil ISL29020 ambient light sensor"
340 If you say yes here you get support for the Intersil ISL29020
341 ambient light sensor.
343 This driver can also be built as a module. If so, the module
344 will be called isl29020.
346 config SENSORS_TSL2550
347 tristate "Taos TSL2550 ambient light sensor"
348 depends on I2C && SYSFS
350 If you say yes here you get support for the Taos TSL2550
351 ambient light sensor.
353 This driver can also be built as a module. If so, the module
354 will be called tsl2550.
356 config SENSORS_BH1780
357 tristate "ROHM BH1780GLI ambient light sensor"
358 depends on I2C && SYSFS
360 If you say yes here you get support for the ROHM BH1780GLI
361 ambient light sensor.
363 This driver can also be built as a module. If so, the module
364 will be called bh1780gli.
366 config SENSORS_BH1770
367 tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
370 Say Y here if you want to build a driver for BH1770GLC (ROHM) or
371 SFH7770 (Osram) combined ambient light and proximity sensor chip.
373 To compile this driver as a module, choose M here: the
374 module will be called bh1770glc. If unsure, say N here.
376 config SENSORS_APDS990X
377 tristate "APDS990X combined als and proximity sensors"
381 Say Y here if you want to build a driver for Avago APDS990x
382 combined ambient light and proximity sensor chip.
384 To compile this driver as a module, choose M here: the
385 module will be called apds990x. If unsure, say N here.
388 tristate "Honeywell HMC6352 compass"
391 This driver provides support for the Honeywell HMC6352 compass,
392 providing configuration and heading data via sysfs.
394 config SENSORS_AK8975
395 tristate "AK8975 compass support"
399 If you say yes here you get support for Asahi Kasei's
400 orientation sensor AK8975.
403 tristate "EP93xx PWM support"
404 depends on ARCH_EP93XX
406 This option enables device driver support for the PWM channels
407 on the Cirrus EP93xx processors. The EP9307 chip only has one
408 PWM channel all the others have two, the second channel is an
409 alternate function of the EGPIO14 pin. A sysfs interface is
410 provided to control the PWM channels.
412 To compile this driver as a module, choose M here: the module will
413 be called ep93xx_pwm.
416 tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
417 depends on I2C && EXPERIMENTAL
419 If you say yes here you get support for Dallas Semiconductor
420 DS1682 Total Elapsed Time Recorder.
422 This driver can also be built as a module. If so, the module
423 will be called ds1682.
425 config SPEAR13XX_PCIE_GADGET
426 bool "PCIe gadget support for SPEAr13XX platform"
427 depends on ARCH_SPEAR13XX
430 This option enables gadget support for PCIe controller. If
431 board file defines any controller as PCIe endpoint then a sysfs
432 entry will be created for that controller. User can use these
433 sysfs node to configure PCIe EP as per his requirements.
436 tristate "Texas Instruments DAC7512"
437 depends on SPI && SYSFS
439 If you say yes here you get support for the Texas Instruments
440 DAC7512 16-bit digital-to-analog converter.
442 This driver can also be built as a module. If so, the module
443 will be called ti_dac7512.
446 bool "UID based statistics tracking exported to /proc/uid_stat"
449 config VMWARE_BALLOON
450 tristate "VMware Balloon Driver"
453 This is VMware physical memory management driver which acts
454 like a "balloon" that can be inflated to reclaim physical pages
455 by reserving them in the guest and invalidating them in the
456 monitor, freeing up the underlying machine pages so they can
457 be allocated to other guests. The balloon can also be deflated
458 to allow the guest to use more physical memory.
462 To compile this driver as a module, choose M here: the
463 module will be called vmw_balloon.
466 bool "ARM Ltd. Character LCD Driver"
467 depends on PLAT_VERSATILE
469 This is a driver for the character LCD found on the ARM Ltd.
470 Versatile and RealView Platform Baseboards. It doesn't do
471 very much more than display the text "ARM Linux" on the first
472 line and the Linux version on the second line, but that's
476 tristate "BMP085 digital pressure sensor"
477 depends on I2C && SYSFS
479 If you say yes here you get support for the Bosch Sensortec
480 BMP085 digital pressure sensor.
482 To compile this driver as a module, choose M here: the
483 module will be called bmp085.
486 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
489 This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
490 Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
491 processor. The Topcliff has MAC address and Option ROM data in SROM.
492 This driver can access MAC address and Option ROM data in SROM.
494 This driver also can be used for LAPIS Semiconductor's IOH,
495 ML7213/ML7223/ML7831.
496 ML7213 which is for IVI(In-Vehicle Infotainment) use.
497 ML7223 IOH is for MP(Media Phone) use.
498 ML7831 IOH is for general purpose use.
499 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
500 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
502 To compile this driver as a module, choose M here: the module will
506 tristate "Bluetooth power control driver for TI wl127x"
510 Creates an rfkill entry in sysfs for power control of Bluetooth
514 bool "Android kernel panic diagnostics driver"
517 Driver which handles kernel panics and attempts to write
518 critical debugging data to flash.
521 string "Android panic dump flash partition label"
525 If your platform uses a different flash partition label for storing
526 crashdumps, enter it here.
529 bool "STE modem control driver"
532 bool "MTK6223D modem control driver"
536 bool "FM rda580x driver"
539 bool "MU509 modem control driver"
542 bool "MW100 modem control driver"
545 bool "MT6229 modem control driver"
548 bool "RK29_NEWTON misc driver"
551 bool "SC8800 misc driver"
555 bool "TDSC8800 modem control driver"
559 source "drivers/misc/c2port/Kconfig"
560 source "drivers/misc/eeprom/Kconfig"
561 source "drivers/misc/cb710/Kconfig"
562 source "drivers/misc/rk29_modem/Kconfig"
563 source "drivers/misc/gps/Kconfig"
564 source "drivers/misc/inv_mpu/Kconfig"
565 source "drivers/misc/iwmc3200top/Kconfig"
566 source "drivers/misc/ti-st/Kconfig"
567 source "drivers/misc/lis3lv02d/Kconfig"
568 source "drivers/misc/carma/Kconfig"