Loading...
1#
2# Misc strange devices
3#
4
5menu "Misc devices"
6
7config SENSORS_LIS3LV02D
8 tristate
9 depends on INPUT
10 select INPUT_POLLDEV
11 default n
12
13config AD525X_DPOT
14 tristate "Analog Devices Digital Potentiometers"
15 depends on (I2C || SPI) && SYSFS
16 help
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.
27
28 See Documentation/misc-devices/ad525x_dpot.txt for the
29 userspace interface.
30
31 This driver can also be built as a module. If so, the module
32 will be called ad525x_dpot.
33
34config AD525X_DPOT_I2C
35 tristate "support I2C bus connection"
36 depends on AD525X_DPOT && I2C
37 help
38 Say Y here if you have a digital potentiometers hooked to an I2C bus.
39
40 To compile this driver as a module, choose M here: the
41 module will be called ad525x_dpot-i2c.
42
43config AD525X_DPOT_SPI
44 tristate "support SPI bus connection"
45 depends on AD525X_DPOT && SPI_MASTER
46 help
47 Say Y here if you have a digital potentiometers hooked to an SPI bus.
48
49 If unsure, say N (but it's safe to say "Y").
50
51 To compile this driver as a module, choose M here: the
52 module will be called ad525x_dpot-spi.
53
54config ATMEL_PWM
55 tristate "Atmel AT32/AT91 PWM support"
56 depends on HAVE_CLK
57 help
58 This option enables device driver support for the PWM channels
59 on certain Atmel processors. Pulse Width Modulation is used for
60 purposes including software controlled power-efficient backlights
61 on LCD displays, motor control, and waveform generation.
62
63config ATMEL_TCLIB
64 bool "Atmel AT32/AT91 Timer/Counter Library"
65 depends on (AVR32 || ARCH_AT91)
66 help
67 Select this if you want a library to allocate the Timer/Counter
68 blocks found on many Atmel processors. This facilitates using
69 these blocks by different drivers despite processor differences.
70
71config ATMEL_TCB_CLKSRC
72 bool "TC Block Clocksource"
73 depends on ATMEL_TCLIB
74 default y
75 help
76 Select this to get a high precision clocksource based on a
77 TC block with a 5+ MHz base clock rate. Two timer channels
78 are combined to make a single 32-bit timer.
79
80 When GENERIC_CLOCKEVENTS is defined, the third timer channel
81 may be used as a clock event device supporting oneshot mode
82 (delays of up to two seconds) based on the 32 KiHz clock.
83
84config ATMEL_TCB_CLKSRC_BLOCK
85 int
86 depends on ATMEL_TCB_CLKSRC
87 prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X
88 default 0
89 range 0 1
90 help
91 Some chips provide more than one TC block, so you have the
92 choice of which one to use for the clock framework. The other
93 TC can be used for other purposes, such as PWM generation and
94 interval timing.
95
96config DUMMY_IRQ
97 tristate "Dummy IRQ handler"
98 default n
99 ---help---
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.
103
104config IBM_ASM
105 tristate "Device driver for IBM RSA service processor"
106 depends on X86 && PCI && INPUT
107 ---help---
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
113 a user space API.
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
117 enabled.
118
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
123 for your IBM server.
124
125config PHANTOM
126 tristate "Sensable PHANToM (PCI)"
127 depends on PCI
128 help
129 Say Y here if you want to build a driver for Sensable PHANToM device.
130
131 This driver is only for PCI PHANToMs.
132
133 If you choose to build module, its name will be phantom. If unsure,
134 say N here.
135
136config INTEL_MID_PTI
137 tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard"
138 depends on PCI && TTY && (X86_INTEL_MID || COMPILE_TEST)
139 default n
140 help
141 The PTI (Parallel Trace Interface) driver directs
142 trace data routed from various parts in the system out
143 through an Intel Penwell PTI port and out of the mobile
144 device for analysis with a debugging tool (Lauterbach or Fido).
145
146 You should select this driver if the target kernel is meant for
147 an Intel Atom (non-netbook) mobile device containing a MIPI
148 P1149.7 standard implementation.
149
150config SGI_IOC4
151 tristate "SGI IOC4 Base IO support"
152 depends on PCI
153 ---help---
154 This option enables basic support for the IOC4 chip on certain
155 SGI IO controller cards (IO9, IO10, and PCI-RT). This option
156 does not enable any specific functions on such a card, but provides
157 necessary infrastructure for other drivers to utilize.
158
159 If you have an SGI Altix with an IOC4-based card say Y.
160 Otherwise say N.
161
162config TIFM_CORE
163 tristate "TI Flash Media interface support"
164 depends on PCI
165 help
166 If you want support for Texas Instruments(R) Flash Media adapters
167 you should select this option and then also choose an appropriate
168 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
169 support', if you have a TI PCI74xx compatible card reader, for
170 example.
171 You will also have to select some flash card format drivers. MMC/SD
172 cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
173 Interface support (MMC_TIFM_SD)'.
174
175 To compile this driver as a module, choose M here: the module will
176 be called tifm_core.
177
178config TIFM_7XX1
179 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support"
180 depends on PCI && TIFM_CORE
181 default TIFM_CORE
182 help
183 This option enables support for Texas Instruments(R) PCI74xx and
184 PCI76xx families of Flash Media adapters, found in many laptops.
185 To make actual use of the device, you will have to select some
186 flash card format drivers, as outlined in the TIFM_CORE Help.
187
188 To compile this driver as a module, choose M here: the module will
189 be called tifm_7xx1.
190
191config ICS932S401
192 tristate "Integrated Circuits ICS932S401"
193 depends on I2C
194 help
195 If you say yes here you get support for the Integrated Circuits
196 ICS932S401 clock control chips.
197
198 This driver can also be built as a module. If so, the module
199 will be called ics932s401.
200
201config ATMEL_SSC
202 tristate "Device driver for Atmel SSC peripheral"
203 depends on HAS_IOMEM
204 ---help---
205 This option enables device driver support for Atmel Synchronized
206 Serial Communication peripheral (SSC).
207
208 The SSC peripheral supports a wide variety of serial frame based
209 communications, i.e. I2S, SPI, etc.
210
211 If unsure, say N.
212
213config ENCLOSURE_SERVICES
214 tristate "Enclosure Services"
215 default n
216 help
217 Provides support for intelligent enclosures (bays which
218 contain storage devices). You also need either a host
219 driver (SCSI/ATA) which supports enclosures
220 or a SCSI enclosure device (SES) to use these services.
221
222config SGI_XP
223 tristate "Support communication between SGI SSIs"
224 depends on NET
225 depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
226 select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
227 select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
228 select SGI_GRU if X86_64 && SMP
229 ---help---
230 An SGI machine can be divided into multiple Single System
231 Images which act independently of each other and have
232 hardware based memory protection from the others. Enabling
233 this feature will allow for direct communication between SSIs
234 based on a network adapter and DMA messaging.
235
236config CS5535_MFGPT
237 tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
238 depends on MFD_CS5535
239 default n
240 help
241 This driver provides access to MFGPT functionality for other
242 drivers that need timers. MFGPTs are available in the CS5535 and
243 CS5536 companion chips that are found in AMD Geode and several
244 other platforms. They have a better resolution and max interval
245 than the generic PIT, and are suitable for use as high-res timers.
246 You probably don't want to enable this manually; other drivers that
247 make use of it should enable it.
248
249config CS5535_MFGPT_DEFAULT_IRQ
250 int
251 depends on CS5535_MFGPT
252 default 7
253 help
254 MFGPTs on the CS5535 require an interrupt. The selected IRQ
255 can be overridden as a module option as well as by driver that
256 use the cs5535_mfgpt_ API; however, different architectures might
257 want to use a different IRQ by default. This is here for
258 architectures to set as necessary.
259
260config CS5535_CLOCK_EVENT_SRC
261 tristate "CS5535/CS5536 high-res timer (MFGPT) events"
262 depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
263 help
264 This driver provides a clock event source based on the MFGPT
265 timer(s) in the CS5535 and CS5536 companion chips.
266 MFGPTs have a better resolution and max interval than the
267 generic PIT, and are suitable for use as high-res timers.
268
269config HP_ILO
270 tristate "Channel interface driver for the HP iLO processor"
271 depends on PCI
272 default n
273 help
274 The channel interface driver allows applications to communicate
275 with iLO management processors present on HP ProLiant servers.
276 Upon loading, the driver creates /dev/hpilo/dXccbN files, which
277 can be used to gather data from the management processor, via
278 read and write system calls.
279
280 To compile this driver as a module, choose M here: the
281 module will be called hpilo.
282
283config SGI_GRU
284 tristate "SGI GRU driver"
285 depends on X86_UV && SMP
286 default n
287 select MMU_NOTIFIER
288 ---help---
289 The GRU is a hardware resource located in the system chipset. The GRU
290 contains memory that can be mmapped into the user address space. This memory is
291 used to communicate with the GRU to perform functions such as load/store,
292 scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
293 instructions using user virtual addresses. GRU instructions (ex., bcopy) use
294 user virtual addresses for operands.
295
296 If you are not running on a SGI UV system, say N.
297
298config SGI_GRU_DEBUG
299 bool "SGI GRU driver debug"
300 depends on SGI_GRU
301 default n
302 ---help---
303 This option enables additional debugging code for the SGI GRU driver.
304 If you are unsure, say N.
305
306config APDS9802ALS
307 tristate "Medfield Avago APDS9802 ALS Sensor module"
308 depends on I2C
309 help
310 If you say yes here you get support for the ALS APDS9802 ambient
311 light sensor.
312
313 This driver can also be built as a module. If so, the module
314 will be called apds9802als.
315
316config ISL29003
317 tristate "Intersil ISL29003 ambient light sensor"
318 depends on I2C && SYSFS
319 help
320 If you say yes here you get support for the Intersil ISL29003
321 ambient light sensor.
322
323 This driver can also be built as a module. If so, the module
324 will be called isl29003.
325
326config ISL29020
327 tristate "Intersil ISL29020 ambient light sensor"
328 depends on I2C
329 help
330 If you say yes here you get support for the Intersil ISL29020
331 ambient light sensor.
332
333 This driver can also be built as a module. If so, the module
334 will be called isl29020.
335
336config SENSORS_TSL2550
337 tristate "Taos TSL2550 ambient light sensor"
338 depends on I2C && SYSFS
339 help
340 If you say yes here you get support for the Taos TSL2550
341 ambient light sensor.
342
343 This driver can also be built as a module. If so, the module
344 will be called tsl2550.
345
346config SENSORS_BH1780
347 tristate "ROHM BH1780GLI ambient light sensor"
348 depends on I2C && SYSFS
349 help
350 If you say yes here you get support for the ROHM BH1780GLI
351 ambient light sensor.
352
353 This driver can also be built as a module. If so, the module
354 will be called bh1780gli.
355
356config SENSORS_BH1770
357 tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
358 depends on I2C
359 ---help---
360 Say Y here if you want to build a driver for BH1770GLC (ROHM) or
361 SFH7770 (Osram) combined ambient light and proximity sensor chip.
362
363 To compile this driver as a module, choose M here: the
364 module will be called bh1770glc. If unsure, say N here.
365
366config SENSORS_APDS990X
367 tristate "APDS990X combined als and proximity sensors"
368 depends on I2C
369 default n
370 ---help---
371 Say Y here if you want to build a driver for Avago APDS990x
372 combined ambient light and proximity sensor chip.
373
374 To compile this driver as a module, choose M here: the
375 module will be called apds990x. If unsure, say N here.
376
377config HMC6352
378 tristate "Honeywell HMC6352 compass"
379 depends on I2C
380 help
381 This driver provides support for the Honeywell HMC6352 compass,
382 providing configuration and heading data via sysfs.
383
384config DS1682
385 tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
386 depends on I2C
387 help
388 If you say yes here you get support for Dallas Semiconductor
389 DS1682 Total Elapsed Time Recorder.
390
391 This driver can also be built as a module. If so, the module
392 will be called ds1682.
393
394config SPEAR13XX_PCIE_GADGET
395 bool "PCIe gadget support for SPEAr13XX platform"
396 depends on ARCH_SPEAR13XX && BROKEN
397 default n
398 help
399 This option enables gadget support for PCIe controller. If
400 board file defines any controller as PCIe endpoint then a sysfs
401 entry will be created for that controller. User can use these
402 sysfs node to configure PCIe EP as per his requirements.
403
404config TI_DAC7512
405 tristate "Texas Instruments DAC7512"
406 depends on SPI && SYSFS
407 help
408 If you say yes here you get support for the Texas Instruments
409 DAC7512 16-bit digital-to-analog converter.
410
411 This driver can also be built as a module. If so, the module
412 will be called ti_dac7512.
413
414config VMWARE_BALLOON
415 tristate "VMware Balloon Driver"
416 depends on X86 && HYPERVISOR_GUEST
417 help
418 This is VMware physical memory management driver which acts
419 like a "balloon" that can be inflated to reclaim physical pages
420 by reserving them in the guest and invalidating them in the
421 monitor, freeing up the underlying machine pages so they can
422 be allocated to other guests. The balloon can also be deflated
423 to allow the guest to use more physical memory.
424
425 If unsure, say N.
426
427 To compile this driver as a module, choose M here: the
428 module will be called vmw_balloon.
429
430config ARM_CHARLCD
431 bool "ARM Ltd. Character LCD Driver"
432 depends on PLAT_VERSATILE
433 help
434 This is a driver for the character LCD found on the ARM Ltd.
435 Versatile and RealView Platform Baseboards. It doesn't do
436 very much more than display the text "ARM Linux" on the first
437 line and the Linux version on the second line, but that's
438 still useful.
439
440config BMP085
441 bool
442 depends on SYSFS
443
444config BMP085_I2C
445 tristate "BMP085 digital pressure sensor on I2C"
446 select BMP085
447 select REGMAP_I2C
448 depends on I2C && SYSFS
449 help
450 Say Y here if you want to support Bosch Sensortec's digital pressure
451 sensor hooked to an I2C bus.
452
453 To compile this driver as a module, choose M here: the
454 module will be called bmp085-i2c.
455
456config BMP085_SPI
457 tristate "BMP085 digital pressure sensor on SPI"
458 select BMP085
459 select REGMAP_SPI
460 depends on SPI_MASTER && SYSFS
461 help
462 Say Y here if you want to support Bosch Sensortec's digital pressure
463 sensor hooked to an SPI bus.
464
465 To compile this driver as a module, choose M here: the
466 module will be called bmp085-spi.
467
468config PCH_PHUB
469 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
470 select GENERIC_NET_UTILS
471 depends on PCI
472 help
473 This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
474 Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
475 processor. The Topcliff has MAC address and Option ROM data in SROM.
476 This driver can access MAC address and Option ROM data in SROM.
477
478 This driver also can be used for LAPIS Semiconductor's IOH,
479 ML7213/ML7223/ML7831.
480 ML7213 which is for IVI(In-Vehicle Infotainment) use.
481 ML7223 IOH is for MP(Media Phone) use.
482 ML7831 IOH is for general purpose use.
483 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
484 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
485
486 To compile this driver as a module, choose M here: the module will
487 be called pch_phub.
488
489config USB_SWITCH_FSA9480
490 tristate "FSA9480 USB Switch"
491 depends on I2C
492 help
493 The FSA9480 is a USB port accessory detector and switch.
494 The FSA9480 is fully controlled using I2C and enables USB data,
495 stereo and mono audio, video, microphone and UART data to use
496 a common connector port.
497
498config LATTICE_ECP3_CONFIG
499 tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
500 depends on SPI && SYSFS
501 select FW_LOADER
502 default n
503 help
504 This option enables support for bitstream configuration (programming
505 or loading) of the Lattice ECP3 FPGA family via SPI.
506
507 If unsure, say N.
508
509config SRAM
510 bool "Generic on-chip SRAM driver"
511 depends on HAS_IOMEM
512 select GENERIC_ALLOCATOR
513 help
514 This driver allows you to declare a memory region to be managed by
515 the genalloc API. It is supposed to be used for small on-chip SRAM
516 areas found on many SoCs.
517
518source "drivers/misc/c2port/Kconfig"
519source "drivers/misc/eeprom/Kconfig"
520source "drivers/misc/cb710/Kconfig"
521source "drivers/misc/ti-st/Kconfig"
522source "drivers/misc/lis3lv02d/Kconfig"
523source "drivers/misc/carma/Kconfig"
524source "drivers/misc/altera-stapl/Kconfig"
525source "drivers/misc/mei/Kconfig"
526source "drivers/misc/vmw_vmci/Kconfig"
527source "drivers/misc/mic/Kconfig"
528source "drivers/misc/genwqe/Kconfig"
529source "drivers/misc/echo/Kconfig"
530endmenu
1# SPDX-License-Identifier: GPL-2.0-only
2#
3# Misc strange devices
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 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 SMPRO_ERRMON
180 tristate "Ampere Computing SMPro error monitor driver"
181 depends on MFD_SMPRO || COMPILE_TEST
182 help
183 Say Y here to get support for the SMpro error monitor function
184 provided by Ampere Computing's Altra and Altra Max SoCs. Upon
185 loading, the driver creates sysfs files which can be use to gather
186 multiple HW error data reported via read and write system calls.
187
188 To compile this driver as a module, say M here. The driver will be
189 called smpro-errmon.
190
191config SMPRO_MISC
192 tristate "Ampere Computing SMPro miscellaneous driver"
193 depends on MFD_SMPRO || COMPILE_TEST
194 help
195 Say Y here to get support for the SMpro error miscellalenous function
196 provided by Ampere Computing's Altra and Altra Max SoCs.
197
198 To compile this driver as a module, say M here. The driver will be
199 called smpro-misc.
200
201config CS5535_MFGPT
202 tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
203 depends on MFD_CS5535
204 help
205 This driver provides access to MFGPT functionality for other
206 drivers that need timers. MFGPTs are available in the CS5535 and
207 CS5536 companion chips that are found in AMD Geode and several
208 other platforms. They have a better resolution and max interval
209 than the generic PIT, and are suitable for use as high-res timers.
210 You probably don't want to enable this manually; other drivers that
211 make use of it should enable it.
212
213config CS5535_MFGPT_DEFAULT_IRQ
214 int
215 depends on CS5535_MFGPT
216 default 7
217 help
218 MFGPTs on the CS5535 require an interrupt. The selected IRQ
219 can be overridden as a module option as well as by driver that
220 use the cs5535_mfgpt_ API; however, different architectures might
221 want to use a different IRQ by default. This is here for
222 architectures to set as necessary.
223
224config CS5535_CLOCK_EVENT_SRC
225 tristate "CS5535/CS5536 high-res timer (MFGPT) events"
226 depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
227 help
228 This driver provides a clock event source based on the MFGPT
229 timer(s) in the CS5535 and CS5536 companion chips.
230 MFGPTs have a better resolution and max interval than the
231 generic PIT, and are suitable for use as high-res timers.
232
233config GEHC_ACHC
234 tristate "GEHC ACHC support"
235 depends on SPI && SYSFS
236 depends on SOC_IMX53 || COMPILE_TEST
237 select FW_LOADER
238 help
239 Support for GE ACHC microcontroller, that is part of the GE
240 PPD device.
241
242 To compile this driver as a module, choose M here: the
243 module will be called gehc-achc.
244
245config HI6421V600_IRQ
246 tristate "HiSilicon Hi6421v600 IRQ and powerkey"
247 depends on OF
248 depends on SPMI
249 depends on HAS_IOMEM
250 select MFD_CORE
251 select REGMAP_SPMI
252 help
253 This driver provides IRQ handling for Hi6421v600, used on
254 some Kirin chipsets, like the one at Hikey 970.
255
256config HP_ILO
257 tristate "Channel interface driver for the HP iLO processor"
258 depends on PCI
259 help
260 The channel interface driver allows applications to communicate
261 with iLO management processors present on HP ProLiant servers.
262 Upon loading, the driver creates /dev/hpilo/dXccbN files, which
263 can be used to gather data from the management processor, via
264 read and write system calls.
265
266 To compile this driver as a module, choose M here: the
267 module will be called hpilo.
268
269config QCOM_COINCELL
270 tristate "Qualcomm coincell charger support"
271 depends on MFD_SPMI_PMIC || COMPILE_TEST
272 help
273 This driver supports the coincell block found inside of
274 Qualcomm PMICs. The coincell charger provides a means to
275 charge a coincell battery or backup capacitor which is used
276 to maintain PMIC register and RTC state in the absence of
277 external power.
278
279config QCOM_FASTRPC
280 tristate "Qualcomm FastRPC"
281 depends on ARCH_QCOM || COMPILE_TEST
282 depends on RPMSG
283 select DMA_SHARED_BUFFER
284 select QCOM_SCM
285 help
286 Provides a communication mechanism that allows for clients to
287 make remote method invocations across processor boundary to
288 applications DSP processor. Say M if you want to enable this
289 module.
290
291config SGI_GRU
292 tristate "SGI GRU driver"
293 depends on X86_UV && SMP
294 select MMU_NOTIFIER
295 help
296 The GRU is a hardware resource located in the system chipset. The GRU
297 contains memory that can be mmapped into the user address space. This memory is
298 used to communicate with the GRU to perform functions such as load/store,
299 scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
300 instructions using user virtual addresses. GRU instructions (ex., bcopy) use
301 user virtual addresses for operands.
302
303 If you are not running on a SGI UV system, say N.
304
305config SGI_GRU_DEBUG
306 bool "SGI GRU driver debug"
307 depends on SGI_GRU
308 help
309 This option enables additional debugging code for the SGI GRU driver.
310 If you are unsure, say N.
311
312config APDS9802ALS
313 tristate "Medfield Avago APDS9802 ALS Sensor module"
314 depends on I2C
315 help
316 If you say yes here you get support for the ALS APDS9802 ambient
317 light sensor.
318
319 This driver can also be built as a module. If so, the module
320 will be called apds9802als.
321
322config ISL29003
323 tristate "Intersil ISL29003 ambient light sensor"
324 depends on I2C && SYSFS
325 help
326 If you say yes here you get support for the Intersil ISL29003
327 ambient light sensor.
328
329 This driver can also be built as a module. If so, the module
330 will be called isl29003.
331
332config ISL29020
333 tristate "Intersil ISL29020 ambient light sensor"
334 depends on I2C
335 help
336 If you say yes here you get support for the Intersil ISL29020
337 ambient light sensor.
338
339 This driver can also be built as a module. If so, the module
340 will be called isl29020.
341
342config SENSORS_TSL2550
343 tristate "Taos TSL2550 ambient light sensor"
344 depends on I2C && SYSFS
345 help
346 If you say yes here you get support for the Taos TSL2550
347 ambient light sensor.
348
349 This driver can also be built as a module. If so, the module
350 will be called tsl2550.
351
352config SENSORS_BH1770
353 tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
354 depends on I2C
355 help
356 Say Y here if you want to build a driver for BH1770GLC (ROHM) or
357 SFH7770 (Osram) combined ambient light and proximity sensor chip.
358
359 To compile this driver as a module, choose M here: the
360 module will be called bh1770glc. If unsure, say N here.
361
362config SENSORS_APDS990X
363 tristate "APDS990X combined als and proximity sensors"
364 depends on I2C
365 help
366 Say Y here if you want to build a driver for Avago APDS990x
367 combined ambient light and proximity sensor chip.
368
369 To compile this driver as a module, choose M here: the
370 module will be called apds990x. If unsure, say N here.
371
372config HMC6352
373 tristate "Honeywell HMC6352 compass"
374 depends on I2C
375 help
376 This driver provides support for the Honeywell HMC6352 compass,
377 providing configuration and heading data via sysfs.
378
379config DS1682
380 tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
381 depends on I2C
382 help
383 If you say yes here you get support for Dallas Semiconductor
384 DS1682 Total Elapsed Time Recorder.
385
386 This driver can also be built as a module. If so, the module
387 will be called ds1682.
388
389config VMWARE_BALLOON
390 tristate "VMware Balloon Driver"
391 depends on VMWARE_VMCI && X86 && HYPERVISOR_GUEST
392 select MEMORY_BALLOON
393 help
394 This is VMware physical memory management driver which acts
395 like a "balloon" that can be inflated to reclaim physical pages
396 by reserving them in the guest and invalidating them in the
397 monitor, freeing up the underlying machine pages so they can
398 be allocated to other guests. The balloon can also be deflated
399 to allow the guest to use more physical memory.
400
401 If unsure, say N.
402
403 To compile this driver as a module, choose M here: the
404 module will be called vmw_balloon.
405
406config PCH_PHUB
407 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
408 select GENERIC_NET_UTILS
409 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
410 help
411 This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
412 Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
413 processor. The Topcliff has MAC address and Option ROM data in SROM.
414 This driver can access MAC address and Option ROM data in SROM.
415
416 This driver also can be used for LAPIS Semiconductor's IOH,
417 ML7213/ML7223/ML7831.
418 ML7213 which is for IVI(In-Vehicle Infotainment) use.
419 ML7223 IOH is for MP(Media Phone) use.
420 ML7831 IOH is for general purpose use.
421 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
422 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
423
424 To compile this driver as a module, choose M here: the module will
425 be called pch_phub.
426
427config LATTICE_ECP3_CONFIG
428 tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
429 depends on SPI && SYSFS
430 select FW_LOADER
431 default n
432 help
433 This option enables support for bitstream configuration (programming
434 or loading) of the Lattice ECP3 FPGA family via SPI.
435
436 If unsure, say N.
437
438config SRAM
439 bool "Generic on-chip SRAM driver"
440 depends on HAS_IOMEM
441 select GENERIC_ALLOCATOR
442 select SRAM_EXEC if ARM
443 help
444 This driver allows you to declare a memory region to be managed by
445 the genalloc API. It is supposed to be used for small on-chip SRAM
446 areas found on many SoCs.
447
448config SRAM_EXEC
449 bool
450
451config DW_XDATA_PCIE
452 depends on PCI
453 tristate "Synopsys DesignWare xData PCIe driver"
454 help
455 This driver allows controlling Synopsys DesignWare PCIe traffic
456 generator IP also known as xData, present in Synopsys DesignWare
457 PCIe Endpoint prototype.
458
459 If unsure, say N.
460
461config PCI_ENDPOINT_TEST
462 depends on PCI
463 select CRC32
464 tristate "PCI Endpoint Test driver"
465 help
466 Enable this configuration option to enable the host side test driver
467 for PCI Endpoint.
468
469config XILINX_SDFEC
470 tristate "Xilinx SDFEC 16"
471 depends on HAS_IOMEM
472 help
473 This option enables support for the Xilinx SDFEC (Soft Decision
474 Forward Error Correction) driver. This enables a char driver
475 for the SDFEC.
476
477 You may select this driver if your design instantiates the
478 SDFEC(16nm) hardened block. To compile this as a module choose M.
479
480 If unsure, say N.
481
482config MISC_RTSX
483 tristate
484 default MISC_RTSX_PCI || MISC_RTSX_USB
485
486config HISI_HIKEY_USB
487 tristate "USB GPIO Hub on HiSilicon Hikey 960/970 Platform"
488 depends on (OF && GPIOLIB) || COMPILE_TEST
489 depends on USB_ROLE_SWITCH
490 help
491 If you say yes here this adds support for the on-board USB GPIO hub
492 found on HiKey 960/970 boards, which is necessary to support
493 switching between the dual-role USB-C port and the USB-A host ports
494 using only one USB controller.
495
496config OPEN_DICE
497 tristate "Open Profile for DICE driver"
498 depends on OF_RESERVED_MEM
499 depends on HAS_IOMEM
500 help
501 This driver exposes a DICE reserved memory region to userspace via
502 a character device. The memory region contains Compound Device
503 Identifiers (CDIs) generated by firmware as an output of DICE
504 measured boot flow. Userspace can use CDIs for remote attestation
505 and sealing.
506
507 If unsure, say N.
508
509config VCPU_STALL_DETECTOR
510 tristate "Guest vCPU stall detector"
511 depends on OF && HAS_IOMEM
512 help
513 When this driver is bound inside a KVM guest, it will
514 periodically "pet" an MMIO stall detector device from each vCPU
515 and allow the host to detect vCPU stalls.
516
517 To compile this driver as a module, choose M here: the module
518 will be called vcpu_stall_detector.
519
520 If you do not intend to run this kernel as a guest, say N.
521
522config TMR_MANAGER
523 tristate "Select TMR Manager"
524 depends on MICROBLAZE && MB_MANAGER
525 help
526 This option enables the driver developed for TMR Manager.
527 The Triple Modular Redundancy(TMR) manager provides support for
528 fault detection.
529
530 Say N here unless you know what you are doing.
531
532config TMR_INJECT
533 tristate "Select TMR Inject"
534 depends on TMR_MANAGER && FAULT_INJECTION_DEBUG_FS
535 help
536 This option enables the driver developed for TMR Inject.
537 The Triple Modular Redundancy(TMR) Inject provides
538 fault injection.
539
540 Say N here unless you know what you are doing.
541
542config TPS6594_ESM
543 tristate "TI TPS6594 Error Signal Monitor support"
544 depends on MFD_TPS6594
545 default MFD_TPS6594
546 help
547 Support ESM (Error Signal Monitor) on TPS6594 PMIC devices.
548 ESM is used typically to reboot the board in error condition.
549
550 This driver can also be built as a module. If so, the module
551 will be called tps6594-esm.
552
553config TPS6594_PFSM
554 tristate "TI TPS6594 Pre-configurable Finite State Machine support"
555 depends on MFD_TPS6594
556 default MFD_TPS6594
557 help
558 Support PFSM (Pre-configurable Finite State Machine) on TPS6594 PMIC devices.
559 These devices integrate a finite state machine engine, which manages the state
560 of the device during operating state transition.
561
562 This driver can also be built as a module. If so, the module
563 will be called tps6594-pfsm.
564
565config NSM
566 tristate "Nitro (Enclaves) Security Module support"
567 depends on VIRTIO
568 select HW_RANDOM
569 help
570 This driver provides support for the Nitro Security Module
571 in AWS EC2 Nitro based Enclaves. The driver exposes a /dev/nsm
572 device user space can use to communicate with the hypervisor.
573
574 To compile this driver as a module, choose M here.
575 The module will be called nsm.
576
577source "drivers/misc/c2port/Kconfig"
578source "drivers/misc/eeprom/Kconfig"
579source "drivers/misc/cb710/Kconfig"
580source "drivers/misc/ti-st/Kconfig"
581source "drivers/misc/lis3lv02d/Kconfig"
582source "drivers/misc/altera-stapl/Kconfig"
583source "drivers/misc/mei/Kconfig"
584source "drivers/misc/vmw_vmci/Kconfig"
585source "drivers/misc/genwqe/Kconfig"
586source "drivers/misc/echo/Kconfig"
587source "drivers/misc/cxl/Kconfig"
588source "drivers/misc/ocxl/Kconfig"
589source "drivers/misc/bcm-vk/Kconfig"
590source "drivers/misc/cardreader/Kconfig"
591source "drivers/misc/uacce/Kconfig"
592source "drivers/misc/pvpanic/Kconfig"
593source "drivers/misc/mchp_pci1xxxx/Kconfig"
594endmenu