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 "Testing module to detect hardware-induced latencies"
96 depends on RING_BUFFER
99 A simple hardware latency detector. Use this module to detect
100 large latencies introduced by the behavior of the underlying
101 system firmware external to Linux. We do this using periodic
102 use of stop_machine to grab all available CPUs and measure
103 for unexplainable gaps in the CPU timestamp counter(s). By
104 default, the module is not enabled until the "enable" file
105 within the "hwlat_detector" debugfs directory is toggled.
107 This module is often used to detect SMI (System Management
108 Interrupts) on x86 systems, though is not x86 specific. To
109 this end, we default to using a sample window of 1 second,
110 during which we will sample for 0.5 seconds. If an SMI or
111 similar event occurs during that time, it is recorded
112 into an 8K samples global ring buffer until retreived.
114 WARNING: This software should never be enabled (it can be built
115 but should not be turned on after it is loaded) in a production
116 environment where high latencies are a concern since the
117 sampling mechanism actually introduces latencies for
118 regular tasks while the CPU(s) are being held.
123 tristate "Sensable PHANToM (PCI)"
126 Say Y here if you want to build a driver for Sensable PHANToM device.
128 This driver is only for PCI PHANToMs.
130 If you choose to build module, its name will be phantom. If unsure,
134 tristate "SGI IOC4 Base IO support"
137 This option enables basic support for the IOC4 chip on certain
138 SGI IO controller cards (IO9, IO10, and PCI-RT). This option
139 does not enable any specific functions on such a card, but provides
140 necessary infrastructure for other drivers to utilize.
142 If you have an SGI Altix with an IOC4-based card say Y.
146 tristate "TI Flash Media interface support (EXPERIMENTAL)"
147 depends on EXPERIMENTAL && PCI
149 If you want support for Texas Instruments(R) Flash Media adapters
150 you should select this option and then also choose an appropriate
151 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
152 support', if you have a TI PCI74xx compatible card reader, for
154 You will also have to select some flash card format drivers. MMC/SD
155 cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
156 Interface support (MMC_TIFM_SD)'.
158 To compile this driver as a module, choose M here: the module will
162 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support (EXPERIMENTAL)"
163 depends on PCI && TIFM_CORE && EXPERIMENTAL
166 This option enables support for Texas Instruments(R) PCI74xx and
167 PCI76xx families of Flash Media adapters, found in many laptops.
168 To make actual use of the device, you will have to select some
169 flash card format drivers, as outlined in the TIFM_CORE Help.
171 To compile this driver as a module, choose M here: the module will
175 tristate "Integrated Circuits ICS932S401"
176 depends on I2C && EXPERIMENTAL
178 If you say yes here you get support for the Integrated Circuits
179 ICS932S401 clock control chips.
181 This driver can also be built as a module. If so, the module
182 will be called ics932s401.
185 tristate "Device driver for Atmel SSC peripheral"
186 depends on AVR32 || ARCH_AT91
188 This option enables device driver support for Atmel Synchronized
189 Serial Communication peripheral (SSC).
191 The SSC peripheral supports a wide variety of serial frame based
192 communications, i.e. I2S, SPI, etc.
196 config ENCLOSURE_SERVICES
197 tristate "Enclosure Services"
200 Provides support for intelligent enclosures (bays which
201 contain storage devices). You also need either a host
202 driver (SCSI/ATA) which supports enclosures
203 or a SCSI enclosure device (SES) to use these services.
206 tristate "Support communication between SGI SSIs"
208 depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
209 select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
210 select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
211 select SGI_GRU if X86_64 && SMP
213 An SGI machine can be divided into multiple Single System
214 Images which act independently of each other and have
215 hardware based memory protection from the others. Enabling
216 this feature will allow for direct communication between SSIs
217 based on a network adapter and DMA messaging.
220 tristate "Channel interface driver for HP iLO/iLO2 processor"
224 The channel interface driver allows applications to communicate
225 with iLO/iLO2 management processors present on HP ProLiant
226 servers. Upon loading, the driver creates /dev/hpilo/dXccbN files,
227 which can be used to gather data from the management processor,
228 via read and write system calls.
230 To compile this driver as a module, choose M here: the
231 module will be called hpilo.
234 tristate "SGI GRU driver"
235 depends on X86_UV && SMP
239 The GRU is a hardware resource located in the system chipset. The GRU
240 contains memory that can be mmapped into the user address space. This memory is
241 used to communicate with the GRU to perform functions such as load/store,
242 scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
243 instructions using user virtual addresses. GRU instructions (ex., bcopy) use
244 user virtual addresses for operands.
246 If you are not running on a SGI UV system, say N.
249 bool "SGI GRU driver debug"
253 This option enables addition debugging code for the SGI GRU driver. If
254 you are unsure, say N.
257 tristate "Dell Laptop Extras (EXPERIMENTAL)"
260 depends on EXPERIMENTAL
261 depends on BACKLIGHT_CLASS_DEVICE
263 depends on POWER_SUPPLY
266 This driver adds support for rfkill and backlight control to Dell
270 tristate "Intersil ISL29003 ambient light sensor"
271 depends on I2C && SYSFS
273 If you say yes here you get support for the Intersil ISL29003
274 ambient light sensor.
276 This driver can also be built as a module. If so, the module
277 will be called isl29003.
280 tristate "EP93xx PWM support"
281 depends on ARCH_EP93XX
283 This option enables device driver support for the PWM channels
284 on the Cirrus EP93xx processors. The EP9307 chip only has one
285 PWM channel all the others have two, the second channel is an
286 alternate function of the EGPIO14 pin. A sysfs interface is
287 provided to control the PWM channels.
289 To compile this driver as a module, choose M here: the module will
290 be called ep93xx_pwm.
293 tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
294 depends on I2C && EXPERIMENTAL
296 If you say yes here you get support for Dallas Semiconductor
297 DS1682 Total Elapsed Time Recorder.
299 This driver can also be built as a module. If so, the module
300 will be called ds1682.
303 tristate "Texas Instruments DAC7512"
304 depends on SPI && SYSFS
306 If you say yes here you get support for the Texas Instruments
307 DAC7512 16-bit digital-to-analog converter.
309 This driver can also be built as a module. If so, the module
310 will be calles ti_dac7512.
312 source "drivers/misc/c2port/Kconfig"
313 source "drivers/misc/eeprom/Kconfig"
314 source "drivers/misc/cb710/Kconfig"