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, AD5241, AD5242,
26 AD5243, AD5245, AD5246, AD5247, AD5248
27 digital potentiometer chips.
29 See Documentation/misc-devices/ad525x_dpot.txt for the
32 This driver can also be built as a module. If so, the module
33 will be called ad525x_dpot.
35 config AD525X_DPOT_I2C
36 tristate "support I2C bus connection"
37 depends on AD525X_DPOT && I2C
39 Say Y here if you have a digital potentiometers hooked to an I2C bus.
41 To compile this driver as a module, choose M here: the
42 module will be called ad525x_dpot-i2c.
44 config AD525X_DPOT_SPI
45 tristate "support SPI bus connection"
46 depends on AD525X_DPOT && SPI_MASTER
48 Say Y here if you have a digital potentiometers hooked to an SPI bus.
50 If unsure, say N (but it's safe to say "Y").
52 To compile this driver as a module, choose M here: the
53 module will be called ad525x_dpot-spi.
56 tristate "Atmel AT32/AT91 PWM support"
57 depends on AVR32 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9
59 This option enables device driver support for the PWM channels
60 on certain Atmel processors. Pulse Width Modulation is used for
61 purposes including software controlled power-efficient backlights
62 on LCD displays, motor control, and waveform generation.
65 bool "Atmel AT32/AT91 Timer/Counter Library"
66 depends on (AVR32 || ARCH_AT91)
68 Select this if you want a library to allocate the Timer/Counter
69 blocks found on many Atmel processors. This facilitates using
70 these blocks by different drivers despite processor differences.
72 config ATMEL_TCB_CLKSRC
73 bool "TC Block Clocksource"
74 depends on ATMEL_TCLIB && GENERIC_TIME
77 Select this to get a high precision clocksource based on a
78 TC block with a 5+ MHz base clock rate. Two timer channels
79 are combined to make a single 32-bit timer.
81 When GENERIC_CLOCKEVENTS is defined, the third timer channel
82 may be used as a clock event device supporting oneshot mode
83 (delays of up to two seconds) based on the 32 KiHz clock.
85 config ATMEL_TCB_CLKSRC_BLOCK
87 depends on ATMEL_TCB_CLKSRC
88 prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X
92 Some chips provide more than one TC block, so you have the
93 choice of which one to use for the clock framework. The other
94 TC can be used for other purposes, such as PWM generation and
98 tristate "Device driver for IBM RSA service processor"
99 depends on X86 && PCI && INPUT && EXPERIMENTAL
101 This option enables device driver support for in-band access to the
102 IBM RSA (Condor) service processor in eServer xSeries systems.
103 The ibmasm device driver allows user space application to access
104 ASM (Advanced Systems Management) functions on the service
105 processor. The driver is meant to be used in conjunction with
107 The ibmasm driver also enables the OS to use the UART on the
108 service processor board as a regular serial port. To make use of
109 this feature serial driver support (CONFIG_SERIAL_8250) must be
112 WARNING: This software may not be supported or function
113 correctly on your IBM server. Please consult the IBM ServerProven
114 website <http://www.pc.ibm.com/ww/eserver/xseries/serverproven> for
115 information on the specific driver level and support statement
119 tristate "Sensable PHANToM (PCI)"
122 Say Y here if you want to build a driver for Sensable PHANToM device.
124 This driver is only for PCI PHANToMs.
126 If you choose to build module, its name will be phantom. If unsure,
130 tristate "SGI IOC4 Base IO support"
133 This option enables basic support for the IOC4 chip on certain
134 SGI IO controller cards (IO9, IO10, and PCI-RT). This option
135 does not enable any specific functions on such a card, but provides
136 necessary infrastructure for other drivers to utilize.
138 If you have an SGI Altix with an IOC4-based card say Y.
142 tristate "TI Flash Media interface support (EXPERIMENTAL)"
143 depends on EXPERIMENTAL && PCI
145 If you want support for Texas Instruments(R) Flash Media adapters
146 you should select this option and then also choose an appropriate
147 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
148 support', if you have a TI PCI74xx compatible card reader, for
150 You will also have to select some flash card format drivers. MMC/SD
151 cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
152 Interface support (MMC_TIFM_SD)'.
154 To compile this driver as a module, choose M here: the module will
158 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support (EXPERIMENTAL)"
159 depends on PCI && TIFM_CORE && EXPERIMENTAL
162 This option enables support for Texas Instruments(R) PCI74xx and
163 PCI76xx families of Flash Media adapters, found in many laptops.
164 To make actual use of the device, you will have to select some
165 flash card format drivers, as outlined in the TIFM_CORE Help.
167 To compile this driver as a module, choose M here: the module will
171 tristate "Integrated Circuits ICS932S401"
172 depends on I2C && EXPERIMENTAL
174 If you say yes here you get support for the Integrated Circuits
175 ICS932S401 clock control chips.
177 This driver can also be built as a module. If so, the module
178 will be called ics932s401.
181 tristate "Device driver for Atmel SSC peripheral"
182 depends on AVR32 || ARCH_AT91
184 This option enables device driver support for Atmel Synchronized
185 Serial Communication peripheral (SSC).
187 The SSC peripheral supports a wide variety of serial frame based
188 communications, i.e. I2S, SPI, etc.
192 config ENCLOSURE_SERVICES
193 tristate "Enclosure Services"
196 Provides support for intelligent enclosures (bays which
197 contain storage devices). You also need either a host
198 driver (SCSI/ATA) which supports enclosures
199 or a SCSI enclosure device (SES) to use these services.
202 tristate "Support communication between SGI SSIs"
204 depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
205 select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
206 select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
207 select SGI_GRU if X86_64 && SMP
209 An SGI machine can be divided into multiple Single System
210 Images which act independently of each other and have
211 hardware based memory protection from the others. Enabling
212 this feature will allow for direct communication between SSIs
213 based on a network adapter and DMA messaging.
216 tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
221 This driver provides access to MFGPT functionality for other
222 drivers that need timers. MFGPTs are available in the CS5535 and
223 CS5536 companion chips that are found in AMD Geode and several
224 other platforms. They have a better resolution and max interval
225 than the generic PIT, and are suitable for use as high-res timers.
226 You probably don't want to enable this manually; other drivers that
227 make use of it should enable it.
229 config CS5535_MFGPT_DEFAULT_IRQ
231 depends on CS5535_MFGPT
234 MFGPTs on the CS5535 require an interrupt. The selected IRQ
235 can be overridden as a module option as well as by driver that
236 use the cs5535_mfgpt_ API; however, different architectures might
237 want to use a different IRQ by default. This is here for
238 architectures to set as necessary.
240 config CS5535_CLOCK_EVENT_SRC
241 tristate "CS5535/CS5536 high-res timer (MFGPT) events"
242 depends on GENERIC_TIME && GENERIC_CLOCKEVENTS && CS5535_MFGPT
244 This driver provides a clock event source based on the MFGPT
245 timer(s) in the CS5535 and CS5536 companion chips.
246 MFGPTs have a better resolution and max interval than the
247 generic PIT, and are suitable for use as high-res timers.
250 tristate "Channel interface driver for HP iLO/iLO2 processor"
254 The channel interface driver allows applications to communicate
255 with iLO/iLO2 management processors present on HP ProLiant
256 servers. Upon loading, the driver creates /dev/hpilo/dXccbN files,
257 which can be used to gather data from the management processor,
258 via read and write system calls.
260 To compile this driver as a module, choose M here: the
261 module will be called hpilo.
264 tristate "SGI GRU driver"
265 depends on X86_UV && SMP
269 The GRU is a hardware resource located in the system chipset. The GRU
270 contains memory that can be mmapped into the user address space. This memory is
271 used to communicate with the GRU to perform functions such as load/store,
272 scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
273 instructions using user virtual addresses. GRU instructions (ex., bcopy) use
274 user virtual addresses for operands.
276 If you are not running on a SGI UV system, say N.
279 bool "SGI GRU driver debug"
283 This option enables addition debugging code for the SGI GRU driver. If
284 you are unsure, say N.
287 tristate "Intersil ISL29003 ambient light sensor"
288 depends on I2C && SYSFS
290 If you say yes here you get support for the Intersil ISL29003
291 ambient light sensor.
293 This driver can also be built as a module. If so, the module
294 will be called isl29003.
296 config SENSORS_TSL2550
297 tristate "Taos TSL2550 ambient light sensor"
298 depends on I2C && SYSFS
300 If you say yes here you get support for the Taos TSL2550
301 ambient light sensor.
303 This driver can also be built as a module. If so, the module
304 will be called tsl2550.
307 tristate "EP93xx PWM support"
308 depends on ARCH_EP93XX
310 This option enables device driver support for the PWM channels
311 on the Cirrus EP93xx processors. The EP9307 chip only has one
312 PWM channel all the others have two, the second channel is an
313 alternate function of the EGPIO14 pin. A sysfs interface is
314 provided to control the PWM channels.
316 To compile this driver as a module, choose M here: the module will
317 be called ep93xx_pwm.
320 tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
321 depends on I2C && EXPERIMENTAL
323 If you say yes here you get support for Dallas Semiconductor
324 DS1682 Total Elapsed Time Recorder.
326 This driver can also be built as a module. If so, the module
327 will be called ds1682.
330 tristate "Texas Instruments DAC7512"
331 depends on SPI && SYSFS
333 If you say yes here you get support for the Texas Instruments
334 DAC7512 16-bit digital-to-analog converter.
336 This driver can also be built as a module. If so, the module
337 will be calles ti_dac7512.
339 config VMWARE_BALLOON
340 tristate "VMware Balloon Driver"
343 This is VMware physical memory management driver which acts
344 like a "balloon" that can be inflated to reclaim physical pages
345 by reserving them in the guest and invalidating them in the
346 monitor, freeing up the underlying machine pages so they can
347 be allocated to other guests. The balloon can also be deflated
348 to allow the guest to use more physical memory.
352 To compile this driver as a module, choose M here: the
353 module will be called vmware_balloon.
355 source "drivers/misc/c2port/Kconfig"
356 source "drivers/misc/eeprom/Kconfig"
357 source "drivers/misc/cb710/Kconfig"
358 source "drivers/misc/iwmc3200top/Kconfig"