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 prcoessors. Pulse Width Modulation is used for
22 purposes including software controlled power-efficent 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 "EEPROM 93CX6 support"
93 This is a driver for the EEPROM chipsets 93c46 and 93c66.
94 The driver supports both read as well as write commands.
99 tristate "SGI IOC4 Base IO support"
102 This option enables basic support for the IOC4 chip on certain
103 SGI IO controller cards (IO9, IO10, and PCI-RT). This option
104 does not enable any specific functions on such a card, but provides
105 necessary infrastructure for other drivers to utilize.
107 If you have an SGI Altix with an IOC4-based card say Y.
111 tristate "TI Flash Media interface support (EXPERIMENTAL)"
112 depends on EXPERIMENTAL && PCI
114 If you want support for Texas Instruments(R) Flash Media adapters
115 you should select this option and then also choose an appropriate
116 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
117 support', if you have a TI PCI74xx compatible card reader, for
119 You will also have to select some flash card format drivers. MMC/SD
120 cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
121 Interface support (MMC_TIFM_SD)'.
123 To compile this driver as a module, choose M here: the module will
127 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support (EXPERIMENTAL)"
128 depends on PCI && TIFM_CORE && EXPERIMENTAL
131 This option enables support for Texas Instruments(R) PCI74xx and
132 PCI76xx families of Flash Media adapters, found in many laptops.
133 To make actual use of the device, you will have to select some
134 flash card format drivers, as outlined in the TIFM_CORE Help.
136 To compile this driver as a module, choose M here: the module will
140 tristate "Acer WMI Laptop Extras (EXPERIMENTAL)"
142 depends on EXPERIMENTAL
144 depends on LEDS_CLASS
146 depends on BACKLIGHT_CLASS_DEVICE
147 depends on SERIO_I8042
151 This is a driver for newer Acer (and Wistron) laptops. It adds
152 wireless radio and bluetooth control, and on some laptops,
153 exposes the mail LED and LCD backlight.
155 For more information about this driver see
156 <file:Documentation/laptops/acer-wmi.txt>
158 If you have an ACPI-WMI compatible Acer/ Wistron laptop, say Y or M
162 tristate "Asus Laptop Extras (EXPERIMENTAL)"
165 depends on EXPERIMENTAL && !ACPI_ASUS
166 depends on LEDS_CLASS
168 depends on BACKLIGHT_CLASS_DEVICE
170 This is the new Linux driver for Asus laptops. It may also support some
171 MEDION, JVC or VICTOR laptops. It makes all the extra buttons generate
172 standard ACPI events that go through /proc/acpi/events. It also adds
173 support for video output switching, LCD backlight control, Bluetooth and
174 Wlan control, and most importantly, allows you to blink those fancy LEDs.
176 For more information and a userspace daemon for handling the extra
177 buttons see <http://acpi4asus.sf.net/>.
179 If you have an ACPI-compatible ASUS laptop, say Y or M here.
181 config FUJITSU_LAPTOP
182 tristate "Fujitsu Laptop Extras"
186 depends on BACKLIGHT_CLASS_DEVICE
188 This is a driver for laptops built by Fujitsu:
190 * P2xxx/P5xxx/S6xxx/S7xxx series Lifebooks
191 * Possibly other Fujitsu laptop models
192 * Tested with S6410 and S7020
194 It adds support for LCD brightness control and some hotkeys.
196 If you have a Fujitsu laptop, say Y or M here.
198 config FUJITSU_LAPTOP_DEBUG
199 bool "Verbose debug mode for Fujitsu Laptop Extras"
200 depends on FUJITSU_LAPTOP
203 Enables extra debug output from the fujitsu extras driver, at the
204 expense of a slight increase in driver size.
206 If you are not sure, say N here.
209 tristate "HP Compaq TC1100 Tablet WMI Extras (EXPERIMENTAL)"
210 depends on X86 && !X86_64
211 depends on EXPERIMENTAL
215 This is a driver for the WMI extensions (wireless and bluetooth power
216 control) of the HP Compaq TC1100 tablet.
219 tristate "HP WMI extras"
224 Say Y here if you want to support WMI-based hotkeys on HP laptops and
225 to read data from WMI such as docking or ambient light sensor state.
227 To compile this driver as a module, choose M here: the module will
231 tristate "Integrated Circuits ICS932S401"
232 depends on I2C && EXPERIMENTAL
234 If you say yes here you get support for the Integrated Circuits
235 ICS932S401 clock control chips.
237 This driver can also be built as a module. If so, the module
238 will be called ics932s401.
241 tristate "MSI Laptop Extras"
244 depends on BACKLIGHT_CLASS_DEVICE
246 This is a driver for laptops built by MSI (MICRO-STAR
249 MSI MegaBook S270 (MS-1013)
250 Cytron/TCM/Medion/Tchibo MD96100/SAM2000
252 It adds support for Bluetooth, WLAN and LCD brightness control.
254 More information about this driver is available at
255 <http://0pointer.de/lennart/tchibo.html>.
257 If you have an MSI S270 laptop, say Y or M here.
259 config PANASONIC_LAPTOP
260 tristate "Panasonic Laptop Extras"
261 depends on X86 && INPUT && ACPI
262 depends on BACKLIGHT_CLASS_DEVICE
264 This driver adds support for access to backlight control and hotkeys
265 on Panasonic Let's Note laptops.
267 If you have a Panasonic Let's note laptop (such as the R1(N variant),
268 R2, R3, R5, T2, W2 and Y2 series), say Y.
271 tristate "Compal Laptop Extras"
274 depends on BACKLIGHT_CLASS_DEVICE
276 This is a driver for laptops built by Compal:
283 It adds support for Bluetooth, WLAN and LCD brightness control.
285 If you have an Compal FL9x/IFL9x/FT00 laptop, say Y or M here.
288 tristate "Sony Laptop Extras"
289 depends on X86 && ACPI
290 select BACKLIGHT_CLASS_DEVICE
293 This mini-driver drives the SNC and SPIC devices present in the ACPI
294 BIOS of the Sony Vaio laptops.
296 It gives access to some extra laptop functionalities like Bluetooth,
297 screen brightness control, Fn keys and allows powering on/off some
300 Read <file:Documentation/laptops/sony-laptop.txt> for more information.
303 bool "Sonypi compatibility"
304 depends on SONY_LAPTOP
306 Build the sonypi driver compatibility code into the sony-laptop driver.
309 tristate "ThinkPad ACPI Laptop Extras"
310 depends on X86 && ACPI
311 select BACKLIGHT_LCD_SUPPORT
312 select BACKLIGHT_CLASS_DEVICE
321 This is a driver for the IBM and Lenovo ThinkPad laptops. It adds
322 support for Fn-Fx key combinations, Bluetooth control, video
323 output switching, ThinkLight control, UltraBay eject and more.
324 For more information about this driver see
325 <file:Documentation/laptops/thinkpad-acpi.txt> and
326 <http://ibm-acpi.sf.net/> .
328 This driver was formerly known as ibm-acpi.
330 If you have an IBM or Lenovo ThinkPad laptop, say Y or M here.
332 config THINKPAD_ACPI_DEBUG
333 bool "Verbose debug mode"
334 depends on THINKPAD_ACPI
337 Enables extra debugging information, at the expense of a slightly
338 increase in driver size.
340 If you are not sure, say N here.
342 config THINKPAD_ACPI_DOCK
343 bool "Legacy Docking Station Support"
344 depends on THINKPAD_ACPI
345 depends on ACPI_DOCK=n
348 Allows the thinkpad_acpi driver to handle docking station events.
349 This support was made obsolete by the generic ACPI docking station
350 support (CONFIG_ACPI_DOCK). It will allow locking and removing the
351 laptop from the docking station, but will not properly connect PCI
354 If you are not sure, say N here.
356 config THINKPAD_ACPI_BAY
357 bool "Legacy Removable Bay Support"
358 depends on THINKPAD_ACPI
361 Allows the thinkpad_acpi driver to handle removable bays. It will
362 electrically disable the device in the bay, and also generate
363 notifications when the bay lever is ejected or inserted.
365 If you are not sure, say Y here.
367 config THINKPAD_ACPI_VIDEO
368 bool "Video output control support"
369 depends on THINKPAD_ACPI
372 Allows the thinkpad_acpi driver to provide an interface to control
373 the various video output ports.
375 This feature often won't work well, depending on ThinkPad model,
376 display state, video output devices in use, whether there is a X
377 server running, phase of the moon, and the current mood of
378 Schroedinger's cat. If you can use X.org's RandR to control
379 your ThinkPad's video output ports instead of this feature,
380 don't think twice: do it and say N here to save some memory.
382 If you are not sure, say Y here.
384 config THINKPAD_ACPI_HOTKEY_POLL
385 bool "Support NVRAM polling for hot keys"
386 depends on THINKPAD_ACPI
389 Some thinkpad models benefit from NVRAM polling to detect a few of
390 the hot key press events. If you know your ThinkPad model does not
391 need to do NVRAM polling to support any of the hot keys you use,
392 unselecting this option will save about 1kB of memory.
394 ThinkPads T40 and newer, R52 and newer, and X31 and newer are
395 unlikely to need NVRAM polling in their latest BIOS versions.
397 NVRAM polling can detect at most the following keys: ThinkPad/Access
398 IBM, Zoom, Switch Display (fn+F7), ThinkLight, Volume up/down/mute,
399 Brightness up/down, Display Expand (fn+F8), Hibernate (fn+F12).
401 If you are not sure, say Y here. The driver enables polling only if
402 it is strictly necessary to do so.
405 tristate "Device driver for Atmel SSC peripheral"
406 depends on AVR32 || ARCH_AT91
408 This option enables device driver support for Atmel Syncronized
409 Serial Communication peripheral (SSC).
411 The SSC peripheral supports a wide variety of serial frame based
412 communications, i.e. I2S, SPI, etc.
417 tristate "Thermal Management driver for Intel menlow platform"
418 depends on ACPI_THERMAL
422 ACPI thermal management enhancement driver on
423 Intel Menlow platform.
428 tristate "Eee PC Hotkey Driver (EXPERIMENTAL)"
431 depends on EXPERIMENTAL
432 select BACKLIGHT_CLASS_DEVICE
436 This driver supports the Fn-Fx keys on Eee PC laptops.
437 It also adds the ability to switch camera/wlan on/off.
439 If you have an Eee PC laptop, say Y or M here.
441 config ENCLOSURE_SERVICES
442 tristate "Enclosure Services"
445 Provides support for intelligent enclosures (bays which
446 contain storage devices). You also need either a host
447 driver (SCSI/ATA) which supports enclosures
448 or a SCSI enclosure device (SES) to use these services.
451 tristate "Support communication between SGI SSIs"
453 depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_64) && SMP
454 select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
455 select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
456 select SGI_GRU if (IA64_GENERIC || IA64_SGI_UV || X86_64) && SMP
458 An SGI machine can be divided into multiple Single System
459 Images which act independently of each other and have
460 hardware based memory protection from the others. Enabling
461 this feature will allow for direct communication between SSIs
462 based on a network adapter and DMA messaging.
465 tristate "Channel interface driver for HP iLO/iLO2 processor"
469 The channel interface driver allows applications to communicate
470 with iLO/iLO2 management processors present on HP ProLiant
471 servers. Upon loading, the driver creates /dev/hpilo/dXccbN files,
472 which can be used to gather data from the management processor,
473 via read and write system calls.
475 To compile this driver as a module, choose M here: the
476 module will be called hpilo.
479 tristate "SGI GRU driver"
480 depends on (X86_64 || IA64_SGI_UV || IA64_GENERIC) && SMP
484 The GRU is a hardware resource located in the system chipset. The GRU
485 contains memory that can be mmapped into the user address space. This memory is
486 used to communicate with the GRU to perform functions such as load/store,
487 scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
488 instructions using user virtual addresses. GRU instructions (ex., bcopy) use
489 user virtual addresses for operands.
491 If you are not running on a SGI UV system, say N.
494 bool "SGI GRU driver debug"
498 This option enables addition debugging code for the SGI GRU driver. If
499 you are unsure, say N.
501 source "drivers/misc/c2port/Kconfig"