1# 2# Misc strange devices 3# 4 5menuconfig MISC_DEVICES 6 bool "Misc devices" 7 ---help--- 8 Say Y here to get to see options for device drivers from various 9 different categories. This option alone does not add any kernel code. 10 11 If you say N, all options in this submenu will be skipped and disabled. 12 13if MISC_DEVICES 14 15config AD525X_DPOT 16 tristate "Analog Devices Digital Potentiometers" 17 depends on (I2C || SPI) && SYSFS 18 help 19 If you say yes here, you get support for the Analog Devices 20 AD5258, AD5259, AD5251, AD5252, AD5253, AD5254, AD5255 21 AD5160, AD5161, AD5162, AD5165, AD5200, AD5201, AD5203, 22 AD5204, AD5206, AD5207, AD5231, AD5232, AD5233, AD5235, 23 AD5260, AD5262, AD5263, AD5290, AD5291, AD5292, AD5293, 24 AD7376, AD8400, AD8402, AD8403, ADN2850, AD5241, AD5242, 25 AD5243, AD5245, AD5246, AD5247, AD5248, AD5280, AD5282, 26 ADN2860, AD5273, AD5171, AD5170, AD5172, AD5173, AD5270, 27 AD5271, AD5272, AD5274 28 digital potentiometer chips. 29 30 See Documentation/misc-devices/ad525x_dpot.txt for the 31 userspace interface. 32 33 This driver can also be built as a module. If so, the module 34 will be called ad525x_dpot. 35 36config AD525X_DPOT_I2C 37 tristate "support I2C bus connection" 38 depends on AD525X_DPOT && I2C 39 help 40 Say Y here if you have a digital potentiometers hooked to an I2C bus. 41 42 To compile this driver as a module, choose M here: the 43 module will be called ad525x_dpot-i2c. 44 45config AD525X_DPOT_SPI 46 tristate "support SPI bus connection" 47 depends on AD525X_DPOT && SPI_MASTER 48 help 49 Say Y here if you have a digital potentiometers hooked to an SPI bus. 50 51 If unsure, say N (but it's safe to say "Y"). 52 53 To compile this driver as a module, choose M here: the 54 module will be called ad525x_dpot-spi. 55 56config ATMEL_PWM 57 tristate "Atmel AT32/AT91 PWM support" 58 depends on AVR32 || ARCH_AT91SAM9263 || ARCH_AT91SAM9RL || ARCH_AT91CAP9 59 help 60 This option enables device driver support for the PWM channels 61 on certain Atmel processors. Pulse Width Modulation is used for 62 purposes including software controlled power-efficient backlights 63 on LCD displays, motor control, and waveform generation. 64 65config AB8500_PWM 66 bool "AB8500 PWM support" 67 depends on AB8500_CORE 68 select HAVE_PWM 69 help 70 This driver exports functions to enable/disble/config/free Pulse 71 Width Modulation in the Analog Baseband Chip AB8500. 72 It is used by led and backlight driver to control the intensity. 73 74config ATMEL_TCLIB 75 bool "Atmel AT32/AT91 Timer/Counter Library" 76 depends on (AVR32 || ARCH_AT91) 77 help 78 Select this if you want a library to allocate the Timer/Counter 79 blocks found on many Atmel processors. This facilitates using 80 these blocks by different drivers despite processor differences. 81 82config ATMEL_TCB_CLKSRC 83 bool "TC Block Clocksource" 84 depends on ATMEL_TCLIB 85 default y 86 help 87 Select this to get a high precision clocksource based on a 88 TC block with a 5+ MHz base clock rate. Two timer channels 89 are combined to make a single 32-bit timer. 90 91 When GENERIC_CLOCKEVENTS is defined, the third timer channel 92 may be used as a clock event device supporting oneshot mode 93 (delays of up to two seconds) based on the 32 KiHz clock. 94 95config ATMEL_TCB_CLKSRC_BLOCK 96 int 97 depends on ATMEL_TCB_CLKSRC 98 prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X 99 default 0 100 range 0 1 101 help 102 Some chips provide more than one TC block, so you have the 103 choice of which one to use for the clock framework. The other 104 TC can be used for other purposes, such as PWM generation and 105 interval timing. 106 107config IBM_ASM 108 tristate "Device driver for IBM RSA service processor" 109 depends on X86 && PCI && INPUT && EXPERIMENTAL 110 ---help--- 111 This option enables device driver support for in-band access to the 112 IBM RSA (Condor) service processor in eServer xSeries systems. 113 The ibmasm device driver allows user space application to access 114 ASM (Advanced Systems Management) functions on the service 115 processor. The driver is meant to be used in conjunction with 116 a user space API. 117 The ibmasm driver also enables the OS to use the UART on the 118 service processor board as a regular serial port. To make use of 119 this feature serial driver support (CONFIG_SERIAL_8250) must be 120 enabled. 121 122 WARNING: This software may not be supported or function 123 correctly on your IBM server. Please consult the IBM ServerProven 124 website <http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/> 125 for information on the specific driver level and support statement 126 for your IBM server. 127 128config PHANTOM 129 tristate "Sensable PHANToM (PCI)" 130 depends on PCI 131 help 132 Say Y here if you want to build a driver for Sensable PHANToM device. 133 134 This driver is only for PCI PHANToMs. 135 136 If you choose to build module, its name will be phantom. If unsure, 137 say N here. 138 139config SGI_IOC4 140 tristate "SGI IOC4 Base IO support" 141 depends on PCI 142 ---help--- 143 This option enables basic support for the IOC4 chip on certain 144 SGI IO controller cards (IO9, IO10, and PCI-RT). This option 145 does not enable any specific functions on such a card, but provides 146 necessary infrastructure for other drivers to utilize. 147 148 If you have an SGI Altix with an IOC4-based card say Y. 149 Otherwise say N. 150 151config TIFM_CORE 152 tristate "TI Flash Media interface support (EXPERIMENTAL)" 153 depends on EXPERIMENTAL && PCI 154 help 155 If you want support for Texas Instruments(R) Flash Media adapters 156 you should select this option and then also choose an appropriate 157 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter 158 support', if you have a TI PCI74xx compatible card reader, for 159 example. 160 You will also have to select some flash card format drivers. MMC/SD 161 cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD 162 Interface support (MMC_TIFM_SD)'. 163 164 To compile this driver as a module, choose M here: the module will 165 be called tifm_core. 166 167config TIFM_7XX1 168 tristate "TI Flash Media PCI74xx/PCI76xx host adapter support (EXPERIMENTAL)" 169 depends on PCI && TIFM_CORE && EXPERIMENTAL 170 default TIFM_CORE 171 help 172 This option enables support for Texas Instruments(R) PCI74xx and 173 PCI76xx families of Flash Media adapters, found in many laptops. 174 To make actual use of the device, you will have to select some 175 flash card format drivers, as outlined in the TIFM_CORE Help. 176 177 To compile this driver as a module, choose M here: the module will 178 be called tifm_7xx1. 179 180config ICS932S401 181 tristate "Integrated Circuits ICS932S401" 182 depends on I2C && EXPERIMENTAL 183 help 184 If you say yes here you get support for the Integrated Circuits 185 ICS932S401 clock control chips. 186 187 This driver can also be built as a module. If so, the module 188 will be called ics932s401. 189 190config ATMEL_SSC 191 tristate "Device driver for Atmel SSC peripheral" 192 depends on AVR32 || ARCH_AT91 193 ---help--- 194 This option enables device driver support for Atmel Synchronized 195 Serial Communication peripheral (SSC). 196 197 The SSC peripheral supports a wide variety of serial frame based 198 communications, i.e. I2S, SPI, etc. 199 200 If unsure, say N. 201 202config ENCLOSURE_SERVICES 203 tristate "Enclosure Services" 204 default n 205 help 206 Provides support for intelligent enclosures (bays which 207 contain storage devices). You also need either a host 208 driver (SCSI/ATA) which supports enclosures 209 or a SCSI enclosure device (SES) to use these services. 210 211config SGI_XP 212 tristate "Support communication between SGI SSIs" 213 depends on NET 214 depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP 215 select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2 216 select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2 217 select SGI_GRU if X86_64 && SMP 218 ---help--- 219 An SGI machine can be divided into multiple Single System 220 Images which act independently of each other and have 221 hardware based memory protection from the others. Enabling 222 this feature will allow for direct communication between SSIs 223 based on a network adapter and DMA messaging. 224 225config CS5535_MFGPT 226 tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support" 227 depends on PCI 228 depends on X86 229 default n 230 help 231 This driver provides access to MFGPT functionality for other 232 drivers that need timers. MFGPTs are available in the CS5535 and 233 CS5536 companion chips that are found in AMD Geode and several 234 other platforms. They have a better resolution and max interval 235 than the generic PIT, and are suitable for use as high-res timers. 236 You probably don't want to enable this manually; other drivers that 237 make use of it should enable it. 238 239config CS5535_MFGPT_DEFAULT_IRQ 240 int 241 depends on CS5535_MFGPT 242 default 7 243 help 244 MFGPTs on the CS5535 require an interrupt. The selected IRQ 245 can be overridden as a module option as well as by driver that 246 use the cs5535_mfgpt_ API; however, different architectures might 247 want to use a different IRQ by default. This is here for 248 architectures to set as necessary. 249 250config CS5535_CLOCK_EVENT_SRC 251 tristate "CS5535/CS5536 high-res timer (MFGPT) events" 252 depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT 253 help 254 This driver provides a clock event source based on the MFGPT 255 timer(s) in the CS5535 and CS5536 companion chips. 256 MFGPTs have a better resolution and max interval than the 257 generic PIT, and are suitable for use as high-res timers. 258 259config HP_ILO 260 tristate "Channel interface driver for the HP iLO processor" 261 depends on PCI 262 default n 263 help 264 The channel interface driver allows applications to communicate 265 with iLO management processors present on HP ProLiant servers. 266 Upon loading, the driver creates /dev/hpilo/dXccbN files, which 267 can be used to gather data from the management processor, via 268 read and write system calls. 269 270 To compile this driver as a module, choose M here: the 271 module will be called hpilo. 272 273config SGI_GRU 274 tristate "SGI GRU driver" 275 depends on X86_UV && SMP 276 default n 277 select MMU_NOTIFIER 278 ---help--- 279 The GRU is a hardware resource located in the system chipset. The GRU 280 contains memory that can be mmapped into the user address space. This memory is 281 used to communicate with the GRU to perform functions such as load/store, 282 scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user 283 instructions using user virtual addresses. GRU instructions (ex., bcopy) use 284 user virtual addresses for operands. 285 286 If you are not running on a SGI UV system, say N. 287 288config SGI_GRU_DEBUG 289 bool "SGI GRU driver debug" 290 depends on SGI_GRU 291 default n 292 ---help--- 293 This option enables addition debugging code for the SGI GRU driver. If 294 you are unsure, say N. 295 296config APDS9802ALS 297 tristate "Medfield Avago APDS9802 ALS Sensor module" 298 depends on I2C 299 help 300 If you say yes here you get support for the ALS APDS9802 ambient 301 light sensor. 302 303 This driver can also be built as a module. If so, the module 304 will be called apds9802als. 305 306config ISL29003 307 tristate "Intersil ISL29003 ambient light sensor" 308 depends on I2C && SYSFS 309 help 310 If you say yes here you get support for the Intersil ISL29003 311 ambient light sensor. 312 313 This driver can also be built as a module. If so, the module 314 will be called isl29003. 315 316config ISL29020 317 tristate "Intersil ISL29020 ambient light sensor" 318 depends on I2C 319 help 320 If you say yes here you get support for the Intersil ISL29020 321 ambient light sensor. 322 323 This driver can also be built as a module. If so, the module 324 will be called isl29020. 325 326config SENSORS_TSL2550 327 tristate "Taos TSL2550 ambient light sensor" 328 depends on I2C && SYSFS 329 help 330 If you say yes here you get support for the Taos TSL2550 331 ambient light sensor. 332 333 This driver can also be built as a module. If so, the module 334 will be called tsl2550. 335 336config SENSORS_BH1780 337 tristate "ROHM BH1780GLI ambient light sensor" 338 depends on I2C && SYSFS 339 help 340 If you say yes here you get support for the ROHM BH1780GLI 341 ambient light sensor. 342 343 This driver can also be built as a module. If so, the module 344 will be called bh1780gli. 345 346config SENSORS_BH1770 347 tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor" 348 depends on I2C 349 ---help--- 350 Say Y here if you want to build a driver for BH1770GLC (ROHM) or 351 SFH7770 (Osram) combined ambient light and proximity sensor chip. 352 353 To compile this driver as a module, choose M here: the 354 module will be called bh1770glc. If unsure, say N here. 355 356config SENSORS_APDS990X 357 tristate "APDS990X combined als and proximity sensors" 358 depends on I2C 359 default n 360 ---help--- 361 Say Y here if you want to build a driver for Avago APDS990x 362 combined ambient light and proximity sensor chip. 363 364 To compile this driver as a module, choose M here: the 365 module will be called apds990x. If unsure, say N here. 366 367config HMC6352 368 tristate "Honeywell HMC6352 compass" 369 depends on I2C 370 help 371 This driver provides support for the Honeywell HMC6352 compass, 372 providing configuration and heading data via sysfs. 373 374config EP93XX_PWM 375 tristate "EP93xx PWM support" 376 depends on ARCH_EP93XX 377 help 378 This option enables device driver support for the PWM channels 379 on the Cirrus EP93xx processors. The EP9307 chip only has one 380 PWM channel all the others have two, the second channel is an 381 alternate function of the EGPIO14 pin. A sysfs interface is 382 provided to control the PWM channels. 383 384 To compile this driver as a module, choose M here: the module will 385 be called ep93xx_pwm. 386 387config DS1682 388 tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm" 389 depends on I2C && EXPERIMENTAL 390 help 391 If you say yes here you get support for Dallas Semiconductor 392 DS1682 Total Elapsed Time Recorder. 393 394 This driver can also be built as a module. If so, the module 395 will be called ds1682. 396 397config TI_DAC7512 398 tristate "Texas Instruments DAC7512" 399 depends on SPI && SYSFS 400 help 401 If you say yes here you get support for the Texas Instruments 402 DAC7512 16-bit digital-to-analog converter. 403 404 This driver can also be built as a module. If so, the module 405 will be calles ti_dac7512. 406 407config VMWARE_BALLOON 408 tristate "VMware Balloon Driver" 409 depends on X86 410 help 411 This is VMware physical memory management driver which acts 412 like a "balloon" that can be inflated to reclaim physical pages 413 by reserving them in the guest and invalidating them in the 414 monitor, freeing up the underlying machine pages so they can 415 be allocated to other guests. The balloon can also be deflated 416 to allow the guest to use more physical memory. 417 418 If unsure, say N. 419 420 To compile this driver as a module, choose M here: the 421 module will be called vmw_balloon. 422 423config ARM_CHARLCD 424 bool "ARM Ltd. Character LCD Driver" 425 depends on PLAT_VERSATILE 426 help 427 This is a driver for the character LCD found on the ARM Ltd. 428 Versatile and RealView Platform Baseboards. It doesn't do 429 very much more than display the text "ARM Linux" on the first 430 line and the Linux version on the second line, but that's 431 still useful. 432 433config BMP085 434 tristate "BMP085 digital pressure sensor" 435 depends on I2C && SYSFS 436 help 437 If you say yes here you get support for the Bosch Sensortec 438 BMP085 digital pressure sensor. 439 440 To compile this driver as a module, choose M here: the 441 module will be called bmp085. 442 443config PCH_PHUB 444 tristate "PCH Packet Hub of Intel Topcliff" 445 depends on PCI 446 help 447 This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of 448 Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded 449 processor. The Topcliff has MAC address and Option ROM data in SROM. 450 This driver can access MAC address and Option ROM data in SROM. 451 452 To compile this driver as a module, choose M here: the module will 453 be called pch_phub. 454 455source "drivers/misc/c2port/Kconfig" 456source "drivers/misc/eeprom/Kconfig" 457source "drivers/misc/cb710/Kconfig" 458source "drivers/misc/iwmc3200top/Kconfig" 459source "drivers/misc/ti-st/Kconfig" 460 461endif # MISC_DEVICES 462