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
69 This driver exports functions to enable/disble/config/free Pulse
70 Width Modulation in the Analog Baseband Chip AB8500.
71 It is used by led and backlight driver to control the intensity.
74 bool "Atmel AT32/AT91 Timer/Counter Library"
75 depends on (AVR32 || ARCH_AT91)
77 Select this if you want a library to allocate the Timer/Counter
78 blocks found on many Atmel processors. This facilitates using
79 these blocks by different drivers despite processor differences.
81 config ATMEL_TCB_CLKSRC
82 bool "TC Block Clocksource"
83 depends on ATMEL_TCLIB
86 Select this to get a high precision clocksource based on a
87 TC block with a 5+ MHz base clock rate. Two timer channels
88 are combined to make a single 32-bit timer.
90 When GENERIC_CLOCKEVENTS is defined, the third timer channel
91 may be used as a clock event device supporting oneshot mode
92 (delays of up to two seconds) based on the 32 KiHz clock.
94 config ATMEL_TCB_CLKSRC_BLOCK
96 depends on ATMEL_TCB_CLKSRC
97 prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X
101 Some chips provide more than one TC block, so you have the
102 choice of which one to use for the clock framework. The other
103 TC can be used for other purposes, such as PWM generation and
107 tristate "Device driver for IBM RSA service processor"
108 depends on X86 && PCI && INPUT && EXPERIMENTAL
110 This option enables device driver support for in-band access to the
111 IBM RSA (Condor) service processor in eServer xSeries systems.
112 The ibmasm device driver allows user space application to access
113 ASM (Advanced Systems Management) functions on the service
114 processor. The driver is meant to be used in conjunction with
116 The ibmasm driver also enables the OS to use the UART on the
117 service processor board as a regular serial port. To make use of
118 this feature serial driver support (CONFIG_SERIAL_8250) must be
121 WARNING: This software may not be supported or function
122 correctly on your IBM server. Please consult the IBM ServerProven
123 website <http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>
124 for information on the specific driver level and support statement
128 tristate "Sensable PHANToM (PCI)"
131 Say Y here if you want to build a driver for Sensable PHANToM device.
133 This driver is only for PCI PHANToMs.
135 If you choose to build module, its name will be phantom. If unsure,
139 tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard"
143 The PTI (Parallel Trace Interface) driver directs
144 trace data routed from various parts in the system out
145 through an Intel Penwell PTI port and out of the mobile
146 device for analysis with a debugging tool (Lauterbach or Fido).
148 You should select this driver if the target kernel is meant for
149 an Intel Atom (non-netbook) mobile device containing a MIPI
150 P1149.7 standard implementation.
153 tristate "SGI IOC4 Base IO support"
156 This option enables basic support for the IOC4 chip on certain
157 SGI IO controller cards (IO9, IO10, and PCI-RT). This option
158 does not enable any specific functions on such a card, but provides
159 necessary infrastructure for other drivers to utilize.
161 If you have an SGI Altix with an IOC4-based card say Y.
165 tristate "TI Flash Media interface support (EXPERIMENTAL)"
166 depends on EXPERIMENTAL && PCI
168 If you want support for Texas Instruments(R) Flash Media adapters
169 you should select this option and then also choose an appropriate
170 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
171 support', if you have a TI PCI74xx compatible card reader, for
173 You will also have to select some flash card format drivers. MMC/SD
174 cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
175 Interface support (MMC_TIFM_SD)'.
177 To compile this driver as a module, choose M here: the module will
181 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support (EXPERIMENTAL)"
182 depends on PCI && TIFM_CORE && EXPERIMENTAL
185 This option enables support for Texas Instruments(R) PCI74xx and
186 PCI76xx families of Flash Media adapters, found in many laptops.
187 To make actual use of the device, you will have to select some
188 flash card format drivers, as outlined in the TIFM_CORE Help.
190 To compile this driver as a module, choose M here: the module will
194 tristate "Integrated Circuits ICS932S401"
195 depends on I2C && EXPERIMENTAL
197 If you say yes here you get support for the Integrated Circuits
198 ICS932S401 clock control chips.
200 This driver can also be built as a module. If so, the module
201 will be called ics932s401.
204 tristate "Device driver for Atmel SSC peripheral"
205 depends on AVR32 || ARCH_AT91
207 This option enables device driver support for Atmel Synchronized
208 Serial Communication peripheral (SSC).
210 The SSC peripheral supports a wide variety of serial frame based
211 communications, i.e. I2S, SPI, etc.
215 config ENCLOSURE_SERVICES
216 tristate "Enclosure Services"
219 Provides support for intelligent enclosures (bays which
220 contain storage devices). You also need either a host
221 driver (SCSI/ATA) which supports enclosures
222 or a SCSI enclosure device (SES) to use these services.
225 tristate "Support communication between SGI SSIs"
227 depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
228 select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
229 select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
230 select SGI_GRU if X86_64 && SMP
232 An SGI machine can be divided into multiple Single System
233 Images which act independently of each other and have
234 hardware based memory protection from the others. Enabling
235 this feature will allow for direct communication between SSIs
236 based on a network adapter and DMA messaging.
239 tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
240 depends on PCI && X86 && MFD_CS5535
243 This driver provides access to MFGPT functionality for other
244 drivers that need timers. MFGPTs are available in the CS5535 and
245 CS5536 companion chips that are found in AMD Geode and several
246 other platforms. They have a better resolution and max interval
247 than the generic PIT, and are suitable for use as high-res timers.
248 You probably don't want to enable this manually; other drivers that
249 make use of it should enable it.
251 config CS5535_MFGPT_DEFAULT_IRQ
253 depends on CS5535_MFGPT
256 MFGPTs on the CS5535 require an interrupt. The selected IRQ
257 can be overridden as a module option as well as by driver that
258 use the cs5535_mfgpt_ API; however, different architectures might
259 want to use a different IRQ by default. This is here for
260 architectures to set as necessary.
262 config CS5535_CLOCK_EVENT_SRC
263 tristate "CS5535/CS5536 high-res timer (MFGPT) events"
264 depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
266 This driver provides a clock event source based on the MFGPT
267 timer(s) in the CS5535 and CS5536 companion chips.
268 MFGPTs have a better resolution and max interval than the
269 generic PIT, and are suitable for use as high-res timers.
272 tristate "Channel interface driver for the HP iLO processor"
276 The channel interface driver allows applications to communicate
277 with iLO management processors present on HP ProLiant servers.
278 Upon loading, the driver creates /dev/hpilo/dXccbN files, which
279 can be used to gather data from the management processor, via
280 read and write system calls.
282 To compile this driver as a module, choose M here: the
283 module will be called hpilo.
286 tristate "SGI GRU driver"
287 depends on X86_UV && SMP
291 The GRU is a hardware resource located in the system chipset. The GRU
292 contains memory that can be mmapped into the user address space. This memory is
293 used to communicate with the GRU to perform functions such as load/store,
294 scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
295 instructions using user virtual addresses. GRU instructions (ex., bcopy) use
296 user virtual addresses for operands.
298 If you are not running on a SGI UV system, say N.
301 bool "SGI GRU driver debug"
305 This option enables addition debugging code for the SGI GRU driver. If
306 you are unsure, say N.
309 tristate "Medfield Avago APDS9802 ALS Sensor module"
312 If you say yes here you get support for the ALS APDS9802 ambient
315 This driver can also be built as a module. If so, the module
316 will be called apds9802als.
319 tristate "Intersil ISL29003 ambient light sensor"
320 depends on I2C && SYSFS
322 If you say yes here you get support for the Intersil ISL29003
323 ambient light sensor.
325 This driver can also be built as a module. If so, the module
326 will be called isl29003.
329 tristate "Intersil ISL29020 ambient light sensor"
332 If you say yes here you get support for the Intersil ISL29020
333 ambient light sensor.
335 This driver can also be built as a module. If so, the module
336 will be called isl29020.
338 config SENSORS_TSL2550
339 tristate "Taos TSL2550 ambient light sensor"
340 depends on I2C && SYSFS
342 If you say yes here you get support for the Taos TSL2550
343 ambient light sensor.
345 This driver can also be built as a module. If so, the module
346 will be called tsl2550.
348 config SENSORS_BH1780
349 tristate "ROHM BH1780GLI ambient light sensor"
350 depends on I2C && SYSFS
352 If you say yes here you get support for the ROHM BH1780GLI
353 ambient light sensor.
355 This driver can also be built as a module. If so, the module
356 will be called bh1780gli.
358 config SENSORS_BH1770
359 tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
362 Say Y here if you want to build a driver for BH1770GLC (ROHM) or
363 SFH7770 (Osram) combined ambient light and proximity sensor chip.
365 To compile this driver as a module, choose M here: the
366 module will be called bh1770glc. If unsure, say N here.
368 config SENSORS_APDS990X
369 tristate "APDS990X combined als and proximity sensors"
373 Say Y here if you want to build a driver for Avago APDS990x
374 combined ambient light and proximity sensor chip.
376 To compile this driver as a module, choose M here: the
377 module will be called apds990x. If unsure, say N here.
380 tristate "Honeywell HMC6352 compass"
383 This driver provides support for the Honeywell HMC6352 compass,
384 providing configuration and heading data via sysfs.
387 tristate "EP93xx PWM support"
388 depends on ARCH_EP93XX
390 This option enables device driver support for the PWM channels
391 on the Cirrus EP93xx processors. The EP9307 chip only has one
392 PWM channel all the others have two, the second channel is an
393 alternate function of the EGPIO14 pin. A sysfs interface is
394 provided to control the PWM channels.
396 To compile this driver as a module, choose M here: the module will
397 be called ep93xx_pwm.
400 tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
401 depends on I2C && EXPERIMENTAL
403 If you say yes here you get support for Dallas Semiconductor
404 DS1682 Total Elapsed Time Recorder.
406 This driver can also be built as a module. If so, the module
407 will be called ds1682.
409 config SPEAR13XX_PCIE_GADGET
410 bool "PCIe gadget support for SPEAr13XX platform"
411 depends on ARCH_SPEAR13XX
414 This option enables gadget support for PCIe controller. If
415 board file defines any controller as PCIe endpoint then a sysfs
416 entry will be created for that controller. User can use these
417 sysfs node to configure PCIe EP as per his requirements.
420 tristate "Texas Instruments DAC7512"
421 depends on SPI && SYSFS
423 If you say yes here you get support for the Texas Instruments
424 DAC7512 16-bit digital-to-analog converter.
426 This driver can also be built as a module. If so, the module
427 will be called ti_dac7512.
429 config VMWARE_BALLOON
430 tristate "VMware Balloon Driver"
433 This is VMware physical memory management driver which acts
434 like a "balloon" that can be inflated to reclaim physical pages
435 by reserving them in the guest and invalidating them in the
436 monitor, freeing up the underlying machine pages so they can
437 be allocated to other guests. The balloon can also be deflated
438 to allow the guest to use more physical memory.
442 To compile this driver as a module, choose M here: the
443 module will be called vmw_balloon.
446 bool "ARM Ltd. Character LCD Driver"
447 depends on PLAT_VERSATILE
449 This is a driver for the character LCD found on the ARM Ltd.
450 Versatile and RealView Platform Baseboards. It doesn't do
451 very much more than display the text "ARM Linux" on the first
452 line and the Linux version on the second line, but that's
460 tristate "BMP085 digital pressure sensor on I2C"
463 depends on I2C && SYSFS
465 Say Y here if you want to support Bosch Sensortec's digital pressure
466 sensor hooked to an I2C bus.
468 To compile this driver as a module, choose M here: the
469 module will be called bmp085-i2c.
472 tristate "BMP085 digital pressure sensor on SPI"
475 depends on SPI_MASTER && SYSFS
477 Say Y here if you want to support Bosch Sensortec's digital pressure
478 sensor hooked to an SPI bus.
480 To compile this driver as a module, choose M here: the
481 module will be called bmp085-spi.
484 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
487 This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
488 Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
489 processor. The Topcliff has MAC address and Option ROM data in SROM.
490 This driver can access MAC address and Option ROM data in SROM.
492 This driver also can be used for LAPIS Semiconductor's IOH,
493 ML7213/ML7223/ML7831.
494 ML7213 which is for IVI(In-Vehicle Infotainment) use.
495 ML7223 IOH is for MP(Media Phone) use.
496 ML7831 IOH is for general purpose use.
497 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
498 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
500 To compile this driver as a module, choose M here: the module will
503 config USB_SWITCH_FSA9480
504 tristate "FSA9480 USB Switch"
507 The FSA9480 is a USB port accessory detector and switch.
508 The FSA9480 is fully controlled using I2C and enables USB data,
509 stereo and mono audio, video, microphone and UART data to use
510 a common connector port.
512 source "drivers/misc/c2port/Kconfig"
513 source "drivers/misc/eeprom/Kconfig"
514 source "drivers/misc/cb710/Kconfig"
515 source "drivers/misc/ti-st/Kconfig"
516 source "drivers/misc/lis3lv02d/Kconfig"
517 source "drivers/misc/carma/Kconfig"
518 source "drivers/misc/altera-stapl/Kconfig"
519 source "drivers/misc/mei/Kconfig"