1 # SPDX-License-Identifier: GPL-2.0-only
8 config SENSORS_LIS3LV02D
13 tristate "Analog Devices Digital Potentiometers"
14 depends on (I2C || SPI) && SYSFS
16 If you say yes here, you get support for the Analog Devices
17 AD5258, AD5259, AD5251, AD5252, AD5253, AD5254, AD5255
18 AD5160, AD5161, AD5162, AD5165, AD5200, AD5201, AD5203,
19 AD5204, AD5206, AD5207, AD5231, AD5232, AD5233, AD5235,
20 AD5260, AD5262, AD5263, AD5290, AD5291, AD5292, AD5293,
21 AD7376, AD8400, AD8402, AD8403, ADN2850, AD5241, AD5242,
22 AD5243, AD5245, AD5246, AD5247, AD5248, AD5280, AD5282,
23 ADN2860, AD5273, AD5171, AD5170, AD5172, AD5173, AD5270,
24 AD5271, AD5272, AD5274
25 digital potentiometer chips.
27 See Documentation/misc-devices/ad525x_dpot.rst for the
30 This driver can also be built as a module. If so, the module
31 will be called ad525x_dpot.
33 config AD525X_DPOT_I2C
34 tristate "support I2C bus connection"
35 depends on AD525X_DPOT && I2C
37 Say Y here if you have a digital potentiometers hooked to an I2C bus.
39 To compile this driver as a module, choose M here: the
40 module will be called ad525x_dpot-i2c.
42 config AD525X_DPOT_SPI
43 tristate "support SPI bus connection"
44 depends on AD525X_DPOT && SPI_MASTER
46 Say Y here if you have a digital potentiometers hooked to an SPI bus.
48 If unsure, say N (but it's safe to say "Y").
50 To compile this driver as a module, choose M here: the
51 module will be called ad525x_dpot-spi.
54 bool "Atmel AT32/AT91 Timer/Counter Library"
57 Select this if you want a library to allocate the Timer/Counter
58 blocks found on many Atmel processors. This facilitates using
59 these blocks by different drivers despite processor differences.
62 tristate "Dummy IRQ handler"
64 This module accepts a single 'irq' parameter, which it should register for.
65 The sole purpose of this module is to help with debugging of systems on
66 which spurious IRQs would happen on disabled IRQ vector.
69 tristate "Device driver for IBM RSA service processor"
70 depends on X86 && PCI && INPUT
71 depends on SERIAL_8250 || SERIAL_8250=n
73 This option enables device driver support for in-band access to the
74 IBM RSA (Condor) service processor in eServer xSeries systems.
75 The ibmasm device driver allows user space application to access
76 ASM (Advanced Systems Management) functions on the service
77 processor. The driver is meant to be used in conjunction with
79 The ibmasm driver also enables the OS to use the UART on the
80 service processor board as a regular serial port. To make use of
81 this feature serial driver support (CONFIG_SERIAL_8250) must be
84 WARNING: This software may not be supported or function
85 correctly on your IBM server. Please consult the IBM ServerProven
86 website <https://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>
87 for information on the specific driver level and support statement
91 tristate "IBM Virtual Management Channel support"
92 depends on PPC_PSERIES
94 This is the IBM POWER Virtual Management Channel
96 This driver is to be used for the POWER Virtual
97 Management Channel virtual adapter on the PowerVM
98 platform. It provides both request/response and
99 async message support through the /dev/ibmvmc node.
101 To compile this driver as a module, choose M here: the
102 module will be called ibmvmc.
105 tristate "Sensable PHANToM (PCI)"
108 Say Y here if you want to build a driver for Sensable PHANToM device.
110 This driver is only for PCI PHANToMs.
112 If you choose to build module, its name will be phantom. If unsure,
116 tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard"
117 depends on PCI && TTY && (X86_INTEL_MID || COMPILE_TEST)
119 The PTI (Parallel Trace Interface) driver directs
120 trace data routed from various parts in the system out
121 through an Intel Penwell PTI port and out of the mobile
122 device for analysis with a debugging tool (Lauterbach or Fido).
124 You should select this driver if the target kernel is meant for
125 an Intel Atom (non-netbook) mobile device containing a MIPI
126 P1149.7 standard implementation.
129 tristate "TI Flash Media interface support"
132 If you want support for Texas Instruments(R) Flash Media adapters
133 you should select this option and then also choose an appropriate
134 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
135 support', if you have a TI PCI74xx compatible card reader, for
137 You will also have to select some flash card format drivers. MMC/SD
138 cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
139 Interface support (MMC_TIFM_SD)'.
141 To compile this driver as a module, choose M here: the module will
145 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support"
146 depends on PCI && TIFM_CORE
149 This option enables support for Texas Instruments(R) PCI74xx and
150 PCI76xx families of Flash Media adapters, found in many laptops.
151 To make actual use of the device, you will have to select some
152 flash card format drivers, as outlined in the TIFM_CORE Help.
154 To compile this driver as a module, choose M here: the module will
158 tristate "Integrated Circuits ICS932S401"
161 If you say yes here you get support for the Integrated Circuits
162 ICS932S401 clock control chips.
164 This driver can also be built as a module. If so, the module
165 will be called ics932s401.
168 tristate "Device driver for Atmel SSC peripheral"
169 depends on HAS_IOMEM && (ARCH_AT91 || COMPILE_TEST)
171 This option enables device driver support for Atmel Synchronized
172 Serial Communication peripheral (SSC).
174 The SSC peripheral supports a wide variety of serial frame based
175 communications, i.e. I2S, SPI, etc.
179 config ENCLOSURE_SERVICES
180 tristate "Enclosure Services"
182 Provides support for intelligent enclosures (bays which
183 contain storage devices). You also need either a host
184 driver (SCSI/ATA) which supports enclosures
185 or a SCSI enclosure device (SES) to use these services.
188 tristate "Support communication between SGI SSIs"
190 depends on (IA64_SGI_UV || X86_UV) && SMP
191 depends on X86_64 || BROKEN
192 select SGI_GRU if X86_64 && SMP
194 An SGI machine can be divided into multiple Single System
195 Images which act independently of each other and have
196 hardware based memory protection from the others. Enabling
197 this feature will allow for direct communication between SSIs
198 based on a network adapter and DMA messaging.
201 tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
202 depends on MFD_CS5535
204 This driver provides access to MFGPT functionality for other
205 drivers that need timers. MFGPTs are available in the CS5535 and
206 CS5536 companion chips that are found in AMD Geode and several
207 other platforms. They have a better resolution and max interval
208 than the generic PIT, and are suitable for use as high-res timers.
209 You probably don't want to enable this manually; other drivers that
210 make use of it should enable it.
212 config CS5535_MFGPT_DEFAULT_IRQ
214 depends on CS5535_MFGPT
217 MFGPTs on the CS5535 require an interrupt. The selected IRQ
218 can be overridden as a module option as well as by driver that
219 use the cs5535_mfgpt_ API; however, different architectures might
220 want to use a different IRQ by default. This is here for
221 architectures to set as necessary.
223 config CS5535_CLOCK_EVENT_SRC
224 tristate "CS5535/CS5536 high-res timer (MFGPT) events"
225 depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
227 This driver provides a clock event source based on the MFGPT
228 timer(s) in the CS5535 and CS5536 companion chips.
229 MFGPTs have a better resolution and max interval than the
230 generic PIT, and are suitable for use as high-res timers.
233 tristate "Channel interface driver for the HP iLO processor"
236 The channel interface driver allows applications to communicate
237 with iLO management processors present on HP ProLiant servers.
238 Upon loading, the driver creates /dev/hpilo/dXccbN files, which
239 can be used to gather data from the management processor, via
240 read and write system calls.
242 To compile this driver as a module, choose M here: the
243 module will be called hpilo.
246 tristate "Qualcomm coincell charger support"
247 depends on MFD_SPMI_PMIC || COMPILE_TEST
249 This driver supports the coincell block found inside of
250 Qualcomm PMICs. The coincell charger provides a means to
251 charge a coincell battery or backup capacitor which is used
252 to maintain PMIC register and RTC state in the absence of
256 tristate "Qualcomm FastRPC"
257 depends on ARCH_QCOM || COMPILE_TEST
259 select DMA_SHARED_BUFFER
261 Provides a communication mechanism that allows for clients to
262 make remote method invocations across processor boundary to
263 applications DSP processor. Say M if you want to enable this
267 tristate "SGI GRU driver"
268 depends on X86_UV && SMP
271 The GRU is a hardware resource located in the system chipset. The GRU
272 contains memory that can be mmapped into the user address space. This memory is
273 used to communicate with the GRU to perform functions such as load/store,
274 scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
275 instructions using user virtual addresses. GRU instructions (ex., bcopy) use
276 user virtual addresses for operands.
278 If you are not running on a SGI UV system, say N.
281 bool "SGI GRU driver debug"
284 This option enables additional debugging code for the SGI GRU driver.
285 If you are unsure, say N.
288 tristate "Medfield Avago APDS9802 ALS Sensor module"
291 If you say yes here you get support for the ALS APDS9802 ambient
294 This driver can also be built as a module. If so, the module
295 will be called apds9802als.
298 tristate "Intersil ISL29003 ambient light sensor"
299 depends on I2C && SYSFS
301 If you say yes here you get support for the Intersil ISL29003
302 ambient light sensor.
304 This driver can also be built as a module. If so, the module
305 will be called isl29003.
308 tristate "Intersil ISL29020 ambient light sensor"
311 If you say yes here you get support for the Intersil ISL29020
312 ambient light sensor.
314 This driver can also be built as a module. If so, the module
315 will be called isl29020.
317 config SENSORS_TSL2550
318 tristate "Taos TSL2550 ambient light sensor"
319 depends on I2C && SYSFS
321 If you say yes here you get support for the Taos TSL2550
322 ambient light sensor.
324 This driver can also be built as a module. If so, the module
325 will be called tsl2550.
327 config SENSORS_BH1770
328 tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
331 Say Y here if you want to build a driver for BH1770GLC (ROHM) or
332 SFH7770 (Osram) combined ambient light and proximity sensor chip.
334 To compile this driver as a module, choose M here: the
335 module will be called bh1770glc. If unsure, say N here.
337 config SENSORS_APDS990X
338 tristate "APDS990X combined als and proximity sensors"
341 Say Y here if you want to build a driver for Avago APDS990x
342 combined ambient light and proximity sensor chip.
344 To compile this driver as a module, choose M here: the
345 module will be called apds990x. If unsure, say N here.
348 tristate "Honeywell HMC6352 compass"
351 This driver provides support for the Honeywell HMC6352 compass,
352 providing configuration and heading data via sysfs.
355 tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
358 If you say yes here you get support for Dallas Semiconductor
359 DS1682 Total Elapsed Time Recorder.
361 This driver can also be built as a module. If so, the module
362 will be called ds1682.
364 config VMWARE_BALLOON
365 tristate "VMware Balloon Driver"
366 depends on VMWARE_VMCI && X86 && HYPERVISOR_GUEST
367 select MEMORY_BALLOON
369 This is VMware physical memory management driver which acts
370 like a "balloon" that can be inflated to reclaim physical pages
371 by reserving them in the guest and invalidating them in the
372 monitor, freeing up the underlying machine pages so they can
373 be allocated to other guests. The balloon can also be deflated
374 to allow the guest to use more physical memory.
378 To compile this driver as a module, choose M here: the
379 module will be called vmw_balloon.
382 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
383 select GENERIC_NET_UTILS
384 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
386 This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
387 Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
388 processor. The Topcliff has MAC address and Option ROM data in SROM.
389 This driver can access MAC address and Option ROM data in SROM.
391 This driver also can be used for LAPIS Semiconductor's IOH,
392 ML7213/ML7223/ML7831.
393 ML7213 which is for IVI(In-Vehicle Infotainment) use.
394 ML7223 IOH is for MP(Media Phone) use.
395 ML7831 IOH is for general purpose use.
396 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
397 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
399 To compile this driver as a module, choose M here: the module will
402 config LATTICE_ECP3_CONFIG
403 tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
404 depends on SPI && SYSFS
408 This option enables support for bitstream configuration (programming
409 or loading) of the Lattice ECP3 FPGA family via SPI.
414 bool "Generic on-chip SRAM driver"
416 select GENERIC_ALLOCATOR
417 select SRAM_EXEC if ARM
419 This driver allows you to declare a memory region to be managed by
420 the genalloc API. It is supposed to be used for small on-chip SRAM
421 areas found on many SoCs.
426 config PCI_ENDPOINT_TEST
429 tristate "PCI Endpoint Test driver"
431 Enable this configuration option to enable the host side test driver
435 tristate "Xilinx SDFEC 16"
438 This option enables support for the Xilinx SDFEC (Soft Decision
439 Forward Error Correction) driver. This enables a char driver
442 You may select this driver if your design instantiates the
443 SDFEC(16nm) hardened block. To compile this as a module choose M.
449 default MISC_RTSX_PCI || MISC_RTSX_USB
452 tristate "pvpanic device support"
453 depends on HAS_IOMEM && (ACPI || OF)
455 This driver provides support for the pvpanic device. pvpanic is
456 a paravirtualized device provided by QEMU; it lets a virtual machine
457 (guest) communicate panic events to the host.
459 source "drivers/misc/c2port/Kconfig"
460 source "drivers/misc/eeprom/Kconfig"
461 source "drivers/misc/cb710/Kconfig"
462 source "drivers/misc/ti-st/Kconfig"
463 source "drivers/misc/lis3lv02d/Kconfig"
464 source "drivers/misc/altera-stapl/Kconfig"
465 source "drivers/misc/mei/Kconfig"
466 source "drivers/misc/vmw_vmci/Kconfig"
467 source "drivers/misc/mic/Kconfig"
468 source "drivers/misc/genwqe/Kconfig"
469 source "drivers/misc/echo/Kconfig"
470 source "drivers/misc/cxl/Kconfig"
471 source "drivers/misc/ocxl/Kconfig"
472 source "drivers/misc/cardreader/Kconfig"
473 source "drivers/misc/habanalabs/Kconfig"
474 source "drivers/misc/uacce/Kconfig"