1# 2# Misc strange devices 3# 4 5menuconfig 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 14if MISC_DEVICES 15 16config AD525X_DPOT 17 tristate "Analog Devices AD525x Digital Potentiometers" 18 depends on I2C && SYSFS 19 help 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. 23 24 See Documentation/misc-devices/ad525x_dpot.txt for the 25 userspace interface. 26 27 This driver can also be built as a module. If so, the module 28 will be called ad525x_dpot. 29 30config ATMEL_PWM 31 tristate "Atmel AT32/AT91 PWM support" 32 depends on AVR32 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9 33 help 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. 38 39config ATMEL_TCLIB 40 bool "Atmel AT32/AT91 Timer/Counter Library" 41 depends on (AVR32 || ARCH_AT91) 42 help 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. 46 47config ATMEL_TCB_CLKSRC 48 bool "TC Block Clocksource" 49 depends on ATMEL_TCLIB && GENERIC_TIME 50 default y 51 help 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. 55 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. 59 60config ATMEL_TCB_CLKSRC_BLOCK 61 int 62 depends on ATMEL_TCB_CLKSRC 63 prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X 64 default 0 65 range 0 1 66 help 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 70 interval timing. 71 72config IBM_ASM 73 tristate "Device driver for IBM RSA service processor" 74 depends on X86 && PCI && INPUT && EXPERIMENTAL 75 ---help--- 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 81 a user space API. 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 85 enabled. 86 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 91 for your IBM server. 92 93config PHANTOM 94 tristate "Sensable PHANToM (PCI)" 95 depends on PCI 96 help 97 Say Y here if you want to build a driver for Sensable PHANToM device. 98 99 This driver is only for PCI PHANToMs. 100 101 If you choose to build module, its name will be phantom. If unsure, 102 say N here. 103 104config SGI_IOC4 105 tristate "SGI IOC4 Base IO support" 106 depends on PCI 107 ---help--- 108 This option enables basic support for the IOC4 chip on certain 109 SGI IO controller cards (IO9, IO10, and PCI-RT). This option 110 does not enable any specific functions on such a card, but provides 111 necessary infrastructure for other drivers to utilize. 112 113 If you have an SGI Altix with an IOC4-based card say Y. 114 Otherwise say N. 115 116config TIFM_CORE 117 tristate "TI Flash Media interface support (EXPERIMENTAL)" 118 depends on EXPERIMENTAL && PCI 119 help 120 If you want support for Texas Instruments(R) Flash Media adapters 121 you should select this option and then also choose an appropriate 122 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter 123 support', if you have a TI PCI74xx compatible card reader, for 124 example. 125 You will also have to select some flash card format drivers. MMC/SD 126 cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD 127 Interface support (MMC_TIFM_SD)'. 128 129 To compile this driver as a module, choose M here: the module will 130 be called tifm_core. 131 132config TIFM_7XX1 133 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support (EXPERIMENTAL)" 134 depends on PCI && TIFM_CORE && EXPERIMENTAL 135 default TIFM_CORE 136 help 137 This option enables support for Texas Instruments(R) PCI74xx and 138 PCI76xx families of Flash Media adapters, found in many laptops. 139 To make actual use of the device, you will have to select some 140 flash card format drivers, as outlined in the TIFM_CORE Help. 141 142 To compile this driver as a module, choose M here: the module will 143 be called tifm_7xx1. 144 145config ICS932S401 146 tristate "Integrated Circuits ICS932S401" 147 depends on I2C && EXPERIMENTAL 148 help 149 If you say yes here you get support for the Integrated Circuits 150 ICS932S401 clock control chips. 151 152 This driver can also be built as a module. If so, the module 153 will be called ics932s401. 154 155config ATMEL_SSC 156 tristate "Device driver for Atmel SSC peripheral" 157 depends on AVR32 || ARCH_AT91 158 ---help--- 159 This option enables device driver support for Atmel Synchronized 160 Serial Communication peripheral (SSC). 161 162 The SSC peripheral supports a wide variety of serial frame based 163 communications, i.e. I2S, SPI, etc. 164 165 If unsure, say N. 166 167config ENCLOSURE_SERVICES 168 tristate "Enclosure Services" 169 default n 170 help 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. 175 176config SGI_XP 177 tristate "Support communication between SGI SSIs" 178 depends on NET 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 183 ---help--- 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. 189 190config CS5535_MFGPT 191 tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support" 192 depends on PCI 193 depends on X86 194 default n 195 help 196 This driver provides access to MFGPT functionality for other 197 drivers that need timers. MFGPTs are available in the CS5535 and 198 CS5536 companion chips that are found in AMD Geode and several 199 other platforms. They have a better resolution and max interval 200 than the generic PIT, and are suitable for use as high-res timers. 201 You probably don't want to enable this manually; other drivers that 202 make use of it should enable it. 203 204config CS5535_MFGPT_DEFAULT_IRQ 205 int 206 depends on CS5535_MFGPT 207 default 7 208 help 209 MFGPTs on the CS5535 require an interrupt. The selected IRQ 210 can be overridden as a module option as well as by driver that 211 use the cs5535_mfgpt_ API; however, different architectures might 212 want to use a different IRQ by default. This is here for 213 architectures to set as necessary. 214 215config CS5535_CLOCK_EVENT_SRC 216 tristate "CS5535/CS5536 high-res timer (MFGPT) events" 217 depends on GENERIC_TIME && GENERIC_CLOCKEVENTS && CS5535_MFGPT 218 help 219 This driver provides a clock event source based on the MFGPT 220 timer(s) in the CS5535 and CS5536 companion chips. 221 MFGPTs have a better resolution and max interval than the 222 generic PIT, and are suitable for use as high-res timers. 223 224config HP_ILO 225 tristate "Channel interface driver for HP iLO/iLO2 processor" 226 depends on PCI 227 default n 228 help 229 The channel interface driver allows applications to communicate 230 with iLO/iLO2 management processors present on HP ProLiant 231 servers. Upon loading, the driver creates /dev/hpilo/dXccbN files, 232 which can be used to gather data from the management processor, 233 via read and write system calls. 234 235 To compile this driver as a module, choose M here: the 236 module will be called hpilo. 237 238config SGI_GRU 239 tristate "SGI GRU driver" 240 depends on X86_UV && SMP 241 default n 242 select MMU_NOTIFIER 243 ---help--- 244 The GRU is a hardware resource located in the system chipset. The GRU 245 contains memory that can be mmapped into the user address space. This memory is 246 used to communicate with the GRU to perform functions such as load/store, 247 scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user 248 instructions using user virtual addresses. GRU instructions (ex., bcopy) use 249 user virtual addresses for operands. 250 251 If you are not running on a SGI UV system, say N. 252 253config SGI_GRU_DEBUG 254 bool "SGI GRU driver debug" 255 depends on SGI_GRU 256 default n 257 ---help--- 258 This option enables addition debugging code for the SGI GRU driver. If 259 you are unsure, say N. 260 261config ISL29003 262 tristate "Intersil ISL29003 ambient light sensor" 263 depends on I2C && SYSFS 264 help 265 If you say yes here you get support for the Intersil ISL29003 266 ambient light sensor. 267 268 This driver can also be built as a module. If so, the module 269 will be called isl29003. 270 271config SENSORS_TSL2550 272 tristate "Taos TSL2550 ambient light sensor" 273 depends on I2C && SYSFS 274 help 275 If you say yes here you get support for the Taos TSL2550 276 ambient light sensor. 277 278 This driver can also be built as a module. If so, the module 279 will be called tsl2550. 280 281config EP93XX_PWM 282 tristate "EP93xx PWM support" 283 depends on ARCH_EP93XX 284 help 285 This option enables device driver support for the PWM channels 286 on the Cirrus EP93xx processors. The EP9307 chip only has one 287 PWM channel all the others have two, the second channel is an 288 alternate function of the EGPIO14 pin. A sysfs interface is 289 provided to control the PWM channels. 290 291 To compile this driver as a module, choose M here: the module will 292 be called ep93xx_pwm. 293 294config DS1682 295 tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm" 296 depends on I2C && EXPERIMENTAL 297 help 298 If you say yes here you get support for Dallas Semiconductor 299 DS1682 Total Elapsed Time Recorder. 300 301 This driver can also be built as a module. If so, the module 302 will be called ds1682. 303 304config TI_DAC7512 305 tristate "Texas Instruments DAC7512" 306 depends on SPI && SYSFS 307 help 308 If you say yes here you get support for the Texas Instruments 309 DAC7512 16-bit digital-to-analog converter. 310 311 This driver can also be built as a module. If so, the module 312 will be calles ti_dac7512. 313 314source "drivers/misc/c2port/Kconfig" 315source "drivers/misc/eeprom/Kconfig" 316source "drivers/misc/cb710/Kconfig" 317source "drivers/misc/iwmc3200top/Kconfig" 318 319endif # MISC_DEVICES 320