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)
57 default y if PREEMPT_RT_FULL
59 Select this if you want a library to allocate the Timer/Counter
60 blocks found on many Atmel processors. This facilitates using
61 these blocks by different drivers despite processor differences.
63 config ATMEL_TCB_CLKSRC
64 bool "TC Block Clocksource"
65 depends on ATMEL_TCLIB
68 Select this to get a high precision clocksource based on a
69 TC block with a 5+ MHz base clock rate. Two timer channels
70 are combined to make a single 32-bit timer.
72 When GENERIC_CLOCKEVENTS is defined, the third timer channel
73 may be used as a clock event device supporting oneshot mode.
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
87 config ATMEL_TCB_CLKSRC_USE_SLOW_CLOCK
88 bool "TC Block use 32 KiHz clock"
89 depends on ATMEL_TCB_CLKSRC
90 default y if !PREEMPT_RT_FULL
92 Select this to use 32 KiHz base clock rate as TC block clock
93 source for clock events.
97 tristate "Dummy IRQ handler"
100 This module accepts a single 'irq' parameter, which it should register for.
101 The sole purpose of this module is to help with debugging of systems on
102 which spurious IRQs would happen on disabled IRQ vector.
105 tristate "Device driver for IBM RSA service processor"
106 depends on X86 && PCI && INPUT
108 This option enables device driver support for in-band access to the
109 IBM RSA (Condor) service processor in eServer xSeries systems.
110 The ibmasm device driver allows user space application to access
111 ASM (Advanced Systems Management) functions on the service
112 processor. The driver is meant to be used in conjunction with
114 The ibmasm driver also enables the OS to use the UART on the
115 service processor board as a regular serial port. To make use of
116 this feature serial driver support (CONFIG_SERIAL_8250) must be
119 WARNING: This software may not be supported or function
120 correctly on your IBM server. Please consult the IBM ServerProven
121 website <http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>
122 for information on the specific driver level and support statement
125 config HWLAT_DETECTOR
126 tristate "Testing module to detect hardware-induced latencies"
128 depends on RING_BUFFER
131 A simple hardware latency detector. Use this module to detect
132 large latencies introduced by the behavior of the underlying
133 system firmware external to Linux. We do this using periodic
134 use of stop_machine to grab all available CPUs and measure
135 for unexplainable gaps in the CPU timestamp counter(s). By
136 default, the module is not enabled until the "enable" file
137 within the "hwlat_detector" debugfs directory is toggled.
139 This module is often used to detect SMI (System Management
140 Interrupts) on x86 systems, though is not x86 specific. To
141 this end, we default to using a sample window of 1 second,
142 during which we will sample for 0.5 seconds. If an SMI or
143 similar event occurs during that time, it is recorded
144 into an 8K samples global ring buffer until retreived.
146 WARNING: This software should never be enabled (it can be built
147 but should not be turned on after it is loaded) in a production
148 environment where high latencies are a concern since the
149 sampling mechanism actually introduces latencies for
150 regular tasks while the CPU(s) are being held.
155 tristate "Sensable PHANToM (PCI)"
158 Say Y here if you want to build a driver for Sensable PHANToM device.
160 This driver is only for PCI PHANToMs.
162 If you choose to build module, its name will be phantom. If unsure,
166 tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard"
167 depends on PCI && TTY && (X86_INTEL_MID || COMPILE_TEST)
170 The PTI (Parallel Trace Interface) driver directs
171 trace data routed from various parts in the system out
172 through an Intel Penwell PTI port and out of the mobile
173 device for analysis with a debugging tool (Lauterbach or Fido).
175 You should select this driver if the target kernel is meant for
176 an Intel Atom (non-netbook) mobile device containing a MIPI
177 P1149.7 standard implementation.
180 tristate "SGI IOC4 Base IO support"
183 This option enables basic support for the IOC4 chip on certain
184 SGI IO controller cards (IO9, IO10, and PCI-RT). This option
185 does not enable any specific functions on such a card, but provides
186 necessary infrastructure for other drivers to utilize.
188 If you have an SGI Altix with an IOC4-based card say Y.
192 tristate "TI Flash Media interface support"
195 If you want support for Texas Instruments(R) Flash Media adapters
196 you should select this option and then also choose an appropriate
197 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
198 support', if you have a TI PCI74xx compatible card reader, for
200 You will also have to select some flash card format drivers. MMC/SD
201 cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
202 Interface support (MMC_TIFM_SD)'.
204 To compile this driver as a module, choose M here: the module will
208 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support"
209 depends on PCI && TIFM_CORE
212 This option enables support for Texas Instruments(R) PCI74xx and
213 PCI76xx families of Flash Media adapters, found in many laptops.
214 To make actual use of the device, you will have to select some
215 flash card format drivers, as outlined in the TIFM_CORE Help.
217 To compile this driver as a module, choose M here: the module will
221 tristate "Integrated Circuits ICS932S401"
224 If you say yes here you get support for the Integrated Circuits
225 ICS932S401 clock control chips.
227 This driver can also be built as a module. If so, the module
228 will be called ics932s401.
231 tristate "Device driver for Atmel SSC peripheral"
232 depends on HAS_IOMEM && (AVR32 || ARCH_AT91 || COMPILE_TEST)
234 This option enables device driver support for Atmel Synchronized
235 Serial Communication peripheral (SSC).
237 The SSC peripheral supports a wide variety of serial frame based
238 communications, i.e. I2S, SPI, etc.
242 config ENCLOSURE_SERVICES
243 tristate "Enclosure Services"
246 Provides support for intelligent enclosures (bays which
247 contain storage devices). You also need either a host
248 driver (SCSI/ATA) which supports enclosures
249 or a SCSI enclosure device (SES) to use these services.
252 tristate "Support communication between SGI SSIs"
254 depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
255 select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
256 select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
257 select SGI_GRU if X86_64 && SMP
259 An SGI machine can be divided into multiple Single System
260 Images which act independently of each other and have
261 hardware based memory protection from the others. Enabling
262 this feature will allow for direct communication between SSIs
263 based on a network adapter and DMA messaging.
266 tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
267 depends on MFD_CS5535
270 This driver provides access to MFGPT functionality for other
271 drivers that need timers. MFGPTs are available in the CS5535 and
272 CS5536 companion chips that are found in AMD Geode and several
273 other platforms. They have a better resolution and max interval
274 than the generic PIT, and are suitable for use as high-res timers.
275 You probably don't want to enable this manually; other drivers that
276 make use of it should enable it.
278 config CS5535_MFGPT_DEFAULT_IRQ
280 depends on CS5535_MFGPT
283 MFGPTs on the CS5535 require an interrupt. The selected IRQ
284 can be overridden as a module option as well as by driver that
285 use the cs5535_mfgpt_ API; however, different architectures might
286 want to use a different IRQ by default. This is here for
287 architectures to set as necessary.
289 config CS5535_CLOCK_EVENT_SRC
290 tristate "CS5535/CS5536 high-res timer (MFGPT) events"
291 depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
293 This driver provides a clock event source based on the MFGPT
294 timer(s) in the CS5535 and CS5536 companion chips.
295 MFGPTs have a better resolution and max interval than the
296 generic PIT, and are suitable for use as high-res timers.
299 tristate "Channel interface driver for the HP iLO processor"
303 The channel interface driver allows applications to communicate
304 with iLO management processors present on HP ProLiant servers.
305 Upon loading, the driver creates /dev/hpilo/dXccbN files, which
306 can be used to gather data from the management processor, via
307 read and write system calls.
309 To compile this driver as a module, choose M here: the
310 module will be called hpilo.
313 tristate "SGI GRU driver"
314 depends on X86_UV && SMP
318 The GRU is a hardware resource located in the system chipset. The GRU
319 contains memory that can be mmapped into the user address space. This memory is
320 used to communicate with the GRU to perform functions such as load/store,
321 scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
322 instructions using user virtual addresses. GRU instructions (ex., bcopy) use
323 user virtual addresses for operands.
325 If you are not running on a SGI UV system, say N.
328 bool "SGI GRU driver debug"
332 This option enables additional debugging code for the SGI GRU driver.
333 If you are unsure, say N.
336 tristate "Medfield Avago APDS9802 ALS Sensor module"
339 If you say yes here you get support for the ALS APDS9802 ambient
342 This driver can also be built as a module. If so, the module
343 will be called apds9802als.
346 tristate "Intersil ISL29003 ambient light sensor"
347 depends on I2C && SYSFS
349 If you say yes here you get support for the Intersil ISL29003
350 ambient light sensor.
352 This driver can also be built as a module. If so, the module
353 will be called isl29003.
356 tristate "Intersil ISL29020 ambient light sensor"
359 If you say yes here you get support for the Intersil ISL29020
360 ambient light sensor.
362 This driver can also be built as a module. If so, the module
363 will be called isl29020.
365 config SENSORS_TSL2550
366 tristate "Taos TSL2550 ambient light sensor"
367 depends on I2C && SYSFS
369 If you say yes here you get support for the Taos TSL2550
370 ambient light sensor.
372 This driver can also be built as a module. If so, the module
373 will be called tsl2550.
375 config SENSORS_BH1780
376 tristate "ROHM BH1780GLI ambient light sensor"
377 depends on I2C && SYSFS
379 If you say yes here you get support for the ROHM BH1780GLI
380 ambient light sensor.
382 This driver can also be built as a module. If so, the module
383 will be called bh1780gli.
385 config SENSORS_BH1770
386 tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
389 Say Y here if you want to build a driver for BH1770GLC (ROHM) or
390 SFH7770 (Osram) combined ambient light and proximity sensor chip.
392 To compile this driver as a module, choose M here: the
393 module will be called bh1770glc. If unsure, say N here.
395 config SENSORS_APDS990X
396 tristate "APDS990X combined als and proximity sensors"
400 Say Y here if you want to build a driver for Avago APDS990x
401 combined ambient light and proximity sensor chip.
403 To compile this driver as a module, choose M here: the
404 module will be called apds990x. If unsure, say N here.
407 tristate "Honeywell HMC6352 compass"
410 This driver provides support for the Honeywell HMC6352 compass,
411 providing configuration and heading data via sysfs.
414 tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
417 If you say yes here you get support for Dallas Semiconductor
418 DS1682 Total Elapsed Time Recorder.
420 This driver can also be built as a module. If so, the module
421 will be called ds1682.
423 config SPEAR13XX_PCIE_GADGET
424 bool "PCIe gadget support for SPEAr13XX platform"
425 depends on ARCH_SPEAR13XX && BROKEN
428 This option enables gadget support for PCIe controller. If
429 board file defines any controller as PCIe endpoint then a sysfs
430 entry will be created for that controller. User can use these
431 sysfs node to configure PCIe EP as per his requirements.
434 tristate "Texas Instruments DAC7512"
435 depends on SPI && SYSFS
437 If you say yes here you get support for the Texas Instruments
438 DAC7512 16-bit digital-to-analog converter.
440 This driver can also be built as a module. If so, the module
441 will be called ti_dac7512.
443 config VMWARE_BALLOON
444 tristate "VMware Balloon Driver"
445 depends on X86 && HYPERVISOR_GUEST
447 This is VMware physical memory management driver which acts
448 like a "balloon" that can be inflated to reclaim physical pages
449 by reserving them in the guest and invalidating them in the
450 monitor, freeing up the underlying machine pages so they can
451 be allocated to other guests. The balloon can also be deflated
452 to allow the guest to use more physical memory.
456 To compile this driver as a module, choose M here: the
457 module will be called vmw_balloon.
460 bool "ARM Ltd. Character LCD Driver"
461 depends on PLAT_VERSATILE
463 This is a driver for the character LCD found on the ARM Ltd.
464 Versatile and RealView Platform Baseboards. It doesn't do
465 very much more than display the text "ARM Linux" on the first
466 line and the Linux version on the second line, but that's
474 tristate "BMP085 digital pressure sensor on I2C"
477 depends on I2C && SYSFS
479 Say Y here if you want to support Bosch Sensortec's digital pressure
480 sensor hooked to an I2C bus.
482 To compile this driver as a module, choose M here: the
483 module will be called bmp085-i2c.
486 tristate "BMP085 digital pressure sensor on SPI"
489 depends on SPI_MASTER && SYSFS
491 Say Y here if you want to support Bosch Sensortec's digital pressure
492 sensor hooked to an SPI bus.
494 To compile this driver as a module, choose M here: the
495 module will be called bmp085-spi.
498 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
499 select GENERIC_NET_UTILS
500 depends on PCI && (X86_32 || COMPILE_TEST)
502 This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
503 Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
504 processor. The Topcliff has MAC address and Option ROM data in SROM.
505 This driver can access MAC address and Option ROM data in SROM.
507 This driver also can be used for LAPIS Semiconductor's IOH,
508 ML7213/ML7223/ML7831.
509 ML7213 which is for IVI(In-Vehicle Infotainment) use.
510 ML7223 IOH is for MP(Media Phone) use.
511 ML7831 IOH is for general purpose use.
512 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
513 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
515 To compile this driver as a module, choose M here: the module will
518 config USB_SWITCH_FSA9480
519 tristate "FSA9480 USB Switch"
522 The FSA9480 is a USB port accessory detector and switch.
523 The FSA9480 is fully controlled using I2C and enables USB data,
524 stereo and mono audio, video, microphone and UART data to use
525 a common connector port.
527 config LATTICE_ECP3_CONFIG
528 tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
529 depends on SPI && SYSFS
533 This option enables support for bitstream configuration (programming
534 or loading) of the Lattice ECP3 FPGA family via SPI.
539 bool "Generic on-chip SRAM driver"
541 select GENERIC_ALLOCATOR
543 This driver allows you to declare a memory region to be managed by
544 the genalloc API. It is supposed to be used for small on-chip SRAM
545 areas found on many SoCs.
547 config VEXPRESS_SYSCFG
548 bool "Versatile Express System Configuration driver"
549 depends on VEXPRESS_CONFIG
552 ARM Ltd. Versatile Express uses specialised platform configuration
553 bus. System Configuration interface is one of the possible means
554 of generating transactions on this bus.
556 source "drivers/misc/c2port/Kconfig"
557 source "drivers/misc/eeprom/Kconfig"
558 source "drivers/misc/cb710/Kconfig"
559 source "drivers/misc/ti-st/Kconfig"
560 source "drivers/misc/lis3lv02d/Kconfig"
561 source "drivers/misc/carma/Kconfig"
562 source "drivers/misc/altera-stapl/Kconfig"
563 source "drivers/misc/mei/Kconfig"
564 source "drivers/misc/vmw_vmci/Kconfig"
565 source "drivers/misc/mic/Kconfig"
566 source "drivers/misc/genwqe/Kconfig"
567 source "drivers/misc/echo/Kconfig"
568 source "drivers/misc/cxl/Kconfig"