Merge branch 'for-linus' of git://git.o-hand.com/linux-rpurdie-leds
[deliverable/linux.git] / drivers / misc / Kconfig
1 #
2 # Misc strange devices
3 #
4
5 menuconfig MISC_DEVICES
6 bool "Misc devices"
7 default y
8 ---help---
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.
11
12 If you say N, all options in this submenu will be skipped and disabled.
13
14 if MISC_DEVICES
15
16 config ATMEL_PWM
17 tristate "Atmel AT32/AT91 PWM support"
18 depends on AVR32 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9
19 help
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.
24
25 config ATMEL_TCLIB
26 bool "Atmel AT32/AT91 Timer/Counter Library"
27 depends on (AVR32 || ARCH_AT91)
28 help
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.
32
33 config ATMEL_TCB_CLKSRC
34 bool "TC Block Clocksource"
35 depends on ATMEL_TCLIB && GENERIC_TIME
36 default y
37 help
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.
41
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.
45
46 config ATMEL_TCB_CLKSRC_BLOCK
47 int
48 depends on ATMEL_TCB_CLKSRC
49 prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X
50 default 0
51 range 0 1
52 help
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
56 interval timing.
57
58 config IBM_ASM
59 tristate "Device driver for IBM RSA service processor"
60 depends on X86 && PCI && INPUT && EXPERIMENTAL
61 ---help---
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
67 a user space API.
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
71 enabled.
72
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
77 for your IBM server.
78
79 config PHANTOM
80 tristate "Sensable PHANToM (PCI)"
81 depends on PCI
82 help
83 Say Y here if you want to build a driver for Sensable PHANToM device.
84
85 This driver is only for PCI PHANToMs.
86
87 If you choose to build module, its name will be phantom. If unsure,
88 say N here.
89
90 config EEPROM_93CX6
91 tristate "EEPROM 93CX6 support"
92 ---help---
93 This is a driver for the EEPROM chipsets 93c46 and 93c66.
94 The driver supports both read as well as write commands.
95
96 If unsure, say N.
97
98 config SGI_IOC4
99 tristate "SGI IOC4 Base IO support"
100 depends on PCI
101 ---help---
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.
106
107 If you have an SGI Altix with an IOC4-based card say Y.
108 Otherwise say N.
109
110 config TIFM_CORE
111 tristate "TI Flash Media interface support (EXPERIMENTAL)"
112 depends on EXPERIMENTAL && PCI
113 help
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
118 example.
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)'.
122
123 To compile this driver as a module, choose M here: the module will
124 be called tifm_core.
125
126 config TIFM_7XX1
127 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support (EXPERIMENTAL)"
128 depends on PCI && TIFM_CORE && EXPERIMENTAL
129 default TIFM_CORE
130 help
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.
135
136 To compile this driver as a module, choose M here: the module will
137 be called tifm_7xx1.
138
139 config ICS932S401
140 tristate "Integrated Circuits ICS932S401"
141 depends on I2C && EXPERIMENTAL
142 help
143 If you say yes here you get support for the Integrated Circuits
144 ICS932S401 clock control chips.
145
146 This driver can also be built as a module. If so, the module
147 will be called ics932s401.
148
149 config ATMEL_SSC
150 tristate "Device driver for Atmel SSC peripheral"
151 depends on AVR32 || ARCH_AT91
152 ---help---
153 This option enables device driver support for Atmel Syncronized
154 Serial Communication peripheral (SSC).
155
156 The SSC peripheral supports a wide variety of serial frame based
157 communications, i.e. I2S, SPI, etc.
158
159 If unsure, say N.
160
161 config ENCLOSURE_SERVICES
162 tristate "Enclosure Services"
163 default n
164 help
165 Provides support for intelligent enclosures (bays which
166 contain storage devices). You also need either a host
167 driver (SCSI/ATA) which supports enclosures
168 or a SCSI enclosure device (SES) to use these services.
169
170 config SGI_XP
171 tristate "Support communication between SGI SSIs"
172 depends on NET
173 depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_64) && SMP
174 select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
175 select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
176 select SGI_GRU if (IA64_GENERIC || IA64_SGI_UV || X86_64) && SMP
177 ---help---
178 An SGI machine can be divided into multiple Single System
179 Images which act independently of each other and have
180 hardware based memory protection from the others. Enabling
181 this feature will allow for direct communication between SSIs
182 based on a network adapter and DMA messaging.
183
184 config HP_ILO
185 tristate "Channel interface driver for HP iLO/iLO2 processor"
186 depends on PCI
187 default n
188 help
189 The channel interface driver allows applications to communicate
190 with iLO/iLO2 management processors present on HP ProLiant
191 servers. Upon loading, the driver creates /dev/hpilo/dXccbN files,
192 which can be used to gather data from the management processor,
193 via read and write system calls.
194
195 To compile this driver as a module, choose M here: the
196 module will be called hpilo.
197
198 config SGI_GRU
199 tristate "SGI GRU driver"
200 depends on (X86_64 || IA64_SGI_UV || IA64_GENERIC) && SMP
201 default n
202 select MMU_NOTIFIER
203 ---help---
204 The GRU is a hardware resource located in the system chipset. The GRU
205 contains memory that can be mmapped into the user address space. This memory is
206 used to communicate with the GRU to perform functions such as load/store,
207 scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
208 instructions using user virtual addresses. GRU instructions (ex., bcopy) use
209 user virtual addresses for operands.
210
211 If you are not running on a SGI UV system, say N.
212
213 config SGI_GRU_DEBUG
214 bool "SGI GRU driver debug"
215 depends on SGI_GRU
216 default n
217 ---help---
218 This option enables addition debugging code for the SGI GRU driver. If
219 you are unsure, say N.
220
221 config DELL_LAPTOP
222 tristate "Dell Laptop Extras (EXPERIMENTAL)"
223 depends on X86
224 depends on DCDBAS
225 depends on EXPERIMENTAL
226 depends on BACKLIGHT_CLASS_DEVICE
227 depends on RFKILL
228 default n
229 ---help---
230 This driver adds support for rfkill and backlight control to Dell
231 laptops.
232
233 source "drivers/misc/c2port/Kconfig"
234
235 endif # MISC_DEVICES
This page took 0.035357 seconds and 6 git commands to generate.