xref: /linux/drivers/misc/Kconfig (revision e58e871becec2d3b04ed91c0c16fe8deac9c9dfa)
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_TCLIB
55	bool "Atmel AT32/AT91 Timer/Counter Library"
56	depends on (AVR32 || ARCH_AT91)
57	help
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.
61
62config ATMEL_TCB_CLKSRC
63	bool "TC Block Clocksource"
64	depends on ATMEL_TCLIB
65	default y
66	help
67	  Select this to get a high precision clocksource based on a
68	  TC block with a 5+ MHz base clock rate.  Two timer channels
69	  are combined to make a single 32-bit timer.
70
71	  When GENERIC_CLOCKEVENTS is defined, the third timer channel
72	  may be used as a clock event device supporting oneshot mode
73	  (delays of up to two seconds) based on the 32 KiHz clock.
74
75config ATMEL_TCB_CLKSRC_BLOCK
76	int
77	depends on ATMEL_TCB_CLKSRC
78	prompt "TC Block" if CPU_AT32AP700X
79	default 0
80	range 0 1
81	help
82	  Some chips provide more than one TC block, so you have the
83	  choice of which one to use for the clock framework.  The other
84	  TC can be used for other purposes, such as PWM generation and
85	  interval timing.
86
87config DUMMY_IRQ
88	tristate "Dummy IRQ handler"
89	default n
90	---help---
91	  This module accepts a single 'irq' parameter, which it should register for.
92	  The sole purpose of this module is to help with debugging of systems on
93	  which spurious IRQs would happen on disabled IRQ vector.
94
95config IBM_ASM
96	tristate "Device driver for IBM RSA service processor"
97	depends on X86 && PCI && INPUT
98	depends on SERIAL_8250 || SERIAL_8250=n
99	---help---
100	  This option enables device driver support for in-band access to the
101	  IBM RSA (Condor) service processor in eServer xSeries systems.
102	  The ibmasm device driver allows user space application to access
103	  ASM (Advanced Systems Management) functions on the service
104	  processor. The driver is meant to be used in conjunction with
105	  a user space API.
106	  The ibmasm driver also enables the OS to use the UART on the
107	  service processor board as a regular serial port. To make use of
108	  this feature serial driver support (CONFIG_SERIAL_8250) must be
109	  enabled.
110
111	  WARNING: This software may not be supported or function
112	  correctly on your IBM server. Please consult the IBM ServerProven
113	  website <http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>
114	  for information on the specific driver level and support statement
115	  for your IBM server.
116
117config PHANTOM
118	tristate "Sensable PHANToM (PCI)"
119	depends on PCI
120	help
121	  Say Y here if you want to build a driver for Sensable PHANToM device.
122
123	  This driver is only for PCI PHANToMs.
124
125	  If you choose to build module, its name will be phantom. If unsure,
126	  say N here.
127
128config INTEL_MID_PTI
129	tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard"
130	depends on PCI && TTY && (X86_INTEL_MID || COMPILE_TEST)
131	default n
132	help
133	  The PTI (Parallel Trace Interface) driver directs
134	  trace data routed from various parts in the system out
135	  through an Intel Penwell PTI port and out of the mobile
136	  device for analysis with a debugging tool (Lauterbach or Fido).
137
138	  You should select this driver if the target kernel is meant for
139	  an Intel Atom (non-netbook) mobile device containing a MIPI
140	  P1149.7 standard implementation.
141
142config SGI_IOC4
143	tristate "SGI IOC4 Base IO support"
144	depends on PCI
145	---help---
146	  This option enables basic support for the IOC4 chip on certain
147	  SGI IO controller cards (IO9, IO10, and PCI-RT).  This option
148	  does not enable any specific functions on such a card, but provides
149	  necessary infrastructure for other drivers to utilize.
150
151	  If you have an SGI Altix with an IOC4-based card say Y.
152	  Otherwise say N.
153
154config TIFM_CORE
155	tristate "TI Flash Media interface support"
156	depends on PCI
157	help
158	  If you want support for Texas Instruments(R) Flash Media adapters
159	  you should select this option and then also choose an appropriate
160	  host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
161	  support', if you have a TI PCI74xx compatible card reader, for
162	  example.
163	  You will also have to select some flash card format drivers. MMC/SD
164	  cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
165	  Interface support (MMC_TIFM_SD)'.
166
167	  To compile this driver as a module, choose M here: the module will
168	  be called tifm_core.
169
170config TIFM_7XX1
171	tristate "TI Flash Media PCI74xx/PCI76xx host adapter support"
172	depends on PCI && TIFM_CORE
173	default TIFM_CORE
174	help
175	  This option enables support for Texas Instruments(R) PCI74xx and
176	  PCI76xx families of Flash Media adapters, found in many laptops.
177	  To make actual use of the device, you will have to select some
178	  flash card format drivers, as outlined in the TIFM_CORE Help.
179
180	  To compile this driver as a module, choose M here: the module will
181	  be called tifm_7xx1.
182
183config ICS932S401
184	tristate "Integrated Circuits ICS932S401"
185	depends on I2C
186	help
187	  If you say yes here you get support for the Integrated Circuits
188	  ICS932S401 clock control chips.
189
190	  This driver can also be built as a module. If so, the module
191	  will be called ics932s401.
192
193config ATMEL_SSC
194	tristate "Device driver for Atmel SSC peripheral"
195	depends on HAS_IOMEM && (AVR32 || ARCH_AT91 || COMPILE_TEST)
196	---help---
197	  This option enables device driver support for Atmel Synchronized
198	  Serial Communication peripheral (SSC).
199
200	  The SSC peripheral supports a wide variety of serial frame based
201	  communications, i.e. I2S, SPI, etc.
202
203	  If unsure, say N.
204
205config ENCLOSURE_SERVICES
206	tristate "Enclosure Services"
207	default n
208	help
209	  Provides support for intelligent enclosures (bays which
210	  contain storage devices).  You also need either a host
211	  driver (SCSI/ATA) which supports enclosures
212	  or a SCSI enclosure device (SES) to use these services.
213
214config SGI_XP
215	tristate "Support communication between SGI SSIs"
216	depends on NET
217	depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
218	select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
219	select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
220	select SGI_GRU if X86_64 && SMP
221	---help---
222	  An SGI machine can be divided into multiple Single System
223	  Images which act independently of each other and have
224	  hardware based memory protection from the others.  Enabling
225	  this feature will allow for direct communication between SSIs
226	  based on a network adapter and DMA messaging.
227
228config CS5535_MFGPT
229	tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
230	depends on MFD_CS5535
231	default n
232	help
233	  This driver provides access to MFGPT functionality for other
234	  drivers that need timers.  MFGPTs are available in the CS5535 and
235	  CS5536 companion chips that are found in AMD Geode and several
236	  other platforms.  They have a better resolution and max interval
237	  than the generic PIT, and are suitable for use as high-res timers.
238	  You probably don't want to enable this manually; other drivers that
239	  make use of it should enable it.
240
241config CS5535_MFGPT_DEFAULT_IRQ
242	int
243	depends on CS5535_MFGPT
244	default 7
245	help
246	  MFGPTs on the CS5535 require an interrupt.  The selected IRQ
247	  can be overridden as a module option as well as by driver that
248	  use the cs5535_mfgpt_ API; however, different architectures might
249	  want to use a different IRQ by default.  This is here for
250	  architectures to set as necessary.
251
252config CS5535_CLOCK_EVENT_SRC
253	tristate "CS5535/CS5536 high-res timer (MFGPT) events"
254	depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
255	help
256	  This driver provides a clock event source based on the MFGPT
257	  timer(s) in the CS5535 and CS5536 companion chips.
258	  MFGPTs have a better resolution and max interval than the
259	  generic PIT, and are suitable for use as high-res timers.
260
261config HP_ILO
262	tristate "Channel interface driver for the HP iLO processor"
263	depends on PCI
264	default n
265	help
266	  The channel interface driver allows applications to communicate
267	  with iLO management processors present on HP ProLiant servers.
268	  Upon loading, the driver creates /dev/hpilo/dXccbN files, which
269	  can be used to gather data from the management processor, via
270	  read and write system calls.
271
272	  To compile this driver as a module, choose M here: the
273	  module will be called hpilo.
274
275config QCOM_COINCELL
276	tristate "Qualcomm coincell charger support"
277	depends on MFD_SPMI_PMIC || COMPILE_TEST
278	help
279	  This driver supports the coincell block found inside of
280	  Qualcomm PMICs.  The coincell charger provides a means to
281	  charge a coincell battery or backup capacitor which is used
282	  to maintain PMIC register and RTC state in the absence of
283	  external power.
284
285config SGI_GRU
286	tristate "SGI GRU driver"
287	depends on X86_UV && SMP
288	default n
289	select MMU_NOTIFIER
290	---help---
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.
297
298	If you are not running on a SGI UV system, say N.
299
300config SGI_GRU_DEBUG
301	bool  "SGI GRU driver debug"
302	depends on SGI_GRU
303	default n
304	---help---
305	This option enables additional debugging code for the SGI GRU driver.
306	If you are unsure, say N.
307
308config APDS9802ALS
309	tristate "Medfield Avago APDS9802 ALS Sensor module"
310	depends on I2C
311	help
312	  If you say yes here you get support for the ALS APDS9802 ambient
313	  light sensor.
314
315	  This driver can also be built as a module.  If so, the module
316	  will be called apds9802als.
317
318config ISL29003
319	tristate "Intersil ISL29003 ambient light sensor"
320	depends on I2C && SYSFS
321	help
322	  If you say yes here you get support for the Intersil ISL29003
323	  ambient light sensor.
324
325	  This driver can also be built as a module.  If so, the module
326	  will be called isl29003.
327
328config ISL29020
329	tristate "Intersil ISL29020 ambient light sensor"
330	depends on I2C
331	help
332	  If you say yes here you get support for the Intersil ISL29020
333	  ambient light sensor.
334
335	  This driver can also be built as a module.  If so, the module
336	  will be called isl29020.
337
338config SENSORS_TSL2550
339	tristate "Taos TSL2550 ambient light sensor"
340	depends on I2C && SYSFS
341	help
342	  If you say yes here you get support for the Taos TSL2550
343	  ambient light sensor.
344
345	  This driver can also be built as a module.  If so, the module
346	  will be called tsl2550.
347
348config SENSORS_BH1770
349         tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
350         depends on I2C
351         ---help---
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.
354
355           To compile this driver as a module, choose M here: the
356           module will be called bh1770glc. If unsure, say N here.
357
358config SENSORS_APDS990X
359	 tristate "APDS990X combined als and proximity sensors"
360	 depends on I2C
361	 default n
362	 ---help---
363	   Say Y here if you want to build a driver for Avago APDS990x
364	   combined ambient light and proximity sensor chip.
365
366	   To compile this driver as a module, choose M here: the
367	   module will be called apds990x. If unsure, say N here.
368
369config HMC6352
370	tristate "Honeywell HMC6352 compass"
371	depends on I2C
372	help
373	  This driver provides support for the Honeywell HMC6352 compass,
374	  providing configuration and heading data via sysfs.
375
376config DS1682
377	tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
378	depends on I2C
379	help
380	  If you say yes here you get support for Dallas Semiconductor
381	  DS1682 Total Elapsed Time Recorder.
382
383	  This driver can also be built as a module.  If so, the module
384	  will be called ds1682.
385
386config SPEAR13XX_PCIE_GADGET
387	bool "PCIe gadget support for SPEAr13XX platform"
388	depends on ARCH_SPEAR13XX && BROKEN
389	default n
390	help
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.
395
396config TI_DAC7512
397	tristate "Texas Instruments DAC7512"
398	depends on SPI && SYSFS
399	help
400	  If you say yes here you get support for the Texas Instruments
401	  DAC7512 16-bit digital-to-analog converter.
402
403	  This driver can also be built as a module. If so, the module
404	  will be called ti_dac7512.
405
406config VMWARE_BALLOON
407	tristate "VMware Balloon Driver"
408	depends on VMWARE_VMCI && X86 && HYPERVISOR_GUEST
409	help
410	  This is VMware physical memory management driver which acts
411	  like a "balloon" that can be inflated to reclaim physical pages
412	  by reserving them in the guest and invalidating them in the
413	  monitor, freeing up the underlying machine pages so they can
414	  be allocated to other guests. The balloon can also be deflated
415	  to allow the guest to use more physical memory.
416
417	  If unsure, say N.
418
419	  To compile this driver as a module, choose M here: the
420	  module will be called vmw_balloon.
421
422config PCH_PHUB
423	tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
424	select GENERIC_NET_UTILS
425	depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
426	help
427	  This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
428	  Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
429	  processor. The Topcliff has MAC address and Option ROM data in SROM.
430	  This driver can access MAC address and Option ROM data in SROM.
431
432	  This driver also can be used for LAPIS Semiconductor's IOH,
433	  ML7213/ML7223/ML7831.
434	  ML7213 which is for IVI(In-Vehicle Infotainment) use.
435	  ML7223 IOH is for MP(Media Phone) use.
436	  ML7831 IOH is for general purpose use.
437	  ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
438	  ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
439
440	  To compile this driver as a module, choose M here: the module will
441	  be called pch_phub.
442
443config USB_SWITCH_FSA9480
444	tristate "FSA9480 USB Switch"
445	depends on I2C
446	help
447	  The FSA9480 is a USB port accessory detector and switch.
448	  The FSA9480 is fully controlled using I2C and enables USB data,
449	  stereo and mono audio, video, microphone and UART data to use
450	  a common connector port.
451
452config LATTICE_ECP3_CONFIG
453	tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
454	depends on SPI && SYSFS
455	select FW_LOADER
456	default	n
457	help
458	  This option enables support for bitstream configuration (programming
459	  or loading) of the Lattice ECP3 FPGA family via SPI.
460
461	  If unsure, say N.
462
463config SRAM
464	bool "Generic on-chip SRAM driver"
465	depends on HAS_IOMEM
466	select GENERIC_ALLOCATOR
467	select SRAM_EXEC if ARM
468	help
469	  This driver allows you to declare a memory region to be managed by
470	  the genalloc API. It is supposed to be used for small on-chip SRAM
471	  areas found on many SoCs.
472
473config SRAM_EXEC
474	bool
475
476config VEXPRESS_SYSCFG
477	bool "Versatile Express System Configuration driver"
478	depends on VEXPRESS_CONFIG
479	default y
480	help
481	  ARM Ltd. Versatile Express uses specialised platform configuration
482	  bus. System Configuration interface is one of the possible means
483	  of generating transactions on this bus.
484
485config ASPEED_LPC_CTRL
486	depends on (ARCH_ASPEED || COMPILE_TEST) && REGMAP && MFD_SYSCON
487	tristate "Aspeed ast2400/2500 HOST LPC to BMC bridge control"
488	---help---
489	  Control Aspeed ast2400/2500 HOST LPC to BMC mappings through
490	  ioctl()s, the driver also provides a read/write interface to a BMC ram
491	  region where the host LPC read/write region can be buffered.
492
493config PCI_ENDPOINT_TEST
494	depends on PCI
495	select CRC32
496	tristate "PCI Endpoint Test driver"
497	---help---
498           Enable this configuration option to enable the host side test driver
499           for PCI Endpoint.
500
501source "drivers/misc/c2port/Kconfig"
502source "drivers/misc/eeprom/Kconfig"
503source "drivers/misc/cb710/Kconfig"
504source "drivers/misc/ti-st/Kconfig"
505source "drivers/misc/lis3lv02d/Kconfig"
506source "drivers/misc/altera-stapl/Kconfig"
507source "drivers/misc/mei/Kconfig"
508source "drivers/misc/vmw_vmci/Kconfig"
509source "drivers/misc/mic/Kconfig"
510source "drivers/misc/genwqe/Kconfig"
511source "drivers/misc/echo/Kconfig"
512source "drivers/misc/cxl/Kconfig"
513endmenu
514