drivers/misc/Kconfig

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