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"
57 depends on AVR32 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91SAM9G45
59 This option enables device driver support for the PWM channels
60 on certain Atmel processors. Pulse Width Modulation is used for
61 purposes including software controlled power-efficient backlights
62 on LCD displays, motor control, and waveform generation.
65 bool "Atmel AT32/AT91 Timer/Counter Library"
66 depends on (AVR32 || ARCH_AT91)
68 Select this if you want a library to allocate the Timer/Counter
69 blocks found on many Atmel processors. This facilitates using
70 these blocks by different drivers despite processor differences.
72 config ATMEL_TCB_CLKSRC
73 bool "TC Block Clocksource"
74 depends on ATMEL_TCLIB
77 Select this to get a high precision clocksource based on a
78 TC block with a 5+ MHz base clock rate. Two timer channels
79 are combined to make a single 32-bit timer.
81 When GENERIC_CLOCKEVENTS is defined, the third timer channel
82 may be used as a clock event device supporting oneshot mode
83 (delays of up to two seconds) based on the 32 KiHz clock.
85 config ATMEL_TCB_CLKSRC_BLOCK
87 depends on ATMEL_TCB_CLKSRC
88 prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X
92 Some chips provide more than one TC block, so you have the
93 choice of which one to use for the clock framework. The other
94 TC can be used for other purposes, such as PWM generation and
98 tristate "Dummy IRQ handler"
101 This module accepts a single 'irq' parameter, which it should register for.
102 The sole purpose of this module is to help with debugging of systems on
103 which spurious IRQs would happen on disabled IRQ vector.
106 tristate "Device driver for IBM RSA service processor"
107 depends on X86 && PCI && INPUT
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"
139 depends on PCI && TTY && (X86_INTEL_MID || COMPILE_TEST)
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"
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"
181 depends on PCI && TIFM_CORE
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"
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 HAS_IOMEM && (AVR32 || ARCH_AT91 || COMPILE_TEST)
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.
224 tristate "Support communication between SGI SSIs"
226 depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
227 select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
228 select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
229 select SGI_GRU if X86_64 && SMP
231 An SGI machine can be divided into multiple Single System
232 Images which act independently of each other and have
233 hardware based memory protection from the others. Enabling
234 this feature will allow for direct communication between SSIs
235 based on a network adapter and DMA messaging.
238 tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
239 depends on MFD_CS5535
242 This driver provides access to MFGPT functionality for other
243 drivers that need timers. MFGPTs are available in the CS5535 and
244 CS5536 companion chips that are found in AMD Geode and several
245 other platforms. They have a better resolution and max interval
246 than the generic PIT, and are suitable for use as high-res timers.
247 You probably don't want to enable this manually; other drivers that
248 make use of it should enable it.
250 config CS5535_MFGPT_DEFAULT_IRQ
252 depends on CS5535_MFGPT
255 MFGPTs on the CS5535 require an interrupt. The selected IRQ
256 can be overridden as a module option as well as by driver that
257 use the cs5535_mfgpt_ API; however, different architectures might
258 want to use a different IRQ by default. This is here for
259 architectures to set as necessary.
261 config CS5535_CLOCK_EVENT_SRC
262 tristate "CS5535/CS5536 high-res timer (MFGPT) events"
263 depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
265 This driver provides a clock event source based on the MFGPT
266 timer(s) in the CS5535 and CS5536 companion chips.
267 MFGPTs have a better resolution and max interval than the
268 generic PIT, and are suitable for use as high-res timers.
271 tristate "Channel interface driver for the HP iLO processor"
275 The channel interface driver allows applications to communicate
276 with iLO management processors present on HP ProLiant servers.
277 Upon loading, the driver creates /dev/hpilo/dXccbN files, which
278 can be used to gather data from the management processor, via
279 read and write system calls.
281 To compile this driver as a module, choose M here: the
282 module will be called hpilo.
285 tristate "SGI GRU driver"
286 depends on X86_UV && SMP
290 The GRU is a hardware resource located in the system chipset. The GRU
291 contains memory that can be mmapped into the user address space. This memory is
292 used to communicate with the GRU to perform functions such as load/store,
293 scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
294 instructions using user virtual addresses. GRU instructions (ex., bcopy) use
295 user virtual addresses for operands.
297 If you are not running on a SGI UV system, say N.
300 bool "SGI GRU driver debug"
304 This option enables additional debugging code for the SGI GRU driver.
305 If you are unsure, say N.
308 tristate "Medfield Avago APDS9802 ALS Sensor module"
311 If you say yes here you get support for the ALS APDS9802 ambient
314 This driver can also be built as a module. If so, the module
315 will be called apds9802als.
318 tristate "Intersil ISL29003 ambient light sensor"
319 depends on I2C && SYSFS
321 If you say yes here you get support for the Intersil ISL29003
322 ambient light sensor.
324 This driver can also be built as a module. If so, the module
325 will be called isl29003.
328 tristate "Intersil ISL29020 ambient light sensor"
331 If you say yes here you get support for the Intersil ISL29020
332 ambient light sensor.
334 This driver can also be built as a module. If so, the module
335 will be called isl29020.
337 config SENSORS_TSL2550
338 tristate "Taos TSL2550 ambient light sensor"
339 depends on I2C && SYSFS
341 If you say yes here you get support for the Taos TSL2550
342 ambient light sensor.
344 This driver can also be built as a module. If so, the module
345 will be called tsl2550.
347 config SENSORS_BH1780
348 tristate "ROHM BH1780GLI ambient light sensor"
349 depends on I2C && SYSFS
351 If you say yes here you get support for the ROHM BH1780GLI
352 ambient light sensor.
354 This driver can also be built as a module. If so, the module
355 will be called bh1780gli.
357 config SENSORS_BH1770
358 tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
361 Say Y here if you want to build a driver for BH1770GLC (ROHM) or
362 SFH7770 (Osram) combined ambient light and proximity sensor chip.
364 To compile this driver as a module, choose M here: the
365 module will be called bh1770glc. If unsure, say N here.
367 config SENSORS_APDS990X
368 tristate "APDS990X combined als and proximity sensors"
372 Say Y here if you want to build a driver for Avago APDS990x
373 combined ambient light and proximity sensor chip.
375 To compile this driver as a module, choose M here: the
376 module will be called apds990x. If unsure, say N here.
379 tristate "Honeywell HMC6352 compass"
382 This driver provides support for the Honeywell HMC6352 compass,
383 providing configuration and heading data via sysfs.
386 tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
389 If you say yes here you get support for Dallas Semiconductor
390 DS1682 Total Elapsed Time Recorder.
392 This driver can also be built as a module. If so, the module
393 will be called ds1682.
395 config SPEAR13XX_PCIE_GADGET
396 bool "PCIe gadget support for SPEAr13XX platform"
397 depends on ARCH_SPEAR13XX && BROKEN
400 This option enables gadget support for PCIe controller. If
401 board file defines any controller as PCIe endpoint then a sysfs
402 entry will be created for that controller. User can use these
403 sysfs node to configure PCIe EP as per his requirements.
406 tristate "Texas Instruments DAC7512"
407 depends on SPI && SYSFS
409 If you say yes here you get support for the Texas Instruments
410 DAC7512 16-bit digital-to-analog converter.
412 This driver can also be built as a module. If so, the module
413 will be called ti_dac7512.
415 config VMWARE_BALLOON
416 tristate "VMware Balloon Driver"
417 depends on X86 && HYPERVISOR_GUEST
419 This is VMware physical memory management driver which acts
420 like a "balloon" that can be inflated to reclaim physical pages
421 by reserving them in the guest and invalidating them in the
422 monitor, freeing up the underlying machine pages so they can
423 be allocated to other guests. The balloon can also be deflated
424 to allow the guest to use more physical memory.
428 To compile this driver as a module, choose M here: the
429 module will be called vmw_balloon.
432 bool "ARM Ltd. Character LCD Driver"
433 depends on PLAT_VERSATILE
435 This is a driver for the character LCD found on the ARM Ltd.
436 Versatile and RealView Platform Baseboards. It doesn't do
437 very much more than display the text "ARM Linux" on the first
438 line and the Linux version on the second line, but that's
446 tristate "BMP085 digital pressure sensor on I2C"
449 depends on I2C && SYSFS
451 Say Y here if you want to support Bosch Sensortec's digital pressure
452 sensor hooked to an I2C bus.
454 To compile this driver as a module, choose M here: the
455 module will be called bmp085-i2c.
458 tristate "BMP085 digital pressure sensor on SPI"
461 depends on SPI_MASTER && SYSFS
463 Say Y here if you want to support Bosch Sensortec's digital pressure
464 sensor hooked to an SPI bus.
466 To compile this driver as a module, choose M here: the
467 module will be called bmp085-spi.
470 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
471 select GENERIC_NET_UTILS
472 depends on PCI && (X86_32 || COMPILE_TEST)
474 This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
475 Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
476 processor. The Topcliff has MAC address and Option ROM data in SROM.
477 This driver can access MAC address and Option ROM data in SROM.
479 This driver also can be used for LAPIS Semiconductor's IOH,
480 ML7213/ML7223/ML7831.
481 ML7213 which is for IVI(In-Vehicle Infotainment) use.
482 ML7223 IOH is for MP(Media Phone) use.
483 ML7831 IOH is for general purpose use.
484 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
485 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
487 To compile this driver as a module, choose M here: the module will
490 config USB_SWITCH_FSA9480
491 tristate "FSA9480 USB Switch"
494 The FSA9480 is a USB port accessory detector and switch.
495 The FSA9480 is fully controlled using I2C and enables USB data,
496 stereo and mono audio, video, microphone and UART data to use
497 a common connector port.
499 config LATTICE_ECP3_CONFIG
500 tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
501 depends on SPI && SYSFS
505 This option enables support for bitstream configuration (programming
506 or loading) of the Lattice ECP3 FPGA family via SPI.
511 bool "Generic on-chip SRAM driver"
513 select GENERIC_ALLOCATOR
515 This driver allows you to declare a memory region to be managed by
516 the genalloc API. It is supposed to be used for small on-chip SRAM
517 areas found on many SoCs.
519 config VEXPRESS_SYSCFG
520 bool "Versatile Express System Configuration driver"
521 depends on VEXPRESS_CONFIG
524 ARM Ltd. Versatile Express uses specialised platform configuration
525 bus. System Configuration interface is one of the possible means
526 of generating transactions on this bus.
528 source "drivers/misc/c2port/Kconfig"
529 source "drivers/misc/eeprom/Kconfig"
530 source "drivers/misc/cb710/Kconfig"
531 source "drivers/misc/ti-st/Kconfig"
532 source "drivers/misc/lis3lv02d/Kconfig"
533 source "drivers/misc/carma/Kconfig"
534 source "drivers/misc/altera-stapl/Kconfig"
535 source "drivers/misc/mei/Kconfig"
536 source "drivers/misc/vmw_vmci/Kconfig"
537 source "drivers/misc/mic/Kconfig"
538 source "drivers/misc/genwqe/Kconfig"
539 source "drivers/misc/echo/Kconfig"