5 menuconfig MISC_DEVICES
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.
12 If you say N, all options in this submenu will be skipped and disabled.
17 tristate "Analog Devices Digital Potentiometers"
18 depends on (I2C || SPI) && SYSFS
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
26 digital potentiometer chips.
28 See Documentation/misc-devices/ad525x_dpot.txt for the
31 This driver can also be built as a module. If so, the module
32 will be called ad525x_dpot.
34 config AD525X_DPOT_I2C
35 tristate "support I2C bus connection"
36 depends on AD525X_DPOT && I2C
38 Say Y here if you have a digital potentiometers hooked to an I2C bus.
40 To compile this driver as a module, choose M here: the
41 module will be called ad525x_dpot-i2c.
43 config AD525X_DPOT_SPI
44 tristate "support SPI bus connection"
45 depends on AD525X_DPOT && SPI_MASTER
47 Say Y here if you have a digital potentiometers hooked to an SPI bus.
49 If unsure, say N (but it's safe to say "Y").
51 To compile this driver as a module, choose M here: the
52 module will be called ad525x_dpot-spi.
55 tristate "Atmel AT32/AT91 PWM support"
56 depends on AVR32 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9
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.
64 bool "Atmel AT32/AT91 Timer/Counter Library"
65 depends on (AVR32 || ARCH_AT91)
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.
71 config ATMEL_TCB_CLKSRC
72 bool "TC Block Clocksource"
73 depends on ATMEL_TCLIB && GENERIC_TIME
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.
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.
84 config ATMEL_TCB_CLKSRC_BLOCK
86 depends on ATMEL_TCB_CLKSRC
87 prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X
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
97 tristate "Device driver for IBM RSA service processor"
98 depends on X86 && PCI && INPUT && EXPERIMENTAL
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
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
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.pc.ibm.com/ww/eserver/xseries/serverproven> for
114 information on the specific driver level and support statement
118 tristate "Sensable PHANToM (PCI)"
121 Say Y here if you want to build a driver for Sensable PHANToM device.
123 This driver is only for PCI PHANToMs.
125 If you choose to build module, its name will be phantom. If unsure,
129 tristate "SGI IOC4 Base IO support"
132 This option enables basic support for the IOC4 chip on certain
133 SGI IO controller cards (IO9, IO10, and PCI-RT). This option
134 does not enable any specific functions on such a card, but provides
135 necessary infrastructure for other drivers to utilize.
137 If you have an SGI Altix with an IOC4-based card say Y.
141 tristate "TI Flash Media interface support (EXPERIMENTAL)"
142 depends on EXPERIMENTAL && PCI
144 If you want support for Texas Instruments(R) Flash Media adapters
145 you should select this option and then also choose an appropriate
146 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
147 support', if you have a TI PCI74xx compatible card reader, for
149 You will also have to select some flash card format drivers. MMC/SD
150 cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
151 Interface support (MMC_TIFM_SD)'.
153 To compile this driver as a module, choose M here: the module will
157 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support (EXPERIMENTAL)"
158 depends on PCI && TIFM_CORE && EXPERIMENTAL
161 This option enables support for Texas Instruments(R) PCI74xx and
162 PCI76xx families of Flash Media adapters, found in many laptops.
163 To make actual use of the device, you will have to select some
164 flash card format drivers, as outlined in the TIFM_CORE Help.
166 To compile this driver as a module, choose M here: the module will
170 tristate "Integrated Circuits ICS932S401"
171 depends on I2C && EXPERIMENTAL
173 If you say yes here you get support for the Integrated Circuits
174 ICS932S401 clock control chips.
176 This driver can also be built as a module. If so, the module
177 will be called ics932s401.
180 tristate "Device driver for Atmel SSC peripheral"
181 depends on AVR32 || ARCH_AT91
183 This option enables device driver support for Atmel Synchronized
184 Serial Communication peripheral (SSC).
186 The SSC peripheral supports a wide variety of serial frame based
187 communications, i.e. I2S, SPI, etc.
191 config ENCLOSURE_SERVICES
192 tristate "Enclosure Services"
195 Provides support for intelligent enclosures (bays which
196 contain storage devices). You also need either a host
197 driver (SCSI/ATA) which supports enclosures
198 or a SCSI enclosure device (SES) to use these services.
201 tristate "Support communication between SGI SSIs"
203 depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
204 select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
205 select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
206 select SGI_GRU if X86_64 && SMP
208 An SGI machine can be divided into multiple Single System
209 Images which act independently of each other and have
210 hardware based memory protection from the others. Enabling
211 this feature will allow for direct communication between SSIs
212 based on a network adapter and DMA messaging.
215 tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
220 This driver provides access to MFGPT functionality for other
221 drivers that need timers. MFGPTs are available in the CS5535 and
222 CS5536 companion chips that are found in AMD Geode and several
223 other platforms. They have a better resolution and max interval
224 than the generic PIT, and are suitable for use as high-res timers.
225 You probably don't want to enable this manually; other drivers that
226 make use of it should enable it.
228 config CS5535_MFGPT_DEFAULT_IRQ
230 depends on CS5535_MFGPT
233 MFGPTs on the CS5535 require an interrupt. The selected IRQ
234 can be overridden as a module option as well as by driver that
235 use the cs5535_mfgpt_ API; however, different architectures might
236 want to use a different IRQ by default. This is here for
237 architectures to set as necessary.
239 config CS5535_CLOCK_EVENT_SRC
240 tristate "CS5535/CS5536 high-res timer (MFGPT) events"
241 depends on GENERIC_TIME && GENERIC_CLOCKEVENTS && CS5535_MFGPT
243 This driver provides a clock event source based on the MFGPT
244 timer(s) in the CS5535 and CS5536 companion chips.
245 MFGPTs have a better resolution and max interval than the
246 generic PIT, and are suitable for use as high-res timers.
249 tristate "Channel interface driver for HP iLO/iLO2 processor"
253 The channel interface driver allows applications to communicate
254 with iLO/iLO2 management processors present on HP ProLiant
255 servers. Upon loading, the driver creates /dev/hpilo/dXccbN files,
256 which can be used to gather data from the management processor,
257 via read and write system calls.
259 To compile this driver as a module, choose M here: the
260 module will be called hpilo.
263 tristate "SGI GRU driver"
264 depends on X86_UV && SMP
268 The GRU is a hardware resource located in the system chipset. The GRU
269 contains memory that can be mmapped into the user address space. This memory is
270 used to communicate with the GRU to perform functions such as load/store,
271 scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
272 instructions using user virtual addresses. GRU instructions (ex., bcopy) use
273 user virtual addresses for operands.
275 If you are not running on a SGI UV system, say N.
278 bool "SGI GRU driver debug"
282 This option enables addition debugging code for the SGI GRU driver. If
283 you are unsure, say N.
286 tristate "Intersil ISL29003 ambient light sensor"
287 depends on I2C && SYSFS
289 If you say yes here you get support for the Intersil ISL29003
290 ambient light sensor.
292 This driver can also be built as a module. If so, the module
293 will be called isl29003.
295 config SENSORS_TSL2550
296 tristate "Taos TSL2550 ambient light sensor"
297 depends on I2C && SYSFS
299 If you say yes here you get support for the Taos TSL2550
300 ambient light sensor.
302 This driver can also be built as a module. If so, the module
303 will be called tsl2550.
306 tristate "EP93xx PWM support"
307 depends on ARCH_EP93XX
309 This option enables device driver support for the PWM channels
310 on the Cirrus EP93xx processors. The EP9307 chip only has one
311 PWM channel all the others have two, the second channel is an
312 alternate function of the EGPIO14 pin. A sysfs interface is
313 provided to control the PWM channels.
315 To compile this driver as a module, choose M here: the module will
316 be called ep93xx_pwm.
319 tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
320 depends on I2C && EXPERIMENTAL
322 If you say yes here you get support for Dallas Semiconductor
323 DS1682 Total Elapsed Time Recorder.
325 This driver can also be built as a module. If so, the module
326 will be called ds1682.
329 tristate "Texas Instruments DAC7512"
330 depends on SPI && SYSFS
332 If you say yes here you get support for the Texas Instruments
333 DAC7512 16-bit digital-to-analog converter.
335 This driver can also be built as a module. If so, the module
336 will be calles ti_dac7512.
338 config VMWARE_BALLOON
339 tristate "VMware Balloon Driver"
342 This is VMware physical memory management driver which acts
343 like a "balloon" that can be inflated to reclaim physical pages
344 by reserving them in the guest and invalidating them in the
345 monitor, freeing up the underlying machine pages so they can
346 be allocated to other guests. The balloon can also be deflated
347 to allow the guest to use more physical memory.
351 To compile this driver as a module, choose M here: the
352 module will be called vmware_balloon.
354 source "drivers/misc/c2port/Kconfig"
355 source "drivers/misc/eeprom/Kconfig"
356 source "drivers/misc/cb710/Kconfig"
357 source "drivers/misc/iwmc3200top/Kconfig"