7 config SENSORS_LIS3LV02D
14 tristate "Analog Devices Digital Potentiometers"
15 depends on (I2C || SPI) && SYSFS
17 If you say yes here, you get support for the Analog Devices
18 AD5258, AD5259, AD5251, AD5252, AD5253, AD5254, AD5255
19 AD5160, AD5161, AD5162, AD5165, AD5200, AD5201, AD5203,
20 AD5204, AD5206, AD5207, AD5231, AD5232, AD5233, AD5235,
21 AD5260, AD5262, AD5263, AD5290, AD5291, AD5292, AD5293,
22 AD7376, AD8400, AD8402, AD8403, ADN2850, AD5241, AD5242,
23 AD5243, AD5245, AD5246, AD5247, AD5248, AD5280, AD5282,
24 ADN2860, AD5273, AD5171, AD5170, AD5172, AD5173, AD5270,
25 AD5271, AD5272, AD5274
26 digital potentiometer chips.
28 See Documentation/misc-devices/ad525x_dpot.txt for the
31 This driver can also be built as a module. If so, the module
32 will be called ad525x_dpot.
34 config AD525X_DPOT_I2C
35 tristate "support I2C bus connection"
36 depends on AD525X_DPOT && I2C
38 Say Y here if you have a digital potentiometers hooked to an I2C bus.
40 To compile this driver as a module, choose M here: the
41 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
47 Say Y here if you have a digital potentiometers hooked to an SPI bus.
49 If unsure, say N (but it's safe to say "Y").
51 To compile this driver as a module, choose M here: the
52 module will be called ad525x_dpot-spi.
55 tristate "Atmel AT32/AT91 PWM support"
58 This option enables device driver support for the PWM channels
59 on certain Atmel processors. Pulse Width Modulation is used for
60 purposes including software controlled power-efficient backlights
61 on LCD displays, motor control, and waveform generation.
64 bool "AB8500 PWM support"
65 depends on AB8500_CORE && ARCH_U8500
68 This driver exports functions to enable/disble/config/free Pulse
69 Width Modulation in the Analog Baseband Chip AB8500.
70 It is used by led and backlight driver to control the intensity.
73 bool "Atmel AT32/AT91 Timer/Counter Library"
74 depends on (AVR32 || ARCH_AT91)
76 Select this if you want a library to allocate the Timer/Counter
77 blocks found on many Atmel processors. This facilitates using
78 these blocks by different drivers despite processor differences.
80 config ATMEL_TCB_CLKSRC
81 bool "TC Block Clocksource"
82 depends on ATMEL_TCLIB
85 Select this to get a high precision clocksource based on a
86 TC block with a 5+ MHz base clock rate. Two timer channels
87 are combined to make a single 32-bit timer.
89 When GENERIC_CLOCKEVENTS is defined, the third timer channel
90 may be used as a clock event device supporting oneshot mode
91 (delays of up to two seconds) based on the 32 KiHz clock.
93 config ATMEL_TCB_CLKSRC_BLOCK
95 depends on ATMEL_TCB_CLKSRC
96 prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X
100 Some chips provide more than one TC block, so you have the
101 choice of which one to use for the clock framework. The other
102 TC can be used for other purposes, such as PWM generation and
106 tristate "Device driver for IBM RSA service processor"
107 depends on X86 && PCI && INPUT && EXPERIMENTAL
109 This option enables device driver support for in-band access to the
110 IBM RSA (Condor) service processor in eServer xSeries systems.
111 The ibmasm device driver allows user space application to access
112 ASM (Advanced Systems Management) functions on the service
113 processor. The driver is meant to be used in conjunction with
115 The ibmasm driver also enables the OS to use the UART on the
116 service processor board as a regular serial port. To make use of
117 this feature serial driver support (CONFIG_SERIAL_8250) must be
120 WARNING: This software may not be supported or function
121 correctly on your IBM server. Please consult the IBM ServerProven
122 website <http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>
123 for information on the specific driver level and support statement
127 tristate "Sensable PHANToM (PCI)"
130 Say Y here if you want to build a driver for Sensable PHANToM device.
132 This driver is only for PCI PHANToMs.
134 If you choose to build module, its name will be phantom. If unsure,
138 tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard"
142 The PTI (Parallel Trace Interface) driver directs
143 trace data routed from various parts in the system out
144 through an Intel Penwell PTI port and out of the mobile
145 device for analysis with a debugging tool (Lauterbach or Fido).
147 You should select this driver if the target kernel is meant for
148 an Intel Atom (non-netbook) mobile device containing a MIPI
149 P1149.7 standard implementation.
152 tristate "SGI IOC4 Base IO support"
155 This option enables basic support for the IOC4 chip on certain
156 SGI IO controller cards (IO9, IO10, and PCI-RT). This option
157 does not enable any specific functions on such a card, but provides
158 necessary infrastructure for other drivers to utilize.
160 If you have an SGI Altix with an IOC4-based card say Y.
164 tristate "TI Flash Media interface support (EXPERIMENTAL)"
165 depends on EXPERIMENTAL && PCI
167 If you want support for Texas Instruments(R) Flash Media adapters
168 you should select this option and then also choose an appropriate
169 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
170 support', if you have a TI PCI74xx compatible card reader, for
172 You will also have to select some flash card format drivers. MMC/SD
173 cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
174 Interface support (MMC_TIFM_SD)'.
176 To compile this driver as a module, choose M here: the module will
180 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support (EXPERIMENTAL)"
181 depends on PCI && TIFM_CORE && EXPERIMENTAL
184 This option enables support for Texas Instruments(R) PCI74xx and
185 PCI76xx families of Flash Media adapters, found in many laptops.
186 To make actual use of the device, you will have to select some
187 flash card format drivers, as outlined in the TIFM_CORE Help.
189 To compile this driver as a module, choose M here: the module will
193 tristate "Integrated Circuits ICS932S401"
194 depends on I2C && EXPERIMENTAL
196 If you say yes here you get support for the Integrated Circuits
197 ICS932S401 clock control chips.
199 This driver can also be built as a module. If so, the module
200 will be called ics932s401.
203 tristate "Device driver for Atmel SSC peripheral"
204 depends on AVR32 || ARCH_AT91
206 This option enables device driver support for Atmel Synchronized
207 Serial Communication peripheral (SSC).
209 The SSC peripheral supports a wide variety of serial frame based
210 communications, i.e. I2S, SPI, etc.
214 config ENCLOSURE_SERVICES
215 tristate "Enclosure Services"
218 Provides support for intelligent enclosures (bays which
219 contain storage devices). You also need either a host
220 driver (SCSI/ATA) which supports enclosures
221 or a SCSI enclosure device (SES) to use these services.
223 config KERNEL_DEBUGGER_CORE
224 bool "Kernel Debugger Core"
227 Generic kernel debugging command processor used by low level
228 (interrupt context) platform-specific debuggers.
231 tristate "Support communication between SGI SSIs"
233 depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
234 select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
235 select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
236 select SGI_GRU if X86_64 && SMP
238 An SGI machine can be divided into multiple Single System
239 Images which act independently of each other and have
240 hardware based memory protection from the others. Enabling
241 this feature will allow for direct communication between SSIs
242 based on a network adapter and DMA messaging.
245 tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
246 depends on PCI && X86 && MFD_CS5535
249 This driver provides access to MFGPT functionality for other
250 drivers that need timers. MFGPTs are available in the CS5535 and
251 CS5536 companion chips that are found in AMD Geode and several
252 other platforms. They have a better resolution and max interval
253 than the generic PIT, and are suitable for use as high-res timers.
254 You probably don't want to enable this manually; other drivers that
255 make use of it should enable it.
257 config CS5535_MFGPT_DEFAULT_IRQ
259 depends on CS5535_MFGPT
262 MFGPTs on the CS5535 require an interrupt. The selected IRQ
263 can be overridden as a module option as well as by driver that
264 use the cs5535_mfgpt_ API; however, different architectures might
265 want to use a different IRQ by default. This is here for
266 architectures to set as necessary.
268 config CS5535_CLOCK_EVENT_SRC
269 tristate "CS5535/CS5536 high-res timer (MFGPT) events"
270 depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
272 This driver provides a clock event source based on the MFGPT
273 timer(s) in the CS5535 and CS5536 companion chips.
274 MFGPTs have a better resolution and max interval than the
275 generic PIT, and are suitable for use as high-res timers.
278 tristate "Channel interface driver for the HP iLO processor"
282 The channel interface driver allows applications to communicate
283 with iLO management processors present on HP ProLiant servers.
284 Upon loading, the driver creates /dev/hpilo/dXccbN files, which
285 can be used to gather data from the management processor, via
286 read and write system calls.
288 To compile this driver as a module, choose M here: the
289 module will be called hpilo.
292 tristate "SGI GRU driver"
293 depends on X86_UV && SMP
297 The GRU is a hardware resource located in the system chipset. The GRU
298 contains memory that can be mmapped into the user address space. This memory is
299 used to communicate with the GRU to perform functions such as load/store,
300 scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
301 instructions using user virtual addresses. GRU instructions (ex., bcopy) use
302 user virtual addresses for operands.
304 If you are not running on a SGI UV system, say N.
307 bool "SGI GRU driver debug"
311 This option enables addition debugging code for the SGI GRU driver. If
312 you are unsure, say N.
315 tristate "Medfield Avago APDS9802 ALS Sensor module"
318 If you say yes here you get support for the ALS APDS9802 ambient
321 This driver can also be built as a module. If so, the module
322 will be called apds9802als.
325 tristate "Intersil ISL29003 ambient light sensor"
326 depends on I2C && SYSFS
328 If you say yes here you get support for the Intersil ISL29003
329 ambient light sensor.
331 This driver can also be built as a module. If so, the module
332 will be called isl29003.
335 tristate "Intersil ISL29020 ambient light sensor"
338 If you say yes here you get support for the Intersil ISL29020
339 ambient light sensor.
341 This driver can also be built as a module. If so, the module
342 will be called isl29020.
344 config SENSORS_TSL2550
345 tristate "Taos TSL2550 ambient light sensor"
346 depends on I2C && SYSFS
348 If you say yes here you get support for the Taos TSL2550
349 ambient light sensor.
351 This driver can also be built as a module. If so, the module
352 will be called tsl2550.
354 config SENSORS_BH1780
355 tristate "ROHM BH1780GLI ambient light sensor"
356 depends on I2C && SYSFS
358 If you say yes here you get support for the ROHM BH1780GLI
359 ambient light sensor.
361 This driver can also be built as a module. If so, the module
362 will be called bh1780gli.
364 config SENSORS_BH1770
365 tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
368 Say Y here if you want to build a driver for BH1770GLC (ROHM) or
369 SFH7770 (Osram) combined ambient light and proximity sensor chip.
371 To compile this driver as a module, choose M here: the
372 module will be called bh1770glc. If unsure, say N here.
374 config SENSORS_APDS990X
375 tristate "APDS990X combined als and proximity sensors"
379 Say Y here if you want to build a driver for Avago APDS990x
380 combined ambient light and proximity sensor chip.
382 To compile this driver as a module, choose M here: the
383 module will be called apds990x. If unsure, say N here.
386 tristate "Honeywell HMC6352 compass"
389 This driver provides support for the Honeywell HMC6352 compass,
390 providing configuration and heading data via sysfs.
392 config SENSORS_NCT1008
393 tristate "ON Semiconductor Temperature Sensor"
397 Say yes here if you wish to include the ON Semiconductor
398 NCT1008 Temperature sensor.
400 config SENSORS_AK8975
401 tristate "AK8975 compass support"
405 If you say yes here you get support for Asahi Kasei's
406 orientation sensor AK8975.
409 tristate "EP93xx PWM support"
410 depends on ARCH_EP93XX
412 This option enables device driver support for the PWM channels
413 on the Cirrus EP93xx processors. The EP9307 chip only has one
414 PWM channel all the others have two, the second channel is an
415 alternate function of the EGPIO14 pin. A sysfs interface is
416 provided to control the PWM channels.
418 To compile this driver as a module, choose M here: the module will
419 be called ep93xx_pwm.
422 tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
423 depends on I2C && EXPERIMENTAL
425 If you say yes here you get support for Dallas Semiconductor
426 DS1682 Total Elapsed Time Recorder.
428 This driver can also be built as a module. If so, the module
429 will be called ds1682.
431 config SPEAR13XX_PCIE_GADGET
432 bool "PCIe gadget support for SPEAr13XX platform"
433 depends on ARCH_SPEAR13XX
436 This option enables gadget support for PCIe controller. If
437 board file defines any controller as PCIe endpoint then a sysfs
438 entry will be created for that controller. User can use these
439 sysfs node to configure PCIe EP as per his requirements.
442 tristate "Texas Instruments DAC7512"
443 depends on SPI && SYSFS
445 If you say yes here you get support for the Texas Instruments
446 DAC7512 16-bit digital-to-analog converter.
448 This driver can also be built as a module. If so, the module
449 will be called ti_dac7512.
452 bool "UID based statistics tracking exported to /proc/uid_stat"
455 config VMWARE_BALLOON
456 tristate "VMware Balloon Driver"
459 This is VMware physical memory management driver which acts
460 like a "balloon" that can be inflated to reclaim physical pages
461 by reserving them in the guest and invalidating them in the
462 monitor, freeing up the underlying machine pages so they can
463 be allocated to other guests. The balloon can also be deflated
464 to allow the guest to use more physical memory.
468 To compile this driver as a module, choose M here: the
469 module will be called vmw_balloon.
472 bool "ARM Ltd. Character LCD Driver"
473 depends on PLAT_VERSATILE
475 This is a driver for the character LCD found on the ARM Ltd.
476 Versatile and RealView Platform Baseboards. It doesn't do
477 very much more than display the text "ARM Linux" on the first
478 line and the Linux version on the second line, but that's
482 tristate "BMP085 digital pressure sensor"
483 depends on I2C && SYSFS
485 If you say yes here you get support for the Bosch Sensortec
486 BMP085 digital pressure sensor.
488 To compile this driver as a module, choose M here: the
489 module will be called bmp085.
492 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
495 This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
496 Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
497 processor. The Topcliff has MAC address and Option ROM data in SROM.
498 This driver can access MAC address and Option ROM data in SROM.
500 This driver also can be used for LAPIS Semiconductor's IOH,
501 ML7213/ML7223/ML7831.
502 ML7213 which is for IVI(In-Vehicle Infotainment) use.
503 ML7223 IOH is for MP(Media Phone) use.
504 ML7831 IOH is for general purpose use.
505 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
506 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
508 To compile this driver as a module, choose M here: the module will
511 config USB_SWITCH_FSA9480
512 tristate "FSA9480 USB Switch"
515 The FSA9480 is a USB port accessory detector and switch.
516 The FSA9480 is fully controlled using I2C and enables USB data,
517 stereo and mono audio, video, microphone and UART data to use
518 a common connector port.
521 tristate "MAX8997 MUIC Support"
522 depends on MFD_MAX8997
524 If you say yes here you get support for the MUIC device of
526 The MAX8997 MUIC is a USB port accessory detector and switch.
529 tristate "Bluetooth power control driver for TI wl127x"
533 Creates an rfkill entry in sysfs for power control of Bluetooth
536 config BCM4329_RFKILL
537 bool "Enable BCM4329 RFKILL driver"
540 Adds BCM4329 RFKILL driver for Broadcom BCM4329 chipset
542 config TEGRA_CRYPTO_DEV
543 bool "Device node to access tegra aes hardware"
545 Dev node /dev/tegra-crypto in order to get access to tegra aes
546 hardware from user space
548 config MAX1749_VIBRATOR
549 bool "MAX1749 vibrator device driver"
550 depends on ANDROID_TIMED_OUTPUT
553 Adds a timed output vibrator device node for MAX1749 vibrator motor
556 bool "Android kernel panic diagnostics driver"
559 Driver which handles kernel panics and attempts to write
560 critical debugging data to flash.
563 string "Android panic dump flash partition label"
566 If your platform uses a different flash partition label for storing
567 crashdumps, enter it here.
569 source "drivers/misc/c2port/Kconfig"
570 source "drivers/misc/eeprom/Kconfig"
571 source "drivers/misc/cb710/Kconfig"
572 source "drivers/misc/iwmc3200top/Kconfig"
573 source "drivers/misc/ti-st/Kconfig"
574 source "drivers/misc/lis3lv02d/Kconfig"
575 source "drivers/misc/carma/Kconfig"
576 source "drivers/misc/altera-stapl/Kconfig"
577 source "drivers/misc/inv_mpu/Kconfig"
578 source "drivers/misc/tegra-baseband/Kconfig"