1 # SPDX-License-Identifier: GPL-2.0-only
8 config SENSORS_LIS3LV02D
14 tristate "Broadcom 283x Secondary Memory Interface driver"
15 depends on ARCH_BCM2835
18 Driver for enabling and using Broadcom's Secondary/Slow Memory Interface.
19 Appears as /dev/bcm2835_smi. For ioctl interface see drivers/misc/bcm2835_smi.h
22 tristate "Analog Devices Digital Potentiometers"
23 depends on (I2C || SPI) && SYSFS
25 If you say yes here, you get support for the Analog Devices
26 AD5258, AD5259, AD5251, AD5252, AD5253, AD5254, AD5255
27 AD5160, AD5161, AD5162, AD5165, AD5200, AD5201, AD5203,
28 AD5204, AD5206, AD5207, AD5231, AD5232, AD5233, AD5235,
29 AD5260, AD5262, AD5263, AD5290, AD5291, AD5292, AD5293,
30 AD7376, AD8400, AD8402, AD8403, ADN2850, AD5241, AD5242,
31 AD5243, AD5245, AD5246, AD5247, AD5248, AD5280, AD5282,
32 ADN2860, AD5273, AD5171, AD5170, AD5172, AD5173, AD5270,
33 AD5271, AD5272, AD5274
34 digital potentiometer chips.
36 See Documentation/misc-devices/ad525x_dpot.txt for the
39 This driver can also be built as a module. If so, the module
40 will be called ad525x_dpot.
42 config AD525X_DPOT_I2C
43 tristate "support I2C bus connection"
44 depends on AD525X_DPOT && I2C
46 Say Y here if you have a digital potentiometers hooked to an I2C bus.
48 To compile this driver as a module, choose M here: the
49 module will be called ad525x_dpot-i2c.
51 config AD525X_DPOT_SPI
52 tristate "support SPI bus connection"
53 depends on AD525X_DPOT && SPI_MASTER
55 Say Y here if you have a digital potentiometers hooked to an SPI bus.
57 If unsure, say N (but it's safe to say "Y").
59 To compile this driver as a module, choose M here: the
60 module will be called ad525x_dpot-spi.
63 bool "Atmel AT32/AT91 Timer/Counter Library"
66 Select this if you want a library to allocate the Timer/Counter
67 blocks found on many Atmel processors. This facilitates using
68 these blocks by different drivers despite processor differences.
71 tristate "Dummy IRQ handler"
73 This module accepts a single 'irq' parameter, which it should register for.
74 The sole purpose of this module is to help with debugging of systems on
75 which spurious IRQs would happen on disabled IRQ vector.
78 tristate "Device driver for IBM RSA service processor"
79 depends on X86 && PCI && INPUT
80 depends on SERIAL_8250 || SERIAL_8250=n
82 This option enables device driver support for in-band access to the
83 IBM RSA (Condor) service processor in eServer xSeries systems.
84 The ibmasm device driver allows user space application to access
85 ASM (Advanced Systems Management) functions on the service
86 processor. The driver is meant to be used in conjunction with
88 The ibmasm driver also enables the OS to use the UART on the
89 service processor board as a regular serial port. To make use of
90 this feature serial driver support (CONFIG_SERIAL_8250) must be
93 WARNING: This software may not be supported or function
94 correctly on your IBM server. Please consult the IBM ServerProven
95 website <http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>
96 for information on the specific driver level and support statement
100 tristate "IBM Virtual Management Channel support"
101 depends on PPC_PSERIES
103 This is the IBM POWER Virtual Management Channel
105 This driver is to be used for the POWER Virtual
106 Management Channel virtual adapter on the PowerVM
107 platform. It provides both request/response and
108 async message support through the /dev/ibmvmc node.
110 To compile this driver as a module, choose M here: the
111 module will be called ibmvmc.
114 tristate "Sensable PHANToM (PCI)"
117 Say Y here if you want to build a driver for Sensable PHANToM device.
119 This driver is only for PCI PHANToMs.
121 If you choose to build module, its name will be phantom. If unsure,
125 tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard"
126 depends on PCI && TTY && (X86_INTEL_MID || COMPILE_TEST)
128 The PTI (Parallel Trace Interface) driver directs
129 trace data routed from various parts in the system out
130 through an Intel Penwell PTI port and out of the mobile
131 device for analysis with a debugging tool (Lauterbach or Fido).
133 You should select this driver if the target kernel is meant for
134 an Intel Atom (non-netbook) mobile device containing a MIPI
135 P1149.7 standard implementation.
138 tristate "TI Flash Media interface support"
141 If you want support for Texas Instruments(R) Flash Media adapters
142 you should select this option and then also choose an appropriate
143 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
144 support', if you have a TI PCI74xx compatible card reader, for
146 You will also have to select some flash card format drivers. MMC/SD
147 cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
148 Interface support (MMC_TIFM_SD)'.
150 To compile this driver as a module, choose M here: the module will
154 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support"
155 depends on PCI && TIFM_CORE
158 This option enables support for Texas Instruments(R) PCI74xx and
159 PCI76xx families of Flash Media adapters, found in many laptops.
160 To make actual use of the device, you will have to select some
161 flash card format drivers, as outlined in the TIFM_CORE Help.
163 To compile this driver as a module, choose M here: the module will
167 tristate "Integrated Circuits ICS932S401"
170 If you say yes here you get support for the Integrated Circuits
171 ICS932S401 clock control chips.
173 This driver can also be built as a module. If so, the module
174 will be called ics932s401.
177 tristate "Device driver for Atmel SSC peripheral"
178 depends on HAS_IOMEM && (ARCH_AT91 || COMPILE_TEST)
180 This option enables device driver support for Atmel Synchronized
181 Serial Communication peripheral (SSC).
183 The SSC peripheral supports a wide variety of serial frame based
184 communications, i.e. I2S, SPI, etc.
188 config ENCLOSURE_SERVICES
189 tristate "Enclosure Services"
191 Provides support for intelligent enclosures (bays which
192 contain storage devices). You also need either a host
193 driver (SCSI/ATA) which supports enclosures
194 or a SCSI enclosure device (SES) to use these services.
197 tristate "Support communication between SGI SSIs"
199 depends on (IA64_SGI_UV || X86_UV) && SMP
200 depends on X86_64 || BROKEN
201 select SGI_GRU if X86_64 && SMP
203 An SGI machine can be divided into multiple Single System
204 Images which act independently of each other and have
205 hardware based memory protection from the others. Enabling
206 this feature will allow for direct communication between SSIs
207 based on a network adapter and DMA messaging.
210 tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
211 depends on MFD_CS5535
213 This driver provides access to MFGPT functionality for other
214 drivers that need timers. MFGPTs are available in the CS5535 and
215 CS5536 companion chips that are found in AMD Geode and several
216 other platforms. They have a better resolution and max interval
217 than the generic PIT, and are suitable for use as high-res timers.
218 You probably don't want to enable this manually; other drivers that
219 make use of it should enable it.
221 config CS5535_MFGPT_DEFAULT_IRQ
223 depends on CS5535_MFGPT
226 MFGPTs on the CS5535 require an interrupt. The selected IRQ
227 can be overridden as a module option as well as by driver that
228 use the cs5535_mfgpt_ API; however, different architectures might
229 want to use a different IRQ by default. This is here for
230 architectures to set as necessary.
232 config CS5535_CLOCK_EVENT_SRC
233 tristate "CS5535/CS5536 high-res timer (MFGPT) events"
234 depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
236 This driver provides a clock event source based on the MFGPT
237 timer(s) in the CS5535 and CS5536 companion chips.
238 MFGPTs have a better resolution and max interval than the
239 generic PIT, and are suitable for use as high-res timers.
242 tristate "Channel interface driver for the HP iLO processor"
245 The channel interface driver allows applications to communicate
246 with iLO management processors present on HP ProLiant servers.
247 Upon loading, the driver creates /dev/hpilo/dXccbN files, which
248 can be used to gather data from the management processor, via
249 read and write system calls.
251 To compile this driver as a module, choose M here: the
252 module will be called hpilo.
255 tristate "Qualcomm coincell charger support"
256 depends on MFD_SPMI_PMIC || COMPILE_TEST
258 This driver supports the coincell block found inside of
259 Qualcomm PMICs. The coincell charger provides a means to
260 charge a coincell battery or backup capacitor which is used
261 to maintain PMIC register and RTC state in the absence of
265 tristate "Qualcomm FastRPC"
266 depends on ARCH_QCOM || COMPILE_TEST
268 select DMA_SHARED_BUFFER
270 Provides a communication mechanism that allows for clients to
271 make remote method invocations across processor boundary to
272 applications DSP processor. Say M if you want to enable this
276 tristate "SGI GRU driver"
277 depends on X86_UV && SMP
280 The GRU is a hardware resource located in the system chipset. The GRU
281 contains memory that can be mmapped into the user address space. This memory is
282 used to communicate with the GRU to perform functions such as load/store,
283 scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
284 instructions using user virtual addresses. GRU instructions (ex., bcopy) use
285 user virtual addresses for operands.
287 If you are not running on a SGI UV system, say N.
290 bool "SGI GRU driver debug"
293 This option enables additional debugging code for the SGI GRU driver.
294 If you are unsure, say N.
297 tristate "Medfield Avago APDS9802 ALS Sensor module"
300 If you say yes here you get support for the ALS APDS9802 ambient
303 This driver can also be built as a module. If so, the module
304 will be called apds9802als.
307 tristate "Intersil ISL29003 ambient light sensor"
308 depends on I2C && SYSFS
310 If you say yes here you get support for the Intersil ISL29003
311 ambient light sensor.
313 This driver can also be built as a module. If so, the module
314 will be called isl29003.
317 tristate "Intersil ISL29020 ambient light sensor"
320 If you say yes here you get support for the Intersil ISL29020
321 ambient light sensor.
323 This driver can also be built as a module. If so, the module
324 will be called isl29020.
326 config SENSORS_TSL2550
327 tristate "Taos TSL2550 ambient light sensor"
328 depends on I2C && SYSFS
330 If you say yes here you get support for the Taos TSL2550
331 ambient light sensor.
333 This driver can also be built as a module. If so, the module
334 will be called tsl2550.
336 config SENSORS_BH1770
337 tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
340 Say Y here if you want to build a driver for BH1770GLC (ROHM) or
341 SFH7770 (Osram) combined ambient light and proximity sensor chip.
343 To compile this driver as a module, choose M here: the
344 module will be called bh1770glc. If unsure, say N here.
346 config SENSORS_APDS990X
347 tristate "APDS990X combined als and proximity sensors"
350 Say Y here if you want to build a driver for Avago APDS990x
351 combined ambient light and proximity sensor chip.
353 To compile this driver as a module, choose M here: the
354 module will be called apds990x. If unsure, say N here.
357 tristate "Honeywell HMC6352 compass"
360 This driver provides support for the Honeywell HMC6352 compass,
361 providing configuration and heading data via sysfs.
364 tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
367 If you say yes here you get support for Dallas Semiconductor
368 DS1682 Total Elapsed Time Recorder.
370 This driver can also be built as a module. If so, the module
371 will be called ds1682.
373 config VMWARE_BALLOON
374 tristate "VMware Balloon Driver"
375 depends on VMWARE_VMCI && X86 && HYPERVISOR_GUEST
376 select MEMORY_BALLOON
378 This is VMware physical memory management driver which acts
379 like a "balloon" that can be inflated to reclaim physical pages
380 by reserving them in the guest and invalidating them in the
381 monitor, freeing up the underlying machine pages so they can
382 be allocated to other guests. The balloon can also be deflated
383 to allow the guest to use more physical memory.
387 To compile this driver as a module, choose M here: the
388 module will be called vmw_balloon.
391 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
392 select GENERIC_NET_UTILS
393 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
395 This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
396 Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
397 processor. The Topcliff has MAC address and Option ROM data in SROM.
398 This driver can access MAC address and Option ROM data in SROM.
400 This driver also can be used for LAPIS Semiconductor's IOH,
401 ML7213/ML7223/ML7831.
402 ML7213 which is for IVI(In-Vehicle Infotainment) use.
403 ML7223 IOH is for MP(Media Phone) use.
404 ML7831 IOH is for general purpose use.
405 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
406 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
408 To compile this driver as a module, choose M here: the module will
411 config LATTICE_ECP3_CONFIG
412 tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
413 depends on SPI && SYSFS
417 This option enables support for bitstream configuration (programming
418 or loading) of the Lattice ECP3 FPGA family via SPI.
423 bool "Generic on-chip SRAM driver"
425 select GENERIC_ALLOCATOR
426 select SRAM_EXEC if ARM
428 This driver allows you to declare a memory region to be managed by
429 the genalloc API. It is supposed to be used for small on-chip SRAM
430 areas found on many SoCs.
435 config VEXPRESS_SYSCFG
436 bool "Versatile Express System Configuration driver"
437 depends on VEXPRESS_CONFIG
440 ARM Ltd. Versatile Express uses specialised platform configuration
441 bus. System Configuration interface is one of the possible means
442 of generating transactions on this bus.
444 config PCI_ENDPOINT_TEST
447 tristate "PCI Endpoint Test driver"
449 Enable this configuration option to enable the host side test driver
453 tristate "Xilinx SDFEC 16"
456 This option enables support for the Xilinx SDFEC (Soft Decision
457 Forward Error Correction) driver. This enables a char driver
460 You may select this driver if your design instantiates the
461 SDFEC(16nm) hardened block. To compile this as a module choose M.
467 default MISC_RTSX_PCI || MISC_RTSX_USB
470 tristate "pvpanic device support"
471 depends on HAS_IOMEM && (ACPI || OF)
473 This driver provides support for the pvpanic device. pvpanic is
474 a paravirtualized device provided by QEMU; it lets a virtual machine
475 (guest) communicate panic events to the host.
477 source "drivers/misc/c2port/Kconfig"
478 source "drivers/misc/eeprom/Kconfig"
479 source "drivers/misc/cb710/Kconfig"
480 source "drivers/misc/ti-st/Kconfig"
481 source "drivers/misc/lis3lv02d/Kconfig"
482 source "drivers/misc/altera-stapl/Kconfig"
483 source "drivers/misc/mei/Kconfig"
484 source "drivers/misc/vmw_vmci/Kconfig"
485 source "drivers/misc/mic/Kconfig"
486 source "drivers/misc/genwqe/Kconfig"
487 source "drivers/misc/echo/Kconfig"
488 source "drivers/misc/cxl/Kconfig"
489 source "drivers/misc/ocxl/Kconfig"
490 source "drivers/misc/cardreader/Kconfig"
491 source "drivers/misc/habanalabs/Kconfig"