1
2
3
4
5
6menu "Misc devices"
7
8config SENSORS_LIS3LV02D
9 tristate
10 depends on INPUT
11
12config AD525X_DPOT
13 tristate "Analog Devices Digital Potentiometers"
14 depends on (I2C || SPI) && SYSFS
15 help
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.
26
27 See Documentation/misc-devices/ad525x_dpot.rst for the
28 userspace interface.
29
30 This driver can also be built as a module. If so, the module
31 will be called ad525x_dpot.
32
33config AD525X_DPOT_I2C
34 tristate "support I2C bus connection"
35 depends on AD525X_DPOT && I2C
36 help
37 Say Y here if you have a digital potentiometers hooked to an I2C bus.
38
39 To compile this driver as a module, choose M here: the
40 module will be called ad525x_dpot-i2c.
41
42config AD525X_DPOT_SPI
43 tristate "support SPI bus connection"
44 depends on AD525X_DPOT && SPI_MASTER
45 help
46 Say Y here if you have a digital potentiometers hooked to an SPI bus.
47
48 If unsure, say N (but it's safe to say "Y").
49
50 To compile this driver as a module, choose M here: the
51 module will be called ad525x_dpot-spi.
52
53config DUMMY_IRQ
54 tristate "Dummy IRQ handler"
55 help
56 This module accepts a single 'irq' parameter, which it should register for.
57 The sole purpose of this module is to help with debugging of systems on
58 which spurious IRQs would happen on disabled IRQ vector.
59
60config IBM_ASM
61 tristate "Device driver for IBM RSA service processor"
62 depends on X86 && PCI && INPUT
63 depends on SERIAL_8250 || SERIAL_8250=n
64 help
65 This option enables device driver support for in-band access to the
66 IBM RSA (Condor) service processor in eServer xSeries systems.
67 The ibmasm device driver allows user space application to access
68 ASM (Advanced Systems Management) functions on the service
69 processor. The driver is meant to be used in conjunction with
70 a user space API.
71 The ibmasm driver also enables the OS to use the UART on the
72 service processor board as a regular serial port. To make use of
73 this feature serial driver support (CONFIG_SERIAL_8250) must be
74 enabled.
75
76 WARNING: This software may not be supported or function
77 correctly on your IBM server. Please consult the IBM ServerProven
78 website <https://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>
79 for information on the specific driver level and support statement
80 for your IBM server.
81
82config IBMVMC
83 tristate "IBM Virtual Management Channel support"
84 depends on PPC_PSERIES
85 help
86 This is the IBM POWER Virtual Management Channel
87
88 This driver is to be used for the POWER Virtual
89 Management Channel virtual adapter on the PowerVM
90 platform. It provides both request/response and
91 async message support through the /dev/ibmvmc node.
92
93 To compile this driver as a module, choose M here: the
94 module will be called ibmvmc.
95
96config PHANTOM
97 tristate "Sensable PHANToM (PCI)"
98 depends on PCI
99 help
100 Say Y here if you want to build a driver for Sensable PHANToM device.
101
102 This driver is only for PCI PHANToMs.
103
104 If you choose to build module, its name will be phantom. If unsure,
105 say N here.
106
107config TIFM_CORE
108 tristate "TI Flash Media interface support"
109 depends on PCI
110 help
111 If you want support for Texas Instruments(R) Flash Media adapters
112 you should select this option and then also choose an appropriate
113 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
114 support', if you have a TI PCI74xx compatible card reader, for
115 example.
116 You will also have to select some flash card format drivers. MMC/SD
117 cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
118 Interface support (MMC_TIFM_SD)'.
119
120 To compile this driver as a module, choose M here: the module will
121 be called tifm_core.
122
123config TIFM_7XX1
124 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support"
125 depends on PCI && TIFM_CORE
126 default TIFM_CORE
127 help
128 This option enables support for Texas Instruments(R) PCI74xx and
129 PCI76xx families of Flash Media adapters, found in many laptops.
130 To make actual use of the device, you will have to select some
131 flash card format drivers, as outlined in the TIFM_CORE Help.
132
133 To compile this driver as a module, choose M here: the module will
134 be called tifm_7xx1.
135
136config ICS932S401
137 tristate "Integrated Circuits ICS932S401"
138 depends on I2C
139 help
140 If you say yes here you get support for the Integrated Circuits
141 ICS932S401 clock control chips.
142
143 This driver can also be built as a module. If so, the module
144 will be called ics932s401.
145
146config ATMEL_SSC
147 tristate "Device driver for Atmel SSC peripheral"
148 depends on HAS_IOMEM && (ARCH_AT91 || COMPILE_TEST)
149 help
150 This option enables device driver support for Atmel Synchronized
151 Serial Communication peripheral (SSC).
152
153 The SSC peripheral supports a wide variety of serial frame based
154 communications, i.e. I2S, SPI, etc.
155
156 If unsure, say N.
157
158config ENCLOSURE_SERVICES
159 tristate "Enclosure Services"
160 help
161 Provides support for intelligent enclosures (bays which
162 contain storage devices). You also need either a host
163 driver (SCSI/ATA) which supports enclosures
164 or a SCSI enclosure device (SES) to use these services.
165
166config SGI_XP
167 tristate "Support communication between SGI SSIs"
168 depends on NET
169 depends on (IA64_SGI_UV || X86_UV) && SMP
170 depends on X86_64 || BROKEN
171 select SGI_GRU if X86_64 && SMP
172 help
173 An SGI machine can be divided into multiple Single System
174 Images which act independently of each other and have
175 hardware based memory protection from the others. Enabling
176 this feature will allow for direct communication between SSIs
177 based on a network adapter and DMA messaging.
178
179config CS5535_MFGPT
180 tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
181 depends on MFD_CS5535
182 help
183 This driver provides access to MFGPT functionality for other
184 drivers that need timers. MFGPTs are available in the CS5535 and
185 CS5536 companion chips that are found in AMD Geode and several
186 other platforms. They have a better resolution and max interval
187 than the generic PIT, and are suitable for use as high-res timers.
188 You probably don't want to enable this manually; other drivers that
189 make use of it should enable it.
190
191config CS5535_MFGPT_DEFAULT_IRQ
192 int
193 depends on CS5535_MFGPT
194 default 7
195 help
196 MFGPTs on the CS5535 require an interrupt. The selected IRQ
197 can be overridden as a module option as well as by driver that
198 use the cs5535_mfgpt_ API; however, different architectures might
199 want to use a different IRQ by default. This is here for
200 architectures to set as necessary.
201
202config CS5535_CLOCK_EVENT_SRC
203 tristate "CS5535/CS5536 high-res timer (MFGPT) events"
204 depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
205 help
206 This driver provides a clock event source based on the MFGPT
207 timer(s) in the CS5535 and CS5536 companion chips.
208 MFGPTs have a better resolution and max interval than the
209 generic PIT, and are suitable for use as high-res timers.
210
211config HP_ILO
212 tristate "Channel interface driver for the HP iLO processor"
213 depends on PCI
214 help
215 The channel interface driver allows applications to communicate
216 with iLO management processors present on HP ProLiant servers.
217 Upon loading, the driver creates /dev/hpilo/dXccbN files, which
218 can be used to gather data from the management processor, via
219 read and write system calls.
220
221 To compile this driver as a module, choose M here: the
222 module will be called hpilo.
223
224config QCOM_COINCELL
225 tristate "Qualcomm coincell charger support"
226 depends on MFD_SPMI_PMIC || COMPILE_TEST
227 help
228 This driver supports the coincell block found inside of
229 Qualcomm PMICs. The coincell charger provides a means to
230 charge a coincell battery or backup capacitor which is used
231 to maintain PMIC register and RTC state in the absence of
232 external power.
233
234config QCOM_FASTRPC
235 tristate "Qualcomm FastRPC"
236 depends on ARCH_QCOM || COMPILE_TEST
237 depends on RPMSG
238 select DMA_SHARED_BUFFER
239 help
240 Provides a communication mechanism that allows for clients to
241 make remote method invocations across processor boundary to
242 applications DSP processor. Say M if you want to enable this
243 module.
244
245config SGI_GRU
246 tristate "SGI GRU driver"
247 depends on X86_UV && SMP
248 select MMU_NOTIFIER
249 help
250 The GRU is a hardware resource located in the system chipset. The GRU
251 contains memory that can be mmapped into the user address space. This memory is
252 used to communicate with the GRU to perform functions such as load/store,
253 scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
254 instructions using user virtual addresses. GRU instructions (ex., bcopy) use
255 user virtual addresses for operands.
256
257 If you are not running on a SGI UV system, say N.
258
259config SGI_GRU_DEBUG
260 bool "SGI GRU driver debug"
261 depends on SGI_GRU
262 help
263 This option enables additional debugging code for the SGI GRU driver.
264 If you are unsure, say N.
265
266config APDS9802ALS
267 tristate "Medfield Avago APDS9802 ALS Sensor module"
268 depends on I2C
269 help
270 If you say yes here you get support for the ALS APDS9802 ambient
271 light sensor.
272
273 This driver can also be built as a module. If so, the module
274 will be called apds9802als.
275
276config ISL29003
277 tristate "Intersil ISL29003 ambient light sensor"
278 depends on I2C && SYSFS
279 help
280 If you say yes here you get support for the Intersil ISL29003
281 ambient light sensor.
282
283 This driver can also be built as a module. If so, the module
284 will be called isl29003.
285
286config ISL29020
287 tristate "Intersil ISL29020 ambient light sensor"
288 depends on I2C
289 help
290 If you say yes here you get support for the Intersil ISL29020
291 ambient light sensor.
292
293 This driver can also be built as a module. If so, the module
294 will be called isl29020.
295
296config SENSORS_TSL2550
297 tristate "Taos TSL2550 ambient light sensor"
298 depends on I2C && SYSFS
299 help
300 If you say yes here you get support for the Taos TSL2550
301 ambient light sensor.
302
303 This driver can also be built as a module. If so, the module
304 will be called tsl2550.
305
306config SENSORS_BH1770
307 tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
308 depends on I2C
309 help
310 Say Y here if you want to build a driver for BH1770GLC (ROHM) or
311 SFH7770 (Osram) combined ambient light and proximity sensor chip.
312
313 To compile this driver as a module, choose M here: the
314 module will be called bh1770glc. If unsure, say N here.
315
316config SENSORS_APDS990X
317 tristate "APDS990X combined als and proximity sensors"
318 depends on I2C
319 help
320 Say Y here if you want to build a driver for Avago APDS990x
321 combined ambient light and proximity sensor chip.
322
323 To compile this driver as a module, choose M here: the
324 module will be called apds990x. If unsure, say N here.
325
326config HMC6352
327 tristate "Honeywell HMC6352 compass"
328 depends on I2C
329 help
330 This driver provides support for the Honeywell HMC6352 compass,
331 providing configuration and heading data via sysfs.
332
333config DS1682
334 tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
335 depends on I2C
336 help
337 If you say yes here you get support for Dallas Semiconductor
338 DS1682 Total Elapsed Time Recorder.
339
340 This driver can also be built as a module. If so, the module
341 will be called ds1682.
342
343config VMWARE_BALLOON
344 tristate "VMware Balloon Driver"
345 depends on VMWARE_VMCI && X86 && HYPERVISOR_GUEST
346 select MEMORY_BALLOON
347 help
348 This is VMware physical memory management driver which acts
349 like a "balloon" that can be inflated to reclaim physical pages
350 by reserving them in the guest and invalidating them in the
351 monitor, freeing up the underlying machine pages so they can
352 be allocated to other guests. The balloon can also be deflated
353 to allow the guest to use more physical memory.
354
355 If unsure, say N.
356
357 To compile this driver as a module, choose M here: the
358 module will be called vmw_balloon.
359
360config PCH_PHUB
361 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
362 select GENERIC_NET_UTILS
363 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
364 help
365 This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
366 Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
367 processor. The Topcliff has MAC address and Option ROM data in SROM.
368 This driver can access MAC address and Option ROM data in SROM.
369
370 This driver also can be used for LAPIS Semiconductor's IOH,
371 ML7213/ML7223/ML7831.
372 ML7213 which is for IVI(In-Vehicle Infotainment) use.
373 ML7223 IOH is for MP(Media Phone) use.
374 ML7831 IOH is for general purpose use.
375 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
376 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
377
378 To compile this driver as a module, choose M here: the module will
379 be called pch_phub.
380
381config LATTICE_ECP3_CONFIG
382 tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
383 depends on SPI && SYSFS
384 select FW_LOADER
385 default n
386 help
387 This option enables support for bitstream configuration (programming
388 or loading) of the Lattice ECP3 FPGA family via SPI.
389
390 If unsure, say N.
391
392config SRAM
393 bool "Generic on-chip SRAM driver"
394 depends on HAS_IOMEM
395 select GENERIC_ALLOCATOR
396 select SRAM_EXEC if ARM
397 help
398 This driver allows you to declare a memory region to be managed by
399 the genalloc API. It is supposed to be used for small on-chip SRAM
400 areas found on many SoCs.
401
402config SRAM_EXEC
403 bool
404
405config PCI_ENDPOINT_TEST
406 depends on PCI
407 select CRC32
408 tristate "PCI Endpoint Test driver"
409 help
410 Enable this configuration option to enable the host side test driver
411 for PCI Endpoint.
412
413config XILINX_SDFEC
414 tristate "Xilinx SDFEC 16"
415 depends on HAS_IOMEM
416 help
417 This option enables support for the Xilinx SDFEC (Soft Decision
418 Forward Error Correction) driver. This enables a char driver
419 for the SDFEC.
420
421 You may select this driver if your design instantiates the
422 SDFEC(16nm) hardened block. To compile this as a module choose M.
423
424 If unsure, say N.
425
426config MISC_RTSX
427 tristate
428 default MISC_RTSX_PCI || MISC_RTSX_USB
429
430config PVPANIC
431 tristate "pvpanic device support"
432 depends on HAS_IOMEM && (ACPI || OF)
433 help
434 This driver provides support for the pvpanic device. pvpanic is
435 a paravirtualized device provided by QEMU; it lets a virtual machine
436 (guest) communicate panic events to the host.
437
438config HISI_HIKEY_USB
439 tristate "USB GPIO Hub on HiSilicon Hikey 960/970 Platform"
440 depends on (OF && GPIOLIB) || COMPILE_TEST
441 depends on USB_ROLE_SWITCH
442 help
443 If you say yes here this adds support for the on-board USB GPIO hub
444 found on HiKey 960/970 boards, which is necessary to support
445 switching between the dual-role USB-C port and the USB-A host ports
446 using only one USB controller.
447
448source "drivers/misc/c2port/Kconfig"
449source "drivers/misc/eeprom/Kconfig"
450source "drivers/misc/cb710/Kconfig"
451source "drivers/misc/ti-st/Kconfig"
452source "drivers/misc/lis3lv02d/Kconfig"
453source "drivers/misc/altera-stapl/Kconfig"
454source "drivers/misc/mei/Kconfig"
455source "drivers/misc/vmw_vmci/Kconfig"
456source "drivers/misc/genwqe/Kconfig"
457source "drivers/misc/echo/Kconfig"
458source "drivers/misc/cxl/Kconfig"
459source "drivers/misc/ocxl/Kconfig"
460source "drivers/misc/bcm-vk/Kconfig"
461source "drivers/misc/cardreader/Kconfig"
462source "drivers/misc/habanalabs/Kconfig"
463source "drivers/misc/uacce/Kconfig"
464endmenu
465
