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