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 "Atmel AT32/AT91 PWM support"
18 depends on AVR32 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9
20 This option enables device driver support for the PWM channels
21 on certain Atmel processors. Pulse Width Modulation is used for
22 purposes including software controlled power-efficient backlights
23 on LCD displays, motor control, and waveform generation.
26 bool "Atmel AT32/AT91 Timer/Counter Library"
27 depends on (AVR32 || ARCH_AT91)
29 Select this if you want a library to allocate the Timer/Counter
30 blocks found on many Atmel processors. This facilitates using
31 these blocks by different drivers despite processor differences.
33 config ATMEL_TCB_CLKSRC
34 bool "TC Block Clocksource"
35 depends on ATMEL_TCLIB && GENERIC_TIME
38 Select this to get a high precision clocksource based on a
39 TC block with a 5+ MHz base clock rate. Two timer channels
40 are combined to make a single 32-bit timer.
42 When GENERIC_CLOCKEVENTS is defined, the third timer channel
43 may be used as a clock event device supporting oneshot mode
44 (delays of up to two seconds) based on the 32 KiHz clock.
46 config ATMEL_TCB_CLKSRC_BLOCK
48 depends on ATMEL_TCB_CLKSRC
49 prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X
53 Some chips provide more than one TC block, so you have the
54 choice of which one to use for the clock framework. The other
55 TC can be used for other purposes, such as PWM generation and
59 tristate "Device driver for IBM RSA service processor"
60 depends on X86 && PCI && INPUT && EXPERIMENTAL
62 This option enables device driver support for in-band access to the
63 IBM RSA (Condor) service processor in eServer xSeries systems.
64 The ibmasm device driver allows user space application to access
65 ASM (Advanced Systems Management) functions on the service
66 processor. The driver is meant to be used in conjunction with
68 The ibmasm driver also enables the OS to use the UART on the
69 service processor board as a regular serial port. To make use of
70 this feature serial driver support (CONFIG_SERIAL_8250) must be
73 WARNING: This software may not be supported or function
74 correctly on your IBM server. Please consult the IBM ServerProven
75 website <http://www.pc.ibm.com/ww/eserver/xseries/serverproven> for
76 information on the specific driver level and support statement
80 tristate "Sensable PHANToM (PCI)"
83 Say Y here if you want to build a driver for Sensable PHANToM device.
85 This driver is only for PCI PHANToMs.
87 If you choose to build module, its name will be phantom. If unsure,
91 tristate "SGI IOC4 Base IO support"
94 This option enables basic support for the IOC4 chip on certain
95 SGI IO controller cards (IO9, IO10, and PCI-RT). This option
96 does not enable any specific functions on such a card, but provides
97 necessary infrastructure for other drivers to utilize.
99 If you have an SGI Altix with an IOC4-based card say Y.
103 tristate "TI Flash Media interface support (EXPERIMENTAL)"
104 depends on EXPERIMENTAL && PCI
106 If you want support for Texas Instruments(R) Flash Media adapters
107 you should select this option and then also choose an appropriate
108 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
109 support', if you have a TI PCI74xx compatible card reader, for
111 You will also have to select some flash card format drivers. MMC/SD
112 cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
113 Interface support (MMC_TIFM_SD)'.
115 To compile this driver as a module, choose M here: the module will
119 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support (EXPERIMENTAL)"
120 depends on PCI && TIFM_CORE && EXPERIMENTAL
123 This option enables support for Texas Instruments(R) PCI74xx and
124 PCI76xx families of Flash Media adapters, found in many laptops.
125 To make actual use of the device, you will have to select some
126 flash card format drivers, as outlined in the TIFM_CORE Help.
128 To compile this driver as a module, choose M here: the module will
132 tristate "Integrated Circuits ICS932S401"
133 depends on I2C && EXPERIMENTAL
135 If you say yes here you get support for the Integrated Circuits
136 ICS932S401 clock control chips.
138 This driver can also be built as a module. If so, the module
139 will be called ics932s401.
142 tristate "Device driver for Atmel SSC peripheral"
143 depends on AVR32 || ARCH_AT91
145 This option enables device driver support for Atmel Synchronized
146 Serial Communication peripheral (SSC).
148 The SSC peripheral supports a wide variety of serial frame based
149 communications, i.e. I2S, SPI, etc.
154 bool "Serial Trace Interface support"
155 depends on ARCH_OMAP16XX || ARCH_OMAP24XX || ARCH_OMAP34XX
158 Serial Trace Interface. The protocols suported for OMAP1/2/3 are
159 STI/CSTI/XTIv2 correspondingly.
161 config OMAP_STI_CONSOLE
162 bool "STI console support"
165 This enables a console driver by way of STI/XTI.
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 "Channel interface driver for HP iLO/iLO2 processor"
195 The channel interface driver allows applications to communicate
196 with iLO/iLO2 management processors present on HP ProLiant
197 servers. Upon loading, the driver creates /dev/hpilo/dXccbN files,
198 which can be used to gather data from the management processor,
199 via read and write system calls.
201 To compile this driver as a module, choose M here: the
202 module will be called hpilo.
205 tristate "SGI GRU driver"
206 depends on X86_UV && SMP
210 The GRU is a hardware resource located in the system chipset. The GRU
211 contains memory that can be mmapped into the user address space. This memory is
212 used to communicate with the GRU to perform functions such as load/store,
213 scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
214 instructions using user virtual addresses. GRU instructions (ex., bcopy) use
215 user virtual addresses for operands.
217 If you are not running on a SGI UV system, say N.
220 bool "SGI GRU driver debug"
224 This option enables addition debugging code for the SGI GRU driver. If
225 you are unsure, say N.
228 tristate "Dell Laptop Extras (EXPERIMENTAL)"
231 depends on EXPERIMENTAL
232 depends on BACKLIGHT_CLASS_DEVICE
234 depends on POWER_SUPPLY
237 This driver adds support for rfkill and backlight control to Dell
241 tristate "Intersil ISL29003 ambient light sensor"
242 depends on I2C && SYSFS
244 If you say yes here you get support for the Intersil ISL29003
245 ambient light sensor.
247 This driver can also be built as a module. If so, the module
248 will be called isl29003.
250 source "drivers/misc/c2port/Kconfig"
251 source "drivers/misc/eeprom/Kconfig"