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"
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.
63 tristate "Dummy IRQ handler"
66 This module accepts a single 'irq' parameter, which it should register for.
67 The sole purpose of this module is to help with debugging of systems on
68 which spurious IRQs would happen on disabled IRQ vector.
71 tristate "Device driver for IBM RSA service processor"
72 depends on X86 && PCI && INPUT
73 depends on SERIAL_8250 || SERIAL_8250=n
75 This option enables device driver support for in-band access to the
76 IBM RSA (Condor) service processor in eServer xSeries systems.
77 The ibmasm device driver allows user space application to access
78 ASM (Advanced Systems Management) functions on the service
79 processor. The driver is meant to be used in conjunction with
81 The ibmasm driver also enables the OS to use the UART on the
82 service processor board as a regular serial port. To make use of
83 this feature serial driver support (CONFIG_SERIAL_8250) must be
86 WARNING: This software may not be supported or function
87 correctly on your IBM server. Please consult the IBM ServerProven
88 website <http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>
89 for information on the specific driver level and support statement
93 tristate "IBM Virtual Management Channel support"
94 depends on PPC_PSERIES
96 This is the IBM POWER Virtual Management Channel
98 This driver is to be used for the POWER Virtual
99 Management Channel virtual adapter on the PowerVM
100 platform. It provides both request/response and
101 async message support through the /dev/ibmvmc node.
103 To compile this driver as a module, choose M here: the
104 module will be called ibmvmc.
107 tristate "Sensable PHANToM (PCI)"
110 Say Y here if you want to build a driver for Sensable PHANToM device.
112 This driver is only for PCI PHANToMs.
114 If you choose to build module, its name will be phantom. If unsure,
118 tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard"
119 depends on PCI && TTY && (X86_INTEL_MID || COMPILE_TEST)
122 The PTI (Parallel Trace Interface) driver directs
123 trace data routed from various parts in the system out
124 through an Intel Penwell PTI port and out of the mobile
125 device for analysis with a debugging tool (Lauterbach or Fido).
127 You should select this driver if the target kernel is meant for
128 an Intel Atom (non-netbook) mobile device containing a MIPI
129 P1149.7 standard implementation.
132 tristate "SGI IOC4 Base IO support"
135 This option enables basic support for the IOC4 chip on certain
136 SGI IO controller cards (IO9, IO10, and PCI-RT). This option
137 does not enable any specific functions on such a card, but provides
138 necessary infrastructure for other drivers to utilize.
140 If you have an SGI Altix with an IOC4-based card say Y.
144 tristate "TI Flash Media interface support"
147 If you want support for Texas Instruments(R) Flash Media adapters
148 you should select this option and then also choose an appropriate
149 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
150 support', if you have a TI PCI74xx compatible card reader, for
152 You will also have to select some flash card format drivers. MMC/SD
153 cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
154 Interface support (MMC_TIFM_SD)'.
156 To compile this driver as a module, choose M here: the module will
160 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support"
161 depends on PCI && TIFM_CORE
164 This option enables support for Texas Instruments(R) PCI74xx and
165 PCI76xx families of Flash Media adapters, found in many laptops.
166 To make actual use of the device, you will have to select some
167 flash card format drivers, as outlined in the TIFM_CORE Help.
169 To compile this driver as a module, choose M here: the module will
173 tristate "Integrated Circuits ICS932S401"
176 If you say yes here you get support for the Integrated Circuits
177 ICS932S401 clock control chips.
179 This driver can also be built as a module. If so, the module
180 will be called ics932s401.
183 tristate "Device driver for Atmel SSC peripheral"
184 depends on HAS_IOMEM && (ARCH_AT91 || COMPILE_TEST)
186 This option enables device driver support for Atmel Synchronized
187 Serial Communication peripheral (SSC).
189 The SSC peripheral supports a wide variety of serial frame based
190 communications, i.e. I2S, SPI, etc.
194 config ENCLOSURE_SERVICES
195 tristate "Enclosure Services"
198 Provides support for intelligent enclosures (bays which
199 contain storage devices). You also need either a host
200 driver (SCSI/ATA) which supports enclosures
201 or a SCSI enclosure device (SES) to use these services.
204 tristate "Support communication between SGI SSIs"
206 depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
207 select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
208 select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
209 select SGI_GRU if X86_64 && SMP
211 An SGI machine can be divided into multiple Single System
212 Images which act independently of each other and have
213 hardware based memory protection from the others. Enabling
214 this feature will allow for direct communication between SSIs
215 based on a network adapter and DMA messaging.
218 tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
219 depends on MFD_CS5535
222 This driver provides access to MFGPT functionality for other
223 drivers that need timers. MFGPTs are available in the CS5535 and
224 CS5536 companion chips that are found in AMD Geode and several
225 other platforms. They have a better resolution and max interval
226 than the generic PIT, and are suitable for use as high-res timers.
227 You probably don't want to enable this manually; other drivers that
228 make use of it should enable it.
230 config CS5535_MFGPT_DEFAULT_IRQ
232 depends on CS5535_MFGPT
235 MFGPTs on the CS5535 require an interrupt. The selected IRQ
236 can be overridden as a module option as well as by driver that
237 use the cs5535_mfgpt_ API; however, different architectures might
238 want to use a different IRQ by default. This is here for
239 architectures to set as necessary.
241 config CS5535_CLOCK_EVENT_SRC
242 tristate "CS5535/CS5536 high-res timer (MFGPT) events"
243 depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
245 This driver provides a clock event source based on the MFGPT
246 timer(s) in the CS5535 and CS5536 companion chips.
247 MFGPTs have a better resolution and max interval than the
248 generic PIT, and are suitable for use as high-res timers.
251 tristate "Channel interface driver for the HP iLO processor"
255 The channel interface driver allows applications to communicate
256 with iLO management processors present on HP ProLiant servers.
257 Upon loading, the driver creates /dev/hpilo/dXccbN files, which
258 can be used to gather data from the management processor, via
259 read and write system calls.
261 To compile this driver as a module, choose M here: the
262 module will be called hpilo.
265 tristate "Qualcomm coincell charger support"
266 depends on MFD_SPMI_PMIC || COMPILE_TEST
268 This driver supports the coincell block found inside of
269 Qualcomm PMICs. The coincell charger provides a means to
270 charge a coincell battery or backup capacitor which is used
271 to maintain PMIC register and RTC state in the absence of
275 tristate "Qualcomm FastRPC"
276 depends on ARCH_QCOM || COMPILE_TEST
278 select DMA_SHARED_BUFFER
280 Provides a communication mechanism that allows for clients to
281 make remote method invocations across processor boundary to
282 applications DSP processor. Say M if you want to enable this
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_BH1770
349 tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
352 Say Y here if you want to build a driver for BH1770GLC (ROHM) or
353 SFH7770 (Osram) combined ambient light and proximity sensor chip.
355 To compile this driver as a module, choose M here: the
356 module will be called bh1770glc. If unsure, say N here.
358 config SENSORS_APDS990X
359 tristate "APDS990X combined als and proximity sensors"
363 Say Y here if you want to build a driver for Avago APDS990x
364 combined ambient light and proximity sensor chip.
366 To compile this driver as a module, choose M here: the
367 module will be called apds990x. If unsure, say N here.
370 tristate "Honeywell HMC6352 compass"
373 This driver provides support for the Honeywell HMC6352 compass,
374 providing configuration and heading data via sysfs.
377 tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
380 If you say yes here you get support for Dallas Semiconductor
381 DS1682 Total Elapsed Time Recorder.
383 This driver can also be built as a module. If so, the module
384 will be called ds1682.
386 config SPEAR13XX_PCIE_GADGET
387 bool "PCIe gadget support for SPEAr13XX platform"
388 depends on ARCH_SPEAR13XX && BROKEN
391 This option enables gadget support for PCIe controller. If
392 board file defines any controller as PCIe endpoint then a sysfs
393 entry will be created for that controller. User can use these
394 sysfs node to configure PCIe EP as per his requirements.
396 config VMWARE_BALLOON
397 tristate "VMware Balloon Driver"
398 depends on VMWARE_VMCI && X86 && HYPERVISOR_GUEST
400 This is VMware physical memory management driver which acts
401 like a "balloon" that can be inflated to reclaim physical pages
402 by reserving them in the guest and invalidating them in the
403 monitor, freeing up the underlying machine pages so they can
404 be allocated to other guests. The balloon can also be deflated
405 to allow the guest to use more physical memory.
409 To compile this driver as a module, choose M here: the
410 module will be called vmw_balloon.
413 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
414 select GENERIC_NET_UTILS
415 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
417 This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
418 Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
419 processor. The Topcliff has MAC address and Option ROM data in SROM.
420 This driver can access MAC address and Option ROM data in SROM.
422 This driver also can be used for LAPIS Semiconductor's IOH,
423 ML7213/ML7223/ML7831.
424 ML7213 which is for IVI(In-Vehicle Infotainment) use.
425 ML7223 IOH is for MP(Media Phone) use.
426 ML7831 IOH is for general purpose use.
427 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
428 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
430 To compile this driver as a module, choose M here: the module will
433 config USB_SWITCH_FSA9480
434 tristate "FSA9480 USB Switch"
437 The FSA9480 is a USB port accessory detector and switch.
438 The FSA9480 is fully controlled using I2C and enables USB data,
439 stereo and mono audio, video, microphone and UART data to use
440 a common connector port.
442 config LATTICE_ECP3_CONFIG
443 tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
444 depends on SPI && SYSFS
448 This option enables support for bitstream configuration (programming
449 or loading) of the Lattice ECP3 FPGA family via SPI.
454 bool "Generic on-chip SRAM driver"
456 select GENERIC_ALLOCATOR
457 select SRAM_EXEC if ARM
459 This driver allows you to declare a memory region to be managed by
460 the genalloc API. It is supposed to be used for small on-chip SRAM
461 areas found on many SoCs.
466 config VEXPRESS_SYSCFG
467 bool "Versatile Express System Configuration driver"
468 depends on VEXPRESS_CONFIG
471 ARM Ltd. Versatile Express uses specialised platform configuration
472 bus. System Configuration interface is one of the possible means
473 of generating transactions on this bus.
475 config PCI_ENDPOINT_TEST
478 tristate "PCI Endpoint Test driver"
480 Enable this configuration option to enable the host side test driver
485 default MISC_RTSX_PCI || MISC_RTSX_USB
488 tristate "pvpanic device support"
489 depends on HAS_IOMEM && (ACPI || OF)
491 This driver provides support for the pvpanic device. pvpanic is
492 a paravirtualized device provided by QEMU; it lets a virtual machine
493 (guest) communicate panic events to the host.
495 source "drivers/misc/c2port/Kconfig"
496 source "drivers/misc/eeprom/Kconfig"
497 source "drivers/misc/cb710/Kconfig"
498 source "drivers/misc/ti-st/Kconfig"
499 source "drivers/misc/lis3lv02d/Kconfig"
500 source "drivers/misc/altera-stapl/Kconfig"
501 source "drivers/misc/mei/Kconfig"
502 source "drivers/misc/vmw_vmci/Kconfig"
503 source "drivers/misc/mic/Kconfig"
504 source "drivers/misc/genwqe/Kconfig"
505 source "drivers/misc/echo/Kconfig"
506 source "drivers/misc/cxl/Kconfig"
507 source "drivers/misc/ocxl/Kconfig"
508 source "drivers/misc/cardreader/Kconfig"
509 source "drivers/misc/habanalabs/Kconfig"