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 AD525x Digital Potentiometers"
18 depends on I2C && SYSFS
20 If you say yes here, you get support for the Analog Devices
21 AD5258, AD5259, AD5251, AD5252, AD5253, AD5254 and AD5255
22 digital potentiometer chips.
24 See Documentation/misc-devices/ad525x_dpot.txt for the
27 This driver can also be built as a module. If so, the module
28 will be called ad525x_dpot.
31 tristate "Atmel AT32/AT91 PWM support"
32 depends on AVR32 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9
34 This option enables device driver support for the PWM channels
35 on certain Atmel processors. Pulse Width Modulation is used for
36 purposes including software controlled power-efficient backlights
37 on LCD displays, motor control, and waveform generation.
40 bool "Atmel AT32/AT91 Timer/Counter Library"
41 depends on (AVR32 || ARCH_AT91)
43 Select this if you want a library to allocate the Timer/Counter
44 blocks found on many Atmel processors. This facilitates using
45 these blocks by different drivers despite processor differences.
47 config ATMEL_TCB_CLKSRC
48 bool "TC Block Clocksource"
49 depends on ATMEL_TCLIB && GENERIC_TIME
52 Select this to get a high precision clocksource based on a
53 TC block with a 5+ MHz base clock rate. Two timer channels
54 are combined to make a single 32-bit timer.
56 When GENERIC_CLOCKEVENTS is defined, the third timer channel
57 may be used as a clock event device supporting oneshot mode
58 (delays of up to two seconds) based on the 32 KiHz clock.
60 config ATMEL_TCB_CLKSRC_BLOCK
62 depends on ATMEL_TCB_CLKSRC
63 prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X
67 Some chips provide more than one TC block, so you have the
68 choice of which one to use for the clock framework. The other
69 TC can be used for other purposes, such as PWM generation and
73 tristate "Device driver for IBM RSA service processor"
74 depends on X86 && PCI && INPUT && EXPERIMENTAL
76 This option enables device driver support for in-band access to the
77 IBM RSA (Condor) service processor in eServer xSeries systems.
78 The ibmasm device driver allows user space application to access
79 ASM (Advanced Systems Management) functions on the service
80 processor. The driver is meant to be used in conjunction with
82 The ibmasm driver also enables the OS to use the UART on the
83 service processor board as a regular serial port. To make use of
84 this feature serial driver support (CONFIG_SERIAL_8250) must be
87 WARNING: This software may not be supported or function
88 correctly on your IBM server. Please consult the IBM ServerProven
89 website <http://www.pc.ibm.com/ww/eserver/xseries/serverproven> for
90 information on the specific driver level and support statement
94 tristate "Sensable PHANToM (PCI)"
97 Say Y here if you want to build a driver for Sensable PHANToM device.
99 This driver is only for PCI PHANToMs.
101 If you choose to build module, its name will be phantom. If unsure,
105 tristate "SGI IOC4 Base IO support"
108 This option enables basic support for the IOC4 chip on certain
109 SGI IO controller cards (IO9, IO10, and PCI-RT). This option
110 does not enable any specific functions on such a card, but provides
111 necessary infrastructure for other drivers to utilize.
113 If you have an SGI Altix with an IOC4-based card say Y.
117 tristate "TI Flash Media interface support (EXPERIMENTAL)"
118 depends on EXPERIMENTAL && PCI
120 If you want support for Texas Instruments(R) Flash Media adapters
121 you should select this option and then also choose an appropriate
122 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
123 support', if you have a TI PCI74xx compatible card reader, for
125 You will also have to select some flash card format drivers. MMC/SD
126 cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
127 Interface support (MMC_TIFM_SD)'.
129 To compile this driver as a module, choose M here: the module will
133 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support (EXPERIMENTAL)"
134 depends on PCI && TIFM_CORE && EXPERIMENTAL
137 This option enables support for Texas Instruments(R) PCI74xx and
138 PCI76xx families of Flash Media adapters, found in many laptops.
139 To make actual use of the device, you will have to select some
140 flash card format drivers, as outlined in the TIFM_CORE Help.
142 To compile this driver as a module, choose M here: the module will
146 tristate "Integrated Circuits ICS932S401"
147 depends on I2C && EXPERIMENTAL
149 If you say yes here you get support for the Integrated Circuits
150 ICS932S401 clock control chips.
152 This driver can also be built as a module. If so, the module
153 will be called ics932s401.
156 tristate "Device driver for Atmel SSC peripheral"
157 depends on AVR32 || ARCH_AT91
159 This option enables device driver support for Atmel Synchronized
160 Serial Communication peripheral (SSC).
162 The SSC peripheral supports a wide variety of serial frame based
163 communications, i.e. I2S, SPI, etc.
167 config ENCLOSURE_SERVICES
168 tristate "Enclosure Services"
171 Provides support for intelligent enclosures (bays which
172 contain storage devices). You also need either a host
173 driver (SCSI/ATA) which supports enclosures
174 or a SCSI enclosure device (SES) to use these services.
177 tristate "Support communication between SGI SSIs"
179 depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
180 select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
181 select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
182 select SGI_GRU if X86_64 && SMP
184 An SGI machine can be divided into multiple Single System
185 Images which act independently of each other and have
186 hardware based memory protection from the others. Enabling
187 this feature will allow for direct communication between SSIs
188 based on a network adapter and DMA messaging.
191 tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
196 This driver provides access to MFGPT functionality for other
197 drivers that need timers. MFGPTs are available in the CS5535 and
198 CS5536 companion chips that are found in AMD Geode and several
199 other platforms. They have a better resolution and max interval
200 than the generic PIT, and are suitable for use as high-res timers.
201 You probably don't want to enable this manually; other drivers that
202 make use of it should enable it.
204 config CS5535_MFGPT_DEFAULT_IRQ
206 depends on CS5535_MFGPT
209 MFGPTs on the CS5535 require an interrupt. The selected IRQ
210 can be overridden as a module option as well as by driver that
211 use the cs5535_mfgpt_ API; however, different architectures might
212 want to use a different IRQ by default. This is here for
213 architectures to set as necessary.
215 config CS5535_CLOCK_EVENT_SRC
216 tristate "CS5535/CS5536 high-res timer (MFGPT) events"
217 depends on GENERIC_TIME && GENERIC_CLOCKEVENTS && CS5535_MFGPT
219 This driver provides a clock event source based on the MFGPT
220 timer(s) in the CS5535 and CS5536 companion chips.
221 MFGPTs have a better resolution and max interval than the
222 generic PIT, and are suitable for use as high-res timers.
225 tristate "Channel interface driver for HP iLO/iLO2 processor"
229 The channel interface driver allows applications to communicate
230 with iLO/iLO2 management processors present on HP ProLiant
231 servers. Upon loading, the driver creates /dev/hpilo/dXccbN files,
232 which can be used to gather data from the management processor,
233 via read and write system calls.
235 To compile this driver as a module, choose M here: the
236 module will be called hpilo.
239 tristate "SGI GRU driver"
240 depends on X86_UV && SMP
244 The GRU is a hardware resource located in the system chipset. The GRU
245 contains memory that can be mmapped into the user address space. This memory is
246 used to communicate with the GRU to perform functions such as load/store,
247 scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
248 instructions using user virtual addresses. GRU instructions (ex., bcopy) use
249 user virtual addresses for operands.
251 If you are not running on a SGI UV system, say N.
254 bool "SGI GRU driver debug"
258 This option enables addition debugging code for the SGI GRU driver. If
259 you are unsure, say N.
262 tristate "Intersil ISL29003 ambient light sensor"
263 depends on I2C && SYSFS
265 If you say yes here you get support for the Intersil ISL29003
266 ambient light sensor.
268 This driver can also be built as a module. If so, the module
269 will be called isl29003.
271 config SENSORS_TSL2550
272 tristate "Taos TSL2550 ambient light sensor"
273 depends on I2C && SYSFS
275 If you say yes here you get support for the Taos TSL2550
276 ambient light sensor.
278 This driver can also be built as a module. If so, the module
279 will be called tsl2550.
282 tristate "EP93xx PWM support"
283 depends on ARCH_EP93XX
285 This option enables device driver support for the PWM channels
286 on the Cirrus EP93xx processors. The EP9307 chip only has one
287 PWM channel all the others have two, the second channel is an
288 alternate function of the EGPIO14 pin. A sysfs interface is
289 provided to control the PWM channels.
291 To compile this driver as a module, choose M here: the module will
292 be called ep93xx_pwm.
295 tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
296 depends on I2C && EXPERIMENTAL
298 If you say yes here you get support for Dallas Semiconductor
299 DS1682 Total Elapsed Time Recorder.
301 This driver can also be built as a module. If so, the module
302 will be called ds1682.
305 tristate "Texas Instruments DAC7512"
306 depends on SPI && SYSFS
308 If you say yes here you get support for the Texas Instruments
309 DAC7512 16-bit digital-to-analog converter.
311 This driver can also be built as a module. If so, the module
312 will be calles ti_dac7512.
314 config VMWARE_BALLOON
315 tristate "VMware Balloon Driver"
318 This is VMware physical memory management driver which acts
319 like a "balloon" that can be inflated to reclaim physical pages
320 by reserving them in the guest and invalidating them in the
321 monitor, freeing up the underlying machine pages so they can
322 be allocated to other guests. The balloon can also be deflated
323 to allow the guest to use more physical memory.
327 To compile this driver as a module, choose M here: the
328 module will be called vmware_balloon.
330 source "drivers/misc/c2port/Kconfig"
331 source "drivers/misc/eeprom/Kconfig"
332 source "drivers/misc/cb710/Kconfig"
333 source "drivers/misc/iwmc3200top/Kconfig"