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 bool "Atmel AT32/AT91 Timer/Counter Library"
56 depends on (AVR32 || ARCH_AT91)
58 Select this if you want a library to allocate the Timer/Counter
59 blocks found on many Atmel processors. This facilitates using
60 these blocks by different drivers despite processor differences.
62 config ATMEL_TCB_CLKSRC
63 bool "TC Block Clocksource"
64 depends on ATMEL_TCLIB
67 Select this to get a high precision clocksource based on a
68 TC block with a 5+ MHz base clock rate. Two timer channels
69 are combined to make a single 32-bit timer.
71 When GENERIC_CLOCKEVENTS is defined, the third timer channel
72 may be used as a clock event device supporting oneshot mode
73 (delays of up to two seconds) based on the 32 KiHz clock.
75 config ATMEL_TCB_CLKSRC_BLOCK
77 depends on ATMEL_TCB_CLKSRC
78 prompt "TC Block" if CPU_AT32AP700X
82 Some chips provide more than one TC block, so you have the
83 choice of which one to use for the clock framework. The other
84 TC can be used for other purposes, such as PWM generation and
88 tristate "Dummy IRQ handler"
91 This module accepts a single 'irq' parameter, which it should register for.
92 The sole purpose of this module is to help with debugging of systems on
93 which spurious IRQs would happen on disabled IRQ vector.
96 tristate "Device driver for IBM RSA service processor"
97 depends on X86 && PCI && INPUT
98 depends on SERIAL_8250 || SERIAL_8250=n
100 This option enables device driver support for in-band access to the
101 IBM RSA (Condor) service processor in eServer xSeries systems.
102 The ibmasm device driver allows user space application to access
103 ASM (Advanced Systems Management) functions on the service
104 processor. The driver is meant to be used in conjunction with
106 The ibmasm driver also enables the OS to use the UART on the
107 service processor board as a regular serial port. To make use of
108 this feature serial driver support (CONFIG_SERIAL_8250) must be
111 WARNING: This software may not be supported or function
112 correctly on your IBM server. Please consult the IBM ServerProven
113 website <http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>
114 for information on the specific driver level and support statement
118 tristate "Sensable PHANToM (PCI)"
121 Say Y here if you want to build a driver for Sensable PHANToM device.
123 This driver is only for PCI PHANToMs.
125 If you choose to build module, its name will be phantom. If unsure,
129 tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard"
130 depends on PCI && TTY && (X86_INTEL_MID || COMPILE_TEST)
133 The PTI (Parallel Trace Interface) driver directs
134 trace data routed from various parts in the system out
135 through an Intel Penwell PTI port and out of the mobile
136 device for analysis with a debugging tool (Lauterbach or Fido).
138 You should select this driver if the target kernel is meant for
139 an Intel Atom (non-netbook) mobile device containing a MIPI
140 P1149.7 standard implementation.
143 tristate "SGI IOC4 Base IO support"
146 This option enables basic support for the IOC4 chip on certain
147 SGI IO controller cards (IO9, IO10, and PCI-RT). This option
148 does not enable any specific functions on such a card, but provides
149 necessary infrastructure for other drivers to utilize.
151 If you have an SGI Altix with an IOC4-based card say Y.
155 tristate "TI Flash Media interface support"
158 If you want support for Texas Instruments(R) Flash Media adapters
159 you should select this option and then also choose an appropriate
160 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
161 support', if you have a TI PCI74xx compatible card reader, for
163 You will also have to select some flash card format drivers. MMC/SD
164 cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
165 Interface support (MMC_TIFM_SD)'.
167 To compile this driver as a module, choose M here: the module will
171 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support"
172 depends on PCI && TIFM_CORE
175 This option enables support for Texas Instruments(R) PCI74xx and
176 PCI76xx families of Flash Media adapters, found in many laptops.
177 To make actual use of the device, you will have to select some
178 flash card format drivers, as outlined in the TIFM_CORE Help.
180 To compile this driver as a module, choose M here: the module will
184 tristate "Integrated Circuits ICS932S401"
187 If you say yes here you get support for the Integrated Circuits
188 ICS932S401 clock control chips.
190 This driver can also be built as a module. If so, the module
191 will be called ics932s401.
194 tristate "Device driver for Atmel SSC peripheral"
195 depends on HAS_IOMEM && (AVR32 || ARCH_AT91 || COMPILE_TEST)
197 This option enables device driver support for Atmel Synchronized
198 Serial Communication peripheral (SSC).
200 The SSC peripheral supports a wide variety of serial frame based
201 communications, i.e. I2S, SPI, etc.
205 config ENCLOSURE_SERVICES
206 tristate "Enclosure Services"
209 Provides support for intelligent enclosures (bays which
210 contain storage devices). You also need either a host
211 driver (SCSI/ATA) which supports enclosures
212 or a SCSI enclosure device (SES) to use these services.
215 tristate "Support communication between SGI SSIs"
217 depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
218 select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
219 select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
220 select SGI_GRU if X86_64 && SMP
222 An SGI machine can be divided into multiple Single System
223 Images which act independently of each other and have
224 hardware based memory protection from the others. Enabling
225 this feature will allow for direct communication between SSIs
226 based on a network adapter and DMA messaging.
229 tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
230 depends on MFD_CS5535
233 This driver provides access to MFGPT functionality for other
234 drivers that need timers. MFGPTs are available in the CS5535 and
235 CS5536 companion chips that are found in AMD Geode and several
236 other platforms. They have a better resolution and max interval
237 than the generic PIT, and are suitable for use as high-res timers.
238 You probably don't want to enable this manually; other drivers that
239 make use of it should enable it.
241 config CS5535_MFGPT_DEFAULT_IRQ
243 depends on CS5535_MFGPT
246 MFGPTs on the CS5535 require an interrupt. The selected IRQ
247 can be overridden as a module option as well as by driver that
248 use the cs5535_mfgpt_ API; however, different architectures might
249 want to use a different IRQ by default. This is here for
250 architectures to set as necessary.
252 config CS5535_CLOCK_EVENT_SRC
253 tristate "CS5535/CS5536 high-res timer (MFGPT) events"
254 depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
256 This driver provides a clock event source based on the MFGPT
257 timer(s) in the CS5535 and CS5536 companion chips.
258 MFGPTs have a better resolution and max interval than the
259 generic PIT, and are suitable for use as high-res timers.
262 tristate "Channel interface driver for the HP iLO processor"
266 The channel interface driver allows applications to communicate
267 with iLO management processors present on HP ProLiant servers.
268 Upon loading, the driver creates /dev/hpilo/dXccbN files, which
269 can be used to gather data from the management processor, via
270 read and write system calls.
272 To compile this driver as a module, choose M here: the
273 module will be called hpilo.
276 tristate "Qualcomm coincell charger support"
277 depends on MFD_SPMI_PMIC || COMPILE_TEST
279 This driver supports the coincell block found inside of
280 Qualcomm PMICs. The coincell charger provides a means to
281 charge a coincell battery or backup capacitor which is used
282 to maintain PMIC register and RTC state in the absence of
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 additional debugging code for the SGI GRU driver.
306 If 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 "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
390 If you say yes here you get support for Dallas Semiconductor
391 DS1682 Total Elapsed Time Recorder.
393 This driver can also be built as a module. If so, the module
394 will be called ds1682.
396 config SPEAR13XX_PCIE_GADGET
397 bool "PCIe gadget support for SPEAr13XX platform"
398 depends on ARCH_SPEAR13XX && BROKEN
401 This option enables gadget support for PCIe controller. If
402 board file defines any controller as PCIe endpoint then a sysfs
403 entry will be created for that controller. User can use these
404 sysfs node to configure PCIe EP as per his requirements.
407 tristate "Texas Instruments DAC7512"
408 depends on SPI && SYSFS
410 If you say yes here you get support for the Texas Instruments
411 DAC7512 16-bit digital-to-analog converter.
413 This driver can also be built as a module. If so, the module
414 will be called ti_dac7512.
416 config VMWARE_BALLOON
417 tristate "VMware Balloon Driver"
418 depends on VMWARE_VMCI && X86 && HYPERVISOR_GUEST
420 This is VMware physical memory management driver which acts
421 like a "balloon" that can be inflated to reclaim physical pages
422 by reserving them in the guest and invalidating them in the
423 monitor, freeing up the underlying machine pages so they can
424 be allocated to other guests. The balloon can also be deflated
425 to allow the guest to use more physical memory.
429 To compile this driver as a module, choose M here: the
430 module will be called vmw_balloon.
433 bool "ARM Ltd. Character LCD Driver"
434 depends on PLAT_VERSATILE
436 This is a driver for the character LCD found on the ARM Ltd.
437 Versatile and RealView Platform Baseboards. It doesn't do
438 very much more than display the text "ARM Linux" on the first
439 line and the Linux version on the second line, but that's
447 tristate "BMP085 digital pressure sensor on I2C"
450 depends on I2C && SYSFS
452 Say Y here if you want to support Bosch Sensortec's digital pressure
453 sensor hooked to an I2C bus.
455 To compile this driver as a module, choose M here: the
456 module will be called bmp085-i2c.
459 tristate "BMP085 digital pressure sensor on SPI"
462 depends on SPI_MASTER && SYSFS
464 Say Y here if you want to support Bosch Sensortec's digital pressure
465 sensor hooked to an SPI bus.
467 To compile this driver as a module, choose M here: the
468 module will be called bmp085-spi.
471 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
472 select GENERIC_NET_UTILS
473 depends on PCI && (X86_32 || COMPILE_TEST)
475 This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
476 Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
477 processor. The Topcliff has MAC address and Option ROM data in SROM.
478 This driver can access MAC address and Option ROM data in SROM.
480 This driver also can be used for LAPIS Semiconductor's IOH,
481 ML7213/ML7223/ML7831.
482 ML7213 which is for IVI(In-Vehicle Infotainment) use.
483 ML7223 IOH is for MP(Media Phone) use.
484 ML7831 IOH is for general purpose use.
485 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
486 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
488 To compile this driver as a module, choose M here: the module will
491 config USB_SWITCH_FSA9480
492 tristate "FSA9480 USB Switch"
495 The FSA9480 is a USB port accessory detector and switch.
496 The FSA9480 is fully controlled using I2C and enables USB data,
497 stereo and mono audio, video, microphone and UART data to use
498 a common connector port.
500 config LATTICE_ECP3_CONFIG
501 tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
502 depends on SPI && SYSFS
506 This option enables support for bitstream configuration (programming
507 or loading) of the Lattice ECP3 FPGA family via SPI.
512 bool "Generic on-chip SRAM driver"
514 select GENERIC_ALLOCATOR
516 This driver allows you to declare a memory region to be managed by
517 the genalloc API. It is supposed to be used for small on-chip SRAM
518 areas found on many SoCs.
520 config VEXPRESS_SYSCFG
521 bool "Versatile Express System Configuration driver"
522 depends on VEXPRESS_CONFIG
525 ARM Ltd. Versatile Express uses specialised platform configuration
526 bus. System Configuration interface is one of the possible means
527 of generating transactions on this bus.
529 source "drivers/misc/c2port/Kconfig"
530 source "drivers/misc/eeprom/Kconfig"
531 source "drivers/misc/cb710/Kconfig"
532 source "drivers/misc/ti-st/Kconfig"
533 source "drivers/misc/lis3lv02d/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"
540 source "drivers/misc/cxl/Kconfig"