xref: /openbmc/linux/drivers/misc/Kconfig (revision d0b73b48)
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 IBM_ASM
97	tristate "Device driver for IBM RSA service processor"
98	depends on X86 && PCI && INPUT
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
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 AVR32 || ARCH_AT91
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 PCI && X86 && 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 SGI_GRU
276	tristate "SGI GRU driver"
277	depends on X86_UV && SMP
278	default n
279	select MMU_NOTIFIER
280	---help---
281	The GRU is a hardware resource located in the system chipset. The GRU
282	contains memory that can be mmapped into the user address space. This memory is
283	used to communicate with the GRU to perform functions such as load/store,
284	scatter/gather, bcopy, AMOs, etc.  The GRU is directly accessed by user
285	instructions using user virtual addresses. GRU instructions (ex., bcopy) use
286	user virtual addresses for operands.
287
288	If you are not running on a SGI UV system, say N.
289
290config SGI_GRU_DEBUG
291	bool  "SGI GRU driver debug"
292	depends on SGI_GRU
293	default n
294	---help---
295	This option enables addition debugging code for the SGI GRU driver. If
296	you are unsure, say N.
297
298config APDS9802ALS
299	tristate "Medfield Avago APDS9802 ALS Sensor module"
300	depends on I2C
301	help
302	  If you say yes here you get support for the ALS APDS9802 ambient
303	  light sensor.
304
305	  This driver can also be built as a module.  If so, the module
306	  will be called apds9802als.
307
308config ISL29003
309	tristate "Intersil ISL29003 ambient light sensor"
310	depends on I2C && SYSFS
311	help
312	  If you say yes here you get support for the Intersil ISL29003
313	  ambient light sensor.
314
315	  This driver can also be built as a module.  If so, the module
316	  will be called isl29003.
317
318config ISL29020
319	tristate "Intersil ISL29020 ambient light sensor"
320	depends on I2C
321	help
322	  If you say yes here you get support for the Intersil ISL29020
323	  ambient light sensor.
324
325	  This driver can also be built as a module.  If so, the module
326	  will be called isl29020.
327
328config SENSORS_TSL2550
329	tristate "Taos TSL2550 ambient light sensor"
330	depends on I2C && SYSFS
331	help
332	  If you say yes here you get support for the Taos TSL2550
333	  ambient light sensor.
334
335	  This driver can also be built as a module.  If so, the module
336	  will be called tsl2550.
337
338config SENSORS_BH1780
339	tristate "ROHM BH1780GLI ambient light sensor"
340	depends on I2C && SYSFS
341	help
342	  If you say yes here you get support for the ROHM BH1780GLI
343	  ambient light sensor.
344
345	  This driver can also be built as a module.  If so, the module
346	  will be called bh1780gli.
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 EP93XX_PWM
377	tristate "EP93xx PWM support"
378	depends on ARCH_EP93XX
379	help
380	  This option enables device driver support for the PWM channels
381	  on the Cirrus EP93xx processors.  The EP9307 chip only has one
382	  PWM channel all the others have two, the second channel is an
383	  alternate function of the EGPIO14 pin.  A sysfs interface is
384	  provided to control the PWM channels.
385
386	  To compile this driver as a module, choose M here: the module will
387	  be called ep93xx_pwm.
388
389config DS1682
390	tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
391	depends on I2C
392	help
393	  If you say yes here you get support for Dallas Semiconductor
394	  DS1682 Total Elapsed Time Recorder.
395
396	  This driver can also be built as a module.  If so, the module
397	  will be called ds1682.
398
399config SPEAR13XX_PCIE_GADGET
400	bool "PCIe gadget support for SPEAr13XX platform"
401	depends on ARCH_SPEAR13XX
402	default n
403	help
404	 This option enables gadget support for PCIe controller. If
405	 board file defines any controller as PCIe endpoint then a sysfs
406	 entry will be created for that controller. User can use these
407	 sysfs node to configure PCIe EP as per his requirements.
408
409config TI_DAC7512
410	tristate "Texas Instruments DAC7512"
411	depends on SPI && SYSFS
412	help
413	  If you say yes here you get support for the Texas Instruments
414	  DAC7512 16-bit digital-to-analog converter.
415
416	  This driver can also be built as a module. If so, the module
417	  will be called ti_dac7512.
418
419config VMWARE_BALLOON
420	tristate "VMware Balloon Driver"
421	depends on X86
422	help
423	  This is VMware physical memory management driver which acts
424	  like a "balloon" that can be inflated to reclaim physical pages
425	  by reserving them in the guest and invalidating them in the
426	  monitor, freeing up the underlying machine pages so they can
427	  be allocated to other guests. The balloon can also be deflated
428	  to allow the guest to use more physical memory.
429
430	  If unsure, say N.
431
432	  To compile this driver as a module, choose M here: the
433	  module will be called vmw_balloon.
434
435config ARM_CHARLCD
436	bool "ARM Ltd. Character LCD Driver"
437	depends on PLAT_VERSATILE
438	help
439	  This is a driver for the character LCD found on the ARM Ltd.
440	  Versatile and RealView Platform Baseboards. It doesn't do
441	  very much more than display the text "ARM Linux" on the first
442	  line and the Linux version on the second line, but that's
443	  still useful.
444
445config BMP085
446	bool
447	depends on SYSFS
448
449config BMP085_I2C
450	tristate "BMP085 digital pressure sensor on I2C"
451	select BMP085
452	select REGMAP_I2C
453	depends on I2C && SYSFS
454	help
455	  Say Y here if you want to support Bosch Sensortec's digital pressure
456	  sensor hooked to an I2C bus.
457
458	  To compile this driver as a module, choose M here: the
459	  module will be called bmp085-i2c.
460
461config BMP085_SPI
462	tristate "BMP085 digital pressure sensor on SPI"
463	select BMP085
464	select REGMAP_SPI
465	depends on SPI_MASTER && SYSFS
466	help
467	  Say Y here if you want to support Bosch Sensortec's digital pressure
468	  sensor hooked to an SPI bus.
469
470	  To compile this driver as a module, choose M here: the
471	  module will be called bmp085-spi.
472
473config PCH_PHUB
474	tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
475	depends on PCI
476	help
477	  This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
478	  Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
479	  processor. The Topcliff has MAC address and Option ROM data in SROM.
480	  This driver can access MAC address and Option ROM data in SROM.
481
482	  This driver also can be used for LAPIS Semiconductor's IOH,
483	  ML7213/ML7223/ML7831.
484	  ML7213 which is for IVI(In-Vehicle Infotainment) use.
485	  ML7223 IOH is for MP(Media Phone) use.
486	  ML7831 IOH is for general purpose use.
487	  ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
488	  ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
489
490	  To compile this driver as a module, choose M here: the module will
491	  be called pch_phub.
492
493config USB_SWITCH_FSA9480
494	tristate "FSA9480 USB Switch"
495	depends on I2C
496	help
497	  The FSA9480 is a USB port accessory detector and switch.
498	  The FSA9480 is fully controlled using I2C and enables USB data,
499	  stereo and mono audio, video, microphone and UART data to use
500	  a common connector port.
501
502source "drivers/misc/c2port/Kconfig"
503source "drivers/misc/eeprom/Kconfig"
504source "drivers/misc/cb710/Kconfig"
505source "drivers/misc/ti-st/Kconfig"
506source "drivers/misc/lis3lv02d/Kconfig"
507source "drivers/misc/carma/Kconfig"
508source "drivers/misc/altera-stapl/Kconfig"
509source "drivers/misc/mei/Kconfig"
510endmenu
511