1#
2# Misc strange devices
3#
4
5# This one has to live outside of the MISC_DEVICES conditional,
6# because it may be selected by drivers/platform/x86/hp_accel.
7config SENSORS_LIS3LV02D
8	tristate
9	depends on INPUT
10	select INPUT_POLLDEV
11	default n
12
13menuconfig MISC_DEVICES
14	bool "Misc devices"
15	---help---
16	  Say Y here to get to see options for device drivers from various
17	  different categories. This option alone does not add any kernel code.
18
19	  If you say N, all options in this submenu will be skipped and disabled.
20
21if MISC_DEVICES
22
23config AD525X_DPOT
24	tristate "Analog Devices Digital Potentiometers"
25	depends on (I2C || SPI) && SYSFS
26	help
27	  If you say yes here, you get support for the Analog Devices
28	  AD5258, AD5259, AD5251, AD5252, AD5253, AD5254, AD5255
29	  AD5160, AD5161, AD5162, AD5165, AD5200, AD5201, AD5203,
30	  AD5204, AD5206, AD5207, AD5231, AD5232, AD5233, AD5235,
31	  AD5260, AD5262, AD5263, AD5290, AD5291, AD5292, AD5293,
32	  AD7376, AD8400, AD8402, AD8403, ADN2850, AD5241, AD5242,
33	  AD5243, AD5245, AD5246, AD5247, AD5248, AD5280, AD5282,
34	  ADN2860, AD5273, AD5171, AD5170, AD5172, AD5173, AD5270,
35	  AD5271, AD5272, AD5274
36	  digital potentiometer chips.
37
38	  See Documentation/misc-devices/ad525x_dpot.txt for the
39	  userspace interface.
40
41	  This driver can also be built as a module.  If so, the module
42	  will be called ad525x_dpot.
43
44config AD525X_DPOT_I2C
45	tristate "support I2C bus connection"
46	depends on AD525X_DPOT && I2C
47	help
48	  Say Y here if you have a digital potentiometers hooked to an I2C bus.
49
50	  To compile this driver as a module, choose M here: the
51	  module will be called ad525x_dpot-i2c.
52
53config AD525X_DPOT_SPI
54	tristate "support SPI bus connection"
55	depends on AD525X_DPOT && SPI_MASTER
56	help
57	  Say Y here if you have a digital potentiometers hooked to an SPI bus.
58
59	  If unsure, say N (but it's safe to say "Y").
60
61	  To compile this driver as a module, choose M here: the
62	  module will be called ad525x_dpot-spi.
63
64config ATMEL_PWM
65	tristate "Atmel AT32/AT91 PWM support"
66	depends on AVR32 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9
67	help
68	  This option enables device driver support for the PWM channels
69	  on certain Atmel processors.  Pulse Width Modulation is used for
70	  purposes including software controlled power-efficient backlights
71	  on LCD displays, motor control, and waveform generation.
72
73config AB8500_PWM
74	bool "AB8500 PWM support"
75	depends on AB8500_CORE && ARCH_U8500
76	select HAVE_PWM
77	help
78	  This driver exports functions to enable/disble/config/free Pulse
79	  Width Modulation in the Analog Baseband Chip AB8500.
80	  It is used by led and backlight driver to control the intensity.
81
82config ATMEL_TCLIB
83	bool "Atmel AT32/AT91 Timer/Counter Library"
84	depends on (AVR32 || ARCH_AT91)
85	help
86	  Select this if you want a library to allocate the Timer/Counter
87	  blocks found on many Atmel processors.  This facilitates using
88	  these blocks by different drivers despite processor differences.
89
90config ATMEL_TCB_CLKSRC
91	bool "TC Block Clocksource"
92	depends on ATMEL_TCLIB
93	default y
94	help
95	  Select this to get a high precision clocksource based on a
96	  TC block with a 5+ MHz base clock rate.  Two timer channels
97	  are combined to make a single 32-bit timer.
98
99	  When GENERIC_CLOCKEVENTS is defined, the third timer channel
100	  may be used as a clock event device supporting oneshot mode
101	  (delays of up to two seconds) based on the 32 KiHz clock.
102
103config ATMEL_TCB_CLKSRC_BLOCK
104	int
105	depends on ATMEL_TCB_CLKSRC
106	prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X
107	default 0
108	range 0 1
109	help
110	  Some chips provide more than one TC block, so you have the
111	  choice of which one to use for the clock framework.  The other
112	  TC can be used for other purposes, such as PWM generation and
113	  interval timing.
114
115config IBM_ASM
116	tristate "Device driver for IBM RSA service processor"
117	depends on X86 && PCI && INPUT && EXPERIMENTAL
118	---help---
119	  This option enables device driver support for in-band access to the
120	  IBM RSA (Condor) service processor in eServer xSeries systems.
121	  The ibmasm device driver allows user space application to access
122	  ASM (Advanced Systems Management) functions on the service
123	  processor. The driver is meant to be used in conjunction with
124	  a user space API.
125	  The ibmasm driver also enables the OS to use the UART on the
126	  service processor board as a regular serial port. To make use of
127	  this feature serial driver support (CONFIG_SERIAL_8250) must be
128	  enabled.
129
130	  WARNING: This software may not be supported or function
131	  correctly on your IBM server. Please consult the IBM ServerProven
132	  website <http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>
133	  for information on the specific driver level and support statement
134	  for your IBM server.
135
136config PHANTOM
137	tristate "Sensable PHANToM (PCI)"
138	depends on PCI
139	help
140	  Say Y here if you want to build a driver for Sensable PHANToM device.
141
142	  This driver is only for PCI PHANToMs.
143
144	  If you choose to build module, its name will be phantom. If unsure,
145	  say N here.
146
147config SGI_IOC4
148	tristate "SGI IOC4 Base IO support"
149	depends on PCI
150	---help---
151	  This option enables basic support for the IOC4 chip on certain
152	  SGI IO controller cards (IO9, IO10, and PCI-RT).  This option
153	  does not enable any specific functions on such a card, but provides
154	  necessary infrastructure for other drivers to utilize.
155
156	  If you have an SGI Altix with an IOC4-based card say Y.
157	  Otherwise say N.
158
159config TIFM_CORE
160	tristate "TI Flash Media interface support (EXPERIMENTAL)"
161	depends on EXPERIMENTAL && PCI
162	help
163	  If you want support for Texas Instruments(R) Flash Media adapters
164	  you should select this option and then also choose an appropriate
165	  host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
166	  support', if you have a TI PCI74xx compatible card reader, for
167	  example.
168	  You will also have to select some flash card format drivers. MMC/SD
169	  cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
170	  Interface support (MMC_TIFM_SD)'.
171
172	  To compile this driver as a module, choose M here: the module will
173	  be called tifm_core.
174
175config TIFM_7XX1
176	tristate "TI Flash Media PCI74xx/PCI76xx host adapter support (EXPERIMENTAL)"
177	depends on PCI && TIFM_CORE && EXPERIMENTAL
178	default TIFM_CORE
179	help
180	  This option enables support for Texas Instruments(R) PCI74xx and
181	  PCI76xx families of Flash Media adapters, found in many laptops.
182	  To make actual use of the device, you will have to select some
183	  flash card format drivers, as outlined in the TIFM_CORE Help.
184
185	  To compile this driver as a module, choose M here: the module will
186	  be called tifm_7xx1.
187
188config ICS932S401
189	tristate "Integrated Circuits ICS932S401"
190	depends on I2C && EXPERIMENTAL
191	help
192	  If you say yes here you get support for the Integrated Circuits
193	  ICS932S401 clock control chips.
194
195	  This driver can also be built as a module. If so, the module
196	  will be called ics932s401.
197
198config ATMEL_SSC
199	tristate "Device driver for Atmel SSC peripheral"
200	depends on AVR32 || ARCH_AT91
201	---help---
202	  This option enables device driver support for Atmel Synchronized
203	  Serial Communication peripheral (SSC).
204
205	  The SSC peripheral supports a wide variety of serial frame based
206	  communications, i.e. I2S, SPI, etc.
207
208	  If unsure, say N.
209
210config ENCLOSURE_SERVICES
211	tristate "Enclosure Services"
212	default n
213	help
214	  Provides support for intelligent enclosures (bays which
215	  contain storage devices).  You also need either a host
216	  driver (SCSI/ATA) which supports enclosures
217	  or a SCSI enclosure device (SES) to use these services.
218
219config SGI_XP
220	tristate "Support communication between SGI SSIs"
221	depends on NET
222	depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
223	select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
224	select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
225	select SGI_GRU if X86_64 && SMP
226	---help---
227	  An SGI machine can be divided into multiple Single System
228	  Images which act independently of each other and have
229	  hardware based memory protection from the others.  Enabling
230	  this feature will allow for direct communication between SSIs
231	  based on a network adapter and DMA messaging.
232
233config CS5535_MFGPT
234	tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
235	depends on PCI
236	depends on X86
237	default n
238	help
239	  This driver provides access to MFGPT functionality for other
240	  drivers that need timers.  MFGPTs are available in the CS5535 and
241	  CS5536 companion chips that are found in AMD Geode and several
242	  other platforms.  They have a better resolution and max interval
243	  than the generic PIT, and are suitable for use as high-res timers.
244	  You probably don't want to enable this manually; other drivers that
245	  make use of it should enable it.
246
247config CS5535_MFGPT_DEFAULT_IRQ
248	int
249	depends on CS5535_MFGPT
250	default 7
251	help
252	  MFGPTs on the CS5535 require an interrupt.  The selected IRQ
253	  can be overridden as a module option as well as by driver that
254	  use the cs5535_mfgpt_ API; however, different architectures might
255	  want to use a different IRQ by default.  This is here for
256	  architectures to set as necessary.
257
258config CS5535_CLOCK_EVENT_SRC
259	tristate "CS5535/CS5536 high-res timer (MFGPT) events"
260	depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
261	help
262	  This driver provides a clock event source based on the MFGPT
263	  timer(s) in the CS5535 and CS5536 companion chips.
264	  MFGPTs have a better resolution and max interval than the
265	  generic PIT, and are suitable for use as high-res timers.
266
267config HP_ILO
268	tristate "Channel interface driver for the HP iLO processor"
269	depends on PCI
270	default n
271	help
272	  The channel interface driver allows applications to communicate
273	  with iLO management processors present on HP ProLiant servers.
274	  Upon loading, the driver creates /dev/hpilo/dXccbN files, which
275	  can be used to gather data from the management processor, via
276	  read and write system calls.
277
278	  To compile this driver as a module, choose M here: the
279	  module will be called hpilo.
280
281config SGI_GRU
282	tristate "SGI GRU driver"
283	depends on X86_UV && SMP
284	default n
285	select MMU_NOTIFIER
286	---help---
287	The GRU is a hardware resource located in the system chipset. The GRU
288	contains memory that can be mmapped into the user address space. This memory is
289	used to communicate with the GRU to perform functions such as load/store,
290	scatter/gather, bcopy, AMOs, etc.  The GRU is directly accessed by user
291	instructions using user virtual addresses. GRU instructions (ex., bcopy) use
292	user virtual addresses for operands.
293
294	If you are not running on a SGI UV system, say N.
295
296config SGI_GRU_DEBUG
297	bool  "SGI GRU driver debug"
298	depends on SGI_GRU
299	default n
300	---help---
301	This option enables addition debugging code for the SGI GRU driver. If
302	you are unsure, say N.
303
304config APDS9802ALS
305	tristate "Medfield Avago APDS9802 ALS Sensor module"
306	depends on I2C
307	help
308	  If you say yes here you get support for the ALS APDS9802 ambient
309	  light sensor.
310
311	  This driver can also be built as a module.  If so, the module
312	  will be called apds9802als.
313
314config ISL29003
315	tristate "Intersil ISL29003 ambient light sensor"
316	depends on I2C && SYSFS
317	help
318	  If you say yes here you get support for the Intersil ISL29003
319	  ambient light sensor.
320
321	  This driver can also be built as a module.  If so, the module
322	  will be called isl29003.
323
324config ISL29020
325	tristate "Intersil ISL29020 ambient light sensor"
326	depends on I2C
327	help
328	  If you say yes here you get support for the Intersil ISL29020
329	  ambient light sensor.
330
331	  This driver can also be built as a module.  If so, the module
332	  will be called isl29020.
333
334config SENSORS_TSL2550
335	tristate "Taos TSL2550 ambient light sensor"
336	depends on I2C && SYSFS
337	help
338	  If you say yes here you get support for the Taos TSL2550
339	  ambient light sensor.
340
341	  This driver can also be built as a module.  If so, the module
342	  will be called tsl2550.
343
344config SENSORS_BH1780
345	tristate "ROHM BH1780GLI ambient light sensor"
346	depends on I2C && SYSFS
347	help
348	  If you say yes here you get support for the ROHM BH1780GLI
349	  ambient light sensor.
350
351	  This driver can also be built as a module.  If so, the module
352	  will be called bh1780gli.
353
354config SENSORS_BH1770
355         tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
356         depends on I2C
357         ---help---
358           Say Y here if you want to build a driver for BH1770GLC (ROHM) or
359	   SFH7770 (Osram) combined ambient light and proximity sensor chip.
360
361           To compile this driver as a module, choose M here: the
362           module will be called bh1770glc. If unsure, say N here.
363
364config SENSORS_APDS990X
365	 tristate "APDS990X combined als and proximity sensors"
366	 depends on I2C
367	 default n
368	 ---help---
369	   Say Y here if you want to build a driver for Avago APDS990x
370	   combined ambient light and proximity sensor chip.
371
372	   To compile this driver as a module, choose M here: the
373	   module will be called apds990x. If unsure, say N here.
374
375config HMC6352
376	tristate "Honeywell HMC6352 compass"
377	depends on I2C
378	help
379	  This driver provides support for the Honeywell HMC6352 compass,
380	  providing configuration and heading data via sysfs.
381
382config EP93XX_PWM
383	tristate "EP93xx PWM support"
384	depends on ARCH_EP93XX
385	help
386	  This option enables device driver support for the PWM channels
387	  on the Cirrus EP93xx processors.  The EP9307 chip only has one
388	  PWM channel all the others have two, the second channel is an
389	  alternate function of the EGPIO14 pin.  A sysfs interface is
390	  provided to control the PWM channels.
391
392	  To compile this driver as a module, choose M here: the module will
393	  be called ep93xx_pwm.
394
395config DS1682
396	tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
397	depends on I2C && EXPERIMENTAL
398	help
399	  If you say yes here you get support for Dallas Semiconductor
400	  DS1682 Total Elapsed Time Recorder.
401
402	  This driver can also be built as a module.  If so, the module
403	  will be called ds1682.
404
405config SPEAR13XX_PCIE_GADGET
406	bool "PCIe gadget support for SPEAr13XX platform"
407	depends on ARCH_SPEAR13XX
408	default n
409	help
410	 This option enables gadget support for PCIe controller. If
411	 board file defines any controller as PCIe endpoint then a sysfs
412	 entry will be created for that controller. User can use these
413	 sysfs node to configure PCIe EP as per his requirements.
414
415config TI_DAC7512
416	tristate "Texas Instruments DAC7512"
417	depends on SPI && SYSFS
418	help
419	  If you say yes here you get support for the Texas Instruments
420	  DAC7512 16-bit digital-to-analog converter.
421
422	  This driver can also be built as a module. If so, the module
423	  will be called ti_dac7512.
424
425config VMWARE_BALLOON
426	tristate "VMware Balloon Driver"
427	depends on X86
428	help
429	  This is VMware physical memory management driver which acts
430	  like a "balloon" that can be inflated to reclaim physical pages
431	  by reserving them in the guest and invalidating them in the
432	  monitor, freeing up the underlying machine pages so they can
433	  be allocated to other guests. The balloon can also be deflated
434	  to allow the guest to use more physical memory.
435
436	  If unsure, say N.
437
438	  To compile this driver as a module, choose M here: the
439	  module will be called vmw_balloon.
440
441config ARM_CHARLCD
442	bool "ARM Ltd. Character LCD Driver"
443	depends on PLAT_VERSATILE
444	help
445	  This is a driver for the character LCD found on the ARM Ltd.
446	  Versatile and RealView Platform Baseboards. It doesn't do
447	  very much more than display the text "ARM Linux" on the first
448	  line and the Linux version on the second line, but that's
449	  still useful.
450
451config BMP085
452	tristate "BMP085 digital pressure sensor"
453	depends on I2C && SYSFS
454	help
455	  If you say yes here you get support for the Bosch Sensortec
456	  BMP085 digital pressure sensor.
457
458	  To compile this driver as a module, choose M here: the
459	  module will be called bmp085.
460
461config PCH_PHUB
462	tristate "PCH Packet Hub of Intel Topcliff / OKI SEMICONDUCTOR ML7213"
463	depends on PCI
464	help
465	  This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
466	  Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
467	  processor. The Topcliff has MAC address and Option ROM data in SROM.
468	  This driver can access MAC address and Option ROM data in SROM.
469
470	  This driver also can be used for OKI SEMICONDUCTOR's ML7213 which is
471	  for IVI(In-Vehicle Infotainment) use.
472	  ML7213 is companion chip for Intel Atom E6xx series.
473	  ML7213 is completely compatible for Intel EG20T PCH.
474
475	  To compile this driver as a module, choose M here: the module will
476	  be called pch_phub.
477
478source "drivers/misc/c2port/Kconfig"
479source "drivers/misc/eeprom/Kconfig"
480source "drivers/misc/cb710/Kconfig"
481source "drivers/misc/iwmc3200top/Kconfig"
482source "drivers/misc/ti-st/Kconfig"
483source "drivers/misc/lis3lv02d/Kconfig"
484
485endif # MISC_DEVICES
486