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 "Atmel AT32/AT91 Timer/Counter Library"
65 depends on (AVR32 || ARCH_AT91)
66 default y if PREEMPT_RT_FULL
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.
84 config ATMEL_TCB_CLKSRC_BLOCK
86 depends on ATMEL_TCB_CLKSRC
87 prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X
91 Some chips provide more than one TC block, so you have the
92 choice of which one to use for the clock framework. The other
93 TC can be used for other purposes, such as PWM generation and
96 config ATMEL_TCB_CLKSRC_USE_SLOW_CLOCK
97 bool "TC Block use 32 KiHz clock"
98 depends on ATMEL_TCB_CLKSRC
99 default y if !PREEMPT_RT_FULL
101 Select this to use 32 KiHz base clock rate as TC block clock
102 source for clock events.
106 tristate "Dummy IRQ handler"
109 This module accepts a single 'irq' parameter, which it should register for.
110 The sole purpose of this module is to help with debugging of systems on
111 which spurious IRQs would happen on disabled IRQ vector.
114 tristate "Device driver for IBM RSA service processor"
115 depends on X86 && PCI && INPUT
117 This option enables device driver support for in-band access to the
118 IBM RSA (Condor) service processor in eServer xSeries systems.
119 The ibmasm device driver allows user space application to access
120 ASM (Advanced Systems Management) functions on the service
121 processor. The driver is meant to be used in conjunction with
123 The ibmasm driver also enables the OS to use the UART on the
124 service processor board as a regular serial port. To make use of
125 this feature serial driver support (CONFIG_SERIAL_8250) must be
128 WARNING: This software may not be supported or function
129 correctly on your IBM server. Please consult the IBM ServerProven
130 website <http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>
131 for information on the specific driver level and support statement
134 config HWLAT_DETECTOR
135 tristate "Testing module to detect hardware-induced latencies"
137 depends on RING_BUFFER
140 A simple hardware latency detector. Use this module to detect
141 large latencies introduced by the behavior of the underlying
142 system firmware external to Linux. We do this using periodic
143 use of stop_machine to grab all available CPUs and measure
144 for unexplainable gaps in the CPU timestamp counter(s). By
145 default, the module is not enabled until the "enable" file
146 within the "hwlat_detector" debugfs directory is toggled.
148 This module is often used to detect SMI (System Management
149 Interrupts) on x86 systems, though is not x86 specific. To
150 this end, we default to using a sample window of 1 second,
151 during which we will sample for 0.5 seconds. If an SMI or
152 similar event occurs during that time, it is recorded
153 into an 8K samples global ring buffer until retreived.
155 WARNING: This software should never be enabled (it can be built
156 but should not be turned on after it is loaded) in a production
157 environment where high latencies are a concern since the
158 sampling mechanism actually introduces latencies for
159 regular tasks while the CPU(s) are being held.
164 tristate "Sensable PHANToM (PCI)"
167 Say Y here if you want to build a driver for Sensable PHANToM device.
169 This driver is only for PCI PHANToMs.
171 If you choose to build module, its name will be phantom. If unsure,
175 tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard"
176 depends on PCI && TTY && (X86_INTEL_MID || COMPILE_TEST)
179 The PTI (Parallel Trace Interface) driver directs
180 trace data routed from various parts in the system out
181 through an Intel Penwell PTI port and out of the mobile
182 device for analysis with a debugging tool (Lauterbach or Fido).
184 You should select this driver if the target kernel is meant for
185 an Intel Atom (non-netbook) mobile device containing a MIPI
186 P1149.7 standard implementation.
189 tristate "SGI IOC4 Base IO support"
192 This option enables basic support for the IOC4 chip on certain
193 SGI IO controller cards (IO9, IO10, and PCI-RT). This option
194 does not enable any specific functions on such a card, but provides
195 necessary infrastructure for other drivers to utilize.
197 If you have an SGI Altix with an IOC4-based card say Y.
201 tristate "TI Flash Media interface support"
204 If you want support for Texas Instruments(R) Flash Media adapters
205 you should select this option and then also choose an appropriate
206 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
207 support', if you have a TI PCI74xx compatible card reader, for
209 You will also have to select some flash card format drivers. MMC/SD
210 cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
211 Interface support (MMC_TIFM_SD)'.
213 To compile this driver as a module, choose M here: the module will
217 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support"
218 depends on PCI && TIFM_CORE
221 This option enables support for Texas Instruments(R) PCI74xx and
222 PCI76xx families of Flash Media adapters, found in many laptops.
223 To make actual use of the device, you will have to select some
224 flash card format drivers, as outlined in the TIFM_CORE Help.
226 To compile this driver as a module, choose M here: the module will
230 tristate "Integrated Circuits ICS932S401"
233 If you say yes here you get support for the Integrated Circuits
234 ICS932S401 clock control chips.
236 This driver can also be built as a module. If so, the module
237 will be called ics932s401.
240 tristate "Device driver for Atmel SSC peripheral"
243 This option enables device driver support for Atmel Synchronized
244 Serial Communication peripheral (SSC).
246 The SSC peripheral supports a wide variety of serial frame based
247 communications, i.e. I2S, SPI, etc.
251 config ENCLOSURE_SERVICES
252 tristate "Enclosure Services"
255 Provides support for intelligent enclosures (bays which
256 contain storage devices). You also need either a host
257 driver (SCSI/ATA) which supports enclosures
258 or a SCSI enclosure device (SES) to use these services.
261 tristate "Support communication between SGI SSIs"
263 depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
264 select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
265 select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
266 select SGI_GRU if X86_64 && SMP
268 An SGI machine can be divided into multiple Single System
269 Images which act independently of each other and have
270 hardware based memory protection from the others. Enabling
271 this feature will allow for direct communication between SSIs
272 based on a network adapter and DMA messaging.
275 tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
276 depends on PCI && X86 && MFD_CS5535
279 This driver provides access to MFGPT functionality for other
280 drivers that need timers. MFGPTs are available in the CS5535 and
281 CS5536 companion chips that are found in AMD Geode and several
282 other platforms. They have a better resolution and max interval
283 than the generic PIT, and are suitable for use as high-res timers.
284 You probably don't want to enable this manually; other drivers that
285 make use of it should enable it.
287 config CS5535_MFGPT_DEFAULT_IRQ
289 depends on CS5535_MFGPT
292 MFGPTs on the CS5535 require an interrupt. The selected IRQ
293 can be overridden as a module option as well as by driver that
294 use the cs5535_mfgpt_ API; however, different architectures might
295 want to use a different IRQ by default. This is here for
296 architectures to set as necessary.
298 config CS5535_CLOCK_EVENT_SRC
299 tristate "CS5535/CS5536 high-res timer (MFGPT) events"
300 depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
302 This driver provides a clock event source based on the MFGPT
303 timer(s) in the CS5535 and CS5536 companion chips.
304 MFGPTs have a better resolution and max interval than the
305 generic PIT, and are suitable for use as high-res timers.
308 tristate "Channel interface driver for the HP iLO processor"
312 The channel interface driver allows applications to communicate
313 with iLO management processors present on HP ProLiant servers.
314 Upon loading, the driver creates /dev/hpilo/dXccbN files, which
315 can be used to gather data from the management processor, via
316 read and write system calls.
318 To compile this driver as a module, choose M here: the
319 module will be called hpilo.
322 tristate "SGI GRU driver"
323 depends on X86_UV && SMP
327 The GRU is a hardware resource located in the system chipset. The GRU
328 contains memory that can be mmapped into the user address space. This memory is
329 used to communicate with the GRU to perform functions such as load/store,
330 scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
331 instructions using user virtual addresses. GRU instructions (ex., bcopy) use
332 user virtual addresses for operands.
334 If you are not running on a SGI UV system, say N.
337 bool "SGI GRU driver debug"
341 This option enables addition debugging code for the SGI GRU driver. If
342 you are unsure, say N.
345 tristate "Medfield Avago APDS9802 ALS Sensor module"
348 If you say yes here you get support for the ALS APDS9802 ambient
351 This driver can also be built as a module. If so, the module
352 will be called apds9802als.
355 tristate "Intersil ISL29020 ambient light sensor"
358 If you say yes here you get support for the Intersil ISL29020
359 ambient light sensor.
361 This driver can also be built as a module. If so, the module
362 will be called isl29020.
365 tristate "Intersil ISL22317 digitally controlled potentiometer"
366 depends on I2C && SYSFS
368 If you say yes here you get support for the Intersil ISL22317
369 precision single digitally controlled potentiometer.
371 This driver can also be built as a module. If so, the module
372 will be called isl22317.
375 tristate "Intersil ISL29003 ambient light sensor"
376 depends on I2C && SYSFS
378 If you say yes here you get support for the Intersil ISL29003
379 ambient light sensor.
381 This driver can also be built as a module. If so, the module
382 will be called isl29003.
385 tristate "Linear Technology LTC4306 bus multiplexer"
386 depends on I2C && SYSFS
388 If you say yes here you get support for the LTC4306
389 4-channel 2-Wire Bus Multiplexer with Capacitance Buffering.
391 This driver can also be built as a module. If so, the module
392 will be called ltc4306.
395 tristate "Texas Instruments 8-ch power supply sequencer and monitor"
396 depends on I2C && SYSFS
398 If you say yes here you get support for the UCD9080
399 Texas Instruments 8-ch power supply sequencer and monitor.
401 This driver can also be built as a module. If so, the module
402 will be called ucd9080.
405 tristate "i2c p2pmc device"
406 depends on I2C && SYSFS
408 If you say yes here you get support for the I2C P2PMC
411 This driver can also be built as a module. If so, the module
412 will be called i2c_p2pmc.
414 config SENSORS_TSL2550
415 tristate "Taos TSL2550 ambient light sensor"
416 depends on I2C && SYSFS
418 If you say yes here you get support for the Taos TSL2550
419 ambient light sensor.
421 This driver can also be built as a module. If so, the module
422 will be called tsl2550.
424 config SENSORS_BH1780
425 tristate "ROHM BH1780GLI ambient light sensor"
426 depends on I2C && SYSFS
428 If you say yes here you get support for the ROHM BH1780GLI
429 ambient light sensor.
431 This driver can also be built as a module. If so, the module
432 will be called bh1780gli.
434 config SENSORS_BH1770
435 tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
438 Say Y here if you want to build a driver for BH1770GLC (ROHM) or
439 SFH7770 (Osram) combined ambient light and proximity sensor chip.
441 To compile this driver as a module, choose M here: the
442 module will be called bh1770glc. If unsure, say N here.
444 config SENSORS_APDS990X
445 tristate "APDS990X combined als and proximity sensors"
449 Say Y here if you want to build a driver for Avago APDS990x
450 combined ambient light and proximity sensor chip.
452 To compile this driver as a module, choose M here: the
453 module will be called apds990x. If unsure, say N here.
456 tristate "Honeywell HMC6352 compass"
459 This driver provides support for the Honeywell HMC6352 compass,
460 providing configuration and heading data via sysfs.
463 tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
466 If you say yes here you get support for Dallas Semiconductor
467 DS1682 Total Elapsed Time Recorder.
469 This driver can also be built as a module. If so, the module
470 will be called ds1682.
472 config SPEAR13XX_PCIE_GADGET
473 bool "PCIe gadget support for SPEAr13XX platform"
474 depends on ARCH_SPEAR13XX && BROKEN
477 This option enables gadget support for PCIe controller. If
478 board file defines any controller as PCIe endpoint then a sysfs
479 entry will be created for that controller. User can use these
480 sysfs node to configure PCIe EP as per his requirements.
483 tristate "Texas Instruments DAC7512"
484 depends on SPI && SYSFS
486 If you say yes here you get support for the Texas Instruments
487 DAC7512 16-bit digital-to-analog converter.
489 This driver can also be built as a module. If so, the module
490 will be called ti_dac7512.
492 config VMWARE_BALLOON
493 tristate "VMware Balloon Driver"
494 depends on X86 && HYPERVISOR_GUEST
496 This is VMware physical memory management driver which acts
497 like a "balloon" that can be inflated to reclaim physical pages
498 by reserving them in the guest and invalidating them in the
499 monitor, freeing up the underlying machine pages so they can
500 be allocated to other guests. The balloon can also be deflated
501 to allow the guest to use more physical memory.
505 To compile this driver as a module, choose M here: the
506 module will be called vmw_balloon.
509 bool "ARM Ltd. Character LCD Driver"
510 depends on PLAT_VERSATILE
512 This is a driver for the character LCD found on the ARM Ltd.
513 Versatile and RealView Platform Baseboards. It doesn't do
514 very much more than display the text "ARM Linux" on the first
515 line and the Linux version on the second line, but that's
523 tristate "BMP085 digital pressure sensor on I2C"
526 depends on I2C && SYSFS
528 Say Y here if you want to support Bosch Sensortec's digital pressure
529 sensor hooked to an I2C bus.
531 To compile this driver as a module, choose M here: the
532 module will be called bmp085-i2c.
535 tristate "BMP085 digital pressure sensor on SPI"
538 depends on SPI_MASTER && SYSFS
540 Say Y here if you want to support Bosch Sensortec's digital pressure
541 sensor hooked to an SPI bus.
543 To compile this driver as a module, choose M here: the
544 module will be called bmp085-spi.
547 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
548 select GENERIC_NET_UTILS
551 This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
552 Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
553 processor. The Topcliff has MAC address and Option ROM data in SROM.
554 This driver can access MAC address and Option ROM data in SROM.
556 This driver also can be used for LAPIS Semiconductor's IOH,
557 ML7213/ML7223/ML7831.
558 ML7213 which is for IVI(In-Vehicle Infotainment) use.
559 ML7223 IOH is for MP(Media Phone) use.
560 ML7831 IOH is for general purpose use.
561 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
562 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
564 To compile this driver as a module, choose M here: the module will
567 config USB_SWITCH_FSA9480
568 tristate "FSA9480 USB Switch"
571 The FSA9480 is a USB port accessory detector and switch.
572 The FSA9480 is fully controlled using I2C and enables USB data,
573 stereo and mono audio, video, microphone and UART data to use
574 a common connector port.
576 config LATTICE_ECP3_CONFIG
577 tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
578 depends on SPI && SYSFS
582 This option enables support for bitstream configuration (programming
583 or loading) of the Lattice ECP3 FPGA family via SPI.
588 bool "Generic on-chip SRAM driver"
590 select GENERIC_ALLOCATOR
592 This driver allows you to declare a memory region to be managed by
593 the genalloc API. It is supposed to be used for small on-chip SRAM
594 areas found on many SoCs.
596 source "drivers/misc/c2port/Kconfig"
597 source "drivers/misc/eeprom/Kconfig"
598 source "drivers/misc/cb710/Kconfig"
599 source "drivers/misc/ti-st/Kconfig"
600 source "drivers/misc/lis3lv02d/Kconfig"
601 source "drivers/misc/carma/Kconfig"
602 source "drivers/misc/altera-stapl/Kconfig"
603 source "drivers/misc/mei/Kconfig"
604 source "drivers/misc/vmw_vmci/Kconfig"
605 source "drivers/misc/mic/Kconfig"
606 source "drivers/misc/genwqe/Kconfig"