LXR linux/drivers/misc/Kconfig

   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 Digital Potentiometers"
  18        depends on (I2C || SPI) && SYSFS
  19        help
  20          If you say yes here, you get support for the Analog Devices
  21          AD5258, AD5259, AD5251, AD5252, AD5253, AD5254, AD5255
  22          AD5160, AD5161, AD5162, AD5165, AD5200, AD5201, AD5203,
  23          AD5204, AD5206, AD5207, AD5231, AD5232, AD5233, AD5235,
  24          AD5260, AD5262, AD5263, AD5290, AD5291, AD5292, AD5293,
  25          AD7376, AD8400, AD8402, AD8403, ADN2850, AD5241, AD5242,
  26          AD5243, AD5245, AD5246, AD5247, AD5248, AD5280, AD5282,
  27          ADN2860, AD5273, AD5171, AD5170, AD5172, AD5173
  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 ATMEL_TCLIB
  66        bool "Atmel AT32/AT91 Timer/Counter Library"
  67        depends on (AVR32 || ARCH_AT91)
  68        help
  69          Select this if you want a library to allocate the Timer/Counter
  70          blocks found on many Atmel processors.  This facilitates using
  71          these blocks by different drivers despite processor differences.
  72
  73config ATMEL_TCB_CLKSRC
  74        bool "TC Block Clocksource"
  75        depends on ATMEL_TCLIB && GENERIC_TIME
  76        default y
  77        help
  78          Select this to get a high precision clocksource based on a
  79          TC block with a 5+ MHz base clock rate.  Two timer channels
  80          are combined to make a single 32-bit timer.
  81
  82          When GENERIC_CLOCKEVENTS is defined, the third timer channel
  83          may be used as a clock event device supporting oneshot mode
  84          (delays of up to two seconds) based on the 32 KiHz clock.
  85
  86config ATMEL_TCB_CLKSRC_BLOCK
  87        int
  88        depends on ATMEL_TCB_CLKSRC
  89        prompt "TC Block" if ARCH_AT91RM9200 || ARCH_AT91SAM9260 || CPU_AT32AP700X
  90        default 0
  91        range 0 1
  92        help
  93          Some chips provide more than one TC block, so you have the
  94          choice of which one to use for the clock framework.  The other
  95          TC can be used for other purposes, such as PWM generation and
  96          interval timing.
  97
  98config IBM_ASM
  99        tristate "Device driver for IBM RSA service processor"
 100        depends on X86 && PCI && INPUT && EXPERIMENTAL
 101        ---help---
 102          This option enables device driver support for in-band access to the
 103          IBM RSA (Condor) service processor in eServer xSeries systems.
 104          The ibmasm device driver allows user space application to access
 105          ASM (Advanced Systems Management) functions on the service
 106          processor. The driver is meant to be used in conjunction with
 107          a user space API.
 108          The ibmasm driver also enables the OS to use the UART on the
 109          service processor board as a regular serial port. To make use of
 110          this feature serial driver support (CONFIG_SERIAL_8250) must be
 111          enabled.
 112
 113          WARNING: This software may not be supported or function
 114          correctly on your IBM server. Please consult the IBM ServerProven
 115          website <http://www.pc.ibm.com/ww/eserver/xseries/serverproven> for
 116          information on the specific driver level and support statement
 117          for your IBM server.
 118
 119config PHANTOM
 120        tristate "Sensable PHANToM (PCI)"
 121        depends on PCI
 122        help
 123          Say Y here if you want to build a driver for Sensable PHANToM device.
 124
 125          This driver is only for PCI PHANToMs.
 126
 127          If you choose to build module, its name will be phantom. If unsure,
 128          say N here.
 129
 130config SGI_IOC4
 131        tristate "SGI IOC4 Base IO support"
 132        depends on PCI
 133        ---help---
 134          This option enables basic support for the IOC4 chip on certain
 135          SGI IO controller cards (IO9, IO10, and PCI-RT).  This option
 136          does not enable any specific functions on such a card, but provides
 137          necessary infrastructure for other drivers to utilize.
 138
 139          If you have an SGI Altix with an IOC4-based card say Y.
 140          Otherwise say N.
 141
 142config TIFM_CORE
 143        tristate "TI Flash Media interface support (EXPERIMENTAL)"
 144        depends on EXPERIMENTAL && PCI
 145        help
 146          If you want support for Texas Instruments(R) Flash Media adapters
 147          you should select this option and then also choose an appropriate
 148          host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
 149          support', if you have a TI PCI74xx compatible card reader, for
 150          example.
 151          You will also have to select some flash card format drivers. MMC/SD
 152          cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
 153          Interface support (MMC_TIFM_SD)'.
 154
 155          To compile this driver as a module, choose M here: the module will
 156          be called tifm_core.
 157
 158config TIFM_7XX1
 159        tristate "TI Flash Media PCI74xx/PCI76xx host adapter support (EXPERIMENTAL)"
 160        depends on PCI && TIFM_CORE && EXPERIMENTAL
 161        default TIFM_CORE
 162        help
 163          This option enables support for Texas Instruments(R) PCI74xx and
 164          PCI76xx families of Flash Media adapters, found in many laptops.
 165          To make actual use of the device, you will have to select some
 166          flash card format drivers, as outlined in the TIFM_CORE Help.
 167
 168          To compile this driver as a module, choose M here: the module will
 169          be called tifm_7xx1.
 170
 171config ICS932S401
 172        tristate "Integrated Circuits ICS932S401"
 173        depends on I2C && EXPERIMENTAL
 174        help
 175          If you say yes here you get support for the Integrated Circuits
 176          ICS932S401 clock control chips.
 177
 178          This driver can also be built as a module. If so, the module
 179          will be called ics932s401.
 180
 181config ATMEL_SSC
 182        tristate "Device driver for Atmel SSC peripheral"
 183        depends on AVR32 || ARCH_AT91
 184        ---help---
 185          This option enables device driver support for Atmel Synchronized
 186          Serial Communication peripheral (SSC).
 187
 188          The SSC peripheral supports a wide variety of serial frame based
 189          communications, i.e. I2S, SPI, etc.
 190
 191          If unsure, say N.
 192
 193config ENCLOSURE_SERVICES
 194        tristate "Enclosure Services"
 195        default n
 196        help
 197          Provides support for intelligent enclosures (bays which
 198          contain storage devices).  You also need either a host
 199          driver (SCSI/ATA) which supports enclosures
 200          or a SCSI enclosure device (SES) to use these services.
 201
 202config SGI_XP
 203        tristate "Support communication between SGI SSIs"
 204        depends on NET
 205        depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP
 206        select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
 207        select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
 208        select SGI_GRU if X86_64 && SMP
 209        ---help---
 210          An SGI machine can be divided into multiple Single System
 211          Images which act independently of each other and have
 212          hardware based memory protection from the others.  Enabling
 213          this feature will allow for direct communication between SSIs
 214          based on a network adapter and DMA messaging.
 215
 216config CS5535_MFGPT
 217        tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
 218        depends on PCI
 219        depends on X86
 220        default n
 221        help
 222          This driver provides access to MFGPT functionality for other
 223          drivers that need timers.  MFGPTs are available in the CS5535 and
 224          CS5536 companion chips that are found in AMD Geode and several
 225          other platforms.  They have a better resolution and max interval
 226          than the generic PIT, and are suitable for use as high-res timers.
 227          You probably don't want to enable this manually; other drivers that
 228          make use of it should enable it.
 229
 230config CS5535_MFGPT_DEFAULT_IRQ
 231        int
 232        depends on CS5535_MFGPT
 233        default 7
 234        help
 235          MFGPTs on the CS5535 require an interrupt.  The selected IRQ
 236          can be overridden as a module option as well as by driver that
 237          use the cs5535_mfgpt_ API; however, different architectures might
 238          want to use a different IRQ by default.  This is here for
 239          architectures to set as necessary.
 240
 241config CS5535_CLOCK_EVENT_SRC
 242        tristate "CS5535/CS5536 high-res timer (MFGPT) events"
 243        depends on GENERIC_TIME && GENERIC_CLOCKEVENTS && CS5535_MFGPT
 244        help
 245          This driver provides a clock event source based on the MFGPT
 246          timer(s) in the CS5535 and CS5536 companion chips.
 247          MFGPTs have a better resolution and max interval than the
 248          generic PIT, and are suitable for use as high-res timers.
 249
 250config HP_ILO
 251        tristate "Channel interface driver for HP iLO/iLO2 processor"
 252        depends on PCI
 253        default n
 254        help
 255          The channel interface driver allows applications to communicate
 256          with iLO/iLO2 management processors present on HP ProLiant
 257          servers.  Upon loading, the driver creates /dev/hpilo/dXccbN files,
 258          which can be used to gather data from the management processor,
 259          via read and write system calls.
 260
 261          To compile this driver as a module, choose M here: the
 262          module will be called hpilo.
 263
 264config SGI_GRU
 265        tristate "SGI GRU driver"
 266        depends on X86_UV && SMP
 267        default n
 268        select MMU_NOTIFIER
 269        ---help---
 270        The GRU is a hardware resource located in the system chipset. The GRU
 271        contains memory that can be mmapped into the user address space. This memory is
 272        used to communicate with the GRU to perform functions such as load/store,
 273        scatter/gather, bcopy, AMOs, etc.  The GRU is directly accessed by user
 274        instructions using user virtual addresses. GRU instructions (ex., bcopy) use
 275        user virtual addresses for operands.
 276
 277        If you are not running on a SGI UV system, say N.
 278
 279config SGI_GRU_DEBUG
 280        bool  "SGI GRU driver debug"
 281        depends on SGI_GRU
 282        default n
 283        ---help---
 284        This option enables addition debugging code for the SGI GRU driver. If
 285        you are unsure, say N.
 286
 287config ISL29003
 288        tristate "Intersil ISL29003 ambient light sensor"
 289        depends on I2C && SYSFS
 290        help
 291          If you say yes here you get support for the Intersil ISL29003
 292          ambient light sensor.
 293
 294          This driver can also be built as a module.  If so, the module
 295          will be called isl29003.
 296
 297config SENSORS_TSL2550
 298        tristate "Taos TSL2550 ambient light sensor"
 299        depends on I2C && SYSFS
 300        help
 301          If you say yes here you get support for the Taos TSL2550
 302          ambient light sensor.
 303
 304          This driver can also be built as a module.  If so, the module
 305          will be called tsl2550.
 306
 307config EP93XX_PWM
 308        tristate "EP93xx PWM support"
 309        depends on ARCH_EP93XX
 310        help
 311          This option enables device driver support for the PWM channels
 312          on the Cirrus EP93xx processors.  The EP9307 chip only has one
 313          PWM channel all the others have two, the second channel is an
 314          alternate function of the EGPIO14 pin.  A sysfs interface is
 315          provided to control the PWM channels.
 316
 317          To compile this driver as a module, choose M here: the module will
 318          be called ep93xx_pwm.
 319
 320config DS1682
 321        tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
 322        depends on I2C && EXPERIMENTAL
 323        help
 324          If you say yes here you get support for Dallas Semiconductor
 325          DS1682 Total Elapsed Time Recorder.
 326
 327          This driver can also be built as a module.  If so, the module
 328          will be called ds1682.
 329
 330config TI_DAC7512
 331        tristate "Texas Instruments DAC7512"
 332        depends on SPI && SYSFS
 333        help
 334          If you say yes here you get support for the Texas Instruments
 335          DAC7512 16-bit digital-to-analog converter.
 336
 337          This driver can also be built as a module. If so, the module
 338          will be calles ti_dac7512.
 339
 340config VMWARE_BALLOON
 341        tristate "VMware Balloon Driver"
 342        depends on X86
 343        help
 344          This is VMware physical memory management driver which acts
 345          like a "balloon" that can be inflated to reclaim physical pages
 346          by reserving them in the guest and invalidating them in the
 347          monitor, freeing up the underlying machine pages so they can
 348          be allocated to other guests. The balloon can also be deflated
 349          to allow the guest to use more physical memory.
 350
 351          If unsure, say N.
 352
 353          To compile this driver as a module, choose M here: the
 354          module will be called vmware_balloon.
 355
 356source "drivers/misc/c2port/Kconfig"
 357source "drivers/misc/eeprom/Kconfig"
 358source "drivers/misc/cb710/Kconfig"
 359source "drivers/misc/iwmc3200top/Kconfig"
 360
 361endif # MISC_DEVICES
 362