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