drivers/misc/Kconfig

   1 #
   2 # Misc strange devices
   3 #
   4
   5 menu "Misc devices"
   6
   7 config SENSORS_LIS3LV02D
   8         tristate
   9         depends on INPUT
  10         select INPUT_POLLDEV
  11         default n
  12
  13 config BCM2835_SMI
  14         tristate "Broadcom 283x Secondary Memory Interface driver"
  15         depends on ARCH_BCM2835
  16         default m
  17         help
  18                 Driver for enabling and using Broadcom's Secondary/Slow Memory Interface.
  19                 Appears as /dev/bcm2835_smi. For ioctl interface see drivers/misc/bcm2835_smi.h
  20
  21 config AD525X_DPOT
  22         tristate "Analog Devices Digital Potentiometers"
  23         depends on (I2C || SPI) && SYSFS
  24         help
  25           If you say yes here, you get support for the Analog Devices
  26           AD5258, AD5259, AD5251, AD5252, AD5253, AD5254, AD5255
  27           AD5160, AD5161, AD5162, AD5165, AD5200, AD5201, AD5203,
  28           AD5204, AD5206, AD5207, AD5231, AD5232, AD5233, AD5235,
  29           AD5260, AD5262, AD5263, AD5290, AD5291, AD5292, AD5293,
  30           AD7376, AD8400, AD8402, AD8403, ADN2850, AD5241, AD5242,
  31           AD5243, AD5245, AD5246, AD5247, AD5248, AD5280, AD5282,
  32           ADN2860, AD5273, AD5171, AD5170, AD5172, AD5173, AD5270,
  33           AD5271, AD5272, AD5274
  34           digital potentiometer chips.
  35
  36           See Documentation/misc-devices/ad525x_dpot.txt for the
  37           userspace interface.
  38
  39           This driver can also be built as a module.  If so, the module
  40           will be called ad525x_dpot.
  41
  42 config AD525X_DPOT_I2C
  43         tristate "support I2C bus connection"
  44         depends on AD525X_DPOT && I2C
  45         help
  46           Say Y here if you have a digital potentiometers hooked to an I2C bus.
  47
  48           To compile this driver as a module, choose M here: the
  49           module will be called ad525x_dpot-i2c.
  50
  51 config AD525X_DPOT_SPI
  52         tristate "support SPI bus connection"
  53         depends on AD525X_DPOT && SPI_MASTER
  54         help
  55           Say Y here if you have a digital potentiometers hooked to an SPI bus.
  56
  57           If unsure, say N (but it's safe to say "Y").
  58
  59           To compile this driver as a module, choose M here: the
  60           module will be called ad525x_dpot-spi.
  61
  62 config ATMEL_TCLIB
  63         bool "Atmel AT32/AT91 Timer/Counter Library"
  64         depends on (AVR32 || ARCH_AT91)
  65         help
  66           Select this if you want a library to allocate the Timer/Counter
  67           blocks found on many Atmel processors.  This facilitates using
  68           these blocks by different drivers despite processor differences.
  69
  70 config ATMEL_TCB_CLKSRC
  71         bool "TC Block Clocksource"
  72         depends on ATMEL_TCLIB
  73         default y
  74         help
  75           Select this to get a high precision clocksource based on a
  76           TC block with a 5+ MHz base clock rate.  Two timer channels
  77           are combined to make a single 32-bit timer.
  78
  79           When GENERIC_CLOCKEVENTS is defined, the third timer channel
  80           may be used as a clock event device supporting oneshot mode
  81           (delays of up to two seconds) based on the 32 KiHz clock.
  82
  83 config ATMEL_TCB_CLKSRC_BLOCK
  84         int
  85         depends on ATMEL_TCB_CLKSRC
  86         prompt "TC Block" if CPU_AT32AP700X
  87         default 0
  88         range 0 1
  89         help
  90           Some chips provide more than one TC block, so you have the
  91           choice of which one to use for the clock framework.  The other
  92           TC can be used for other purposes, such as PWM generation and
  93           interval timing.
  94
  95 config DUMMY_IRQ
  96         tristate "Dummy IRQ handler"
  97         default n
  98         ---help---
  99           This module accepts a single 'irq' parameter, which it should register for.
 100           The sole purpose of this module is to help with debugging of systems on
 101           which spurious IRQs would happen on disabled IRQ vector.
 102
 103 config IBM_ASM
 104         tristate "Device driver for IBM RSA service processor"
 105         depends on X86 && PCI && INPUT
 106         depends on SERIAL_8250 || SERIAL_8250=n
 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
 125 config 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
 136 config INTEL_MID_PTI
 137         tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard"
 138         depends on PCI && TTY && (X86_INTEL_MID || COMPILE_TEST)
 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
 150 config 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
 162 config 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
 178 config 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
 191 config 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
 201 config ATMEL_SSC
 202         tristate "Device driver for Atmel SSC peripheral"
 203         depends on HAS_IOMEM && (AVR32 || ARCH_AT91 || COMPILE_TEST)
 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
 213 config 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
 222 config 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
 236 config CS5535_MFGPT
 237         tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
 238         depends on 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
 249 config 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
 260 config 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
 269 config 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
 283 config QCOM_COINCELL
 284         tristate "Qualcomm coincell charger support"
 285         depends on MFD_SPMI_PMIC || COMPILE_TEST
 286         help
 287           This driver supports the coincell block found inside of
 288           Qualcomm PMICs.  The coincell charger provides a means to
 289           charge a coincell battery or backup capacitor which is used
 290           to maintain PMIC register and RTC state in the absence of
 291           external power.
 292
 293 config SGI_GRU
 294         tristate "SGI GRU driver"
 295         depends on X86_UV && SMP
 296         default n
 297         select MMU_NOTIFIER
 298         ---help---
 299         The GRU is a hardware resource located in the system chipset. The GRU
 300         contains memory that can be mmapped into the user address space. This memory is
 301         used to communicate with the GRU to perform functions such as load/store,
 302         scatter/gather, bcopy, AMOs, etc.  The GRU is directly accessed by user
 303         instructions using user virtual addresses. GRU instructions (ex., bcopy) use
 304         user virtual addresses for operands.
 305
 306         If you are not running on a SGI UV system, say N.
 307
 308 config SGI_GRU_DEBUG
 309         bool  "SGI GRU driver debug"
 310         depends on SGI_GRU
 311         default n
 312         ---help---
 313         This option enables additional debugging code for the SGI GRU driver.
 314         If you are unsure, say N.
 315
 316 config APDS9802ALS
 317         tristate "Medfield Avago APDS9802 ALS Sensor module"
 318         depends on I2C
 319         help
 320           If you say yes here you get support for the ALS APDS9802 ambient
 321           light sensor.
 322
 323           This driver can also be built as a module.  If so, the module
 324           will be called apds9802als.
 325
 326 config ISL29003
 327         tristate "Intersil ISL29003 ambient light sensor"
 328         depends on I2C && SYSFS
 329         help
 330           If you say yes here you get support for the Intersil ISL29003
 331           ambient light sensor.
 332
 333           This driver can also be built as a module.  If so, the module
 334           will be called isl29003.
 335
 336 config ISL29020
 337         tristate "Intersil ISL29020 ambient light sensor"
 338         depends on I2C
 339         help
 340           If you say yes here you get support for the Intersil ISL29020
 341           ambient light sensor.
 342
 343           This driver can also be built as a module.  If so, the module
 344           will be called isl29020.
 345
 346 config SENSORS_TSL2550
 347         tristate "Taos TSL2550 ambient light sensor"
 348         depends on I2C && SYSFS
 349         help
 350           If you say yes here you get support for the Taos TSL2550
 351           ambient light sensor.
 352
 353           This driver can also be built as a module.  If so, the module
 354           will be called tsl2550.
 355
 356 config 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
 366 config 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
 377 config 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
 384 config DS1682
 385         tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
 386         depends on I2C
 387         help
 388           If you say yes here you get support for Dallas Semiconductor
 389           DS1682 Total Elapsed Time Recorder.
 390
 391           This driver can also be built as a module.  If so, the module
 392           will be called ds1682.
 393
 394 config SPEAR13XX_PCIE_GADGET
 395         bool "PCIe gadget support for SPEAr13XX platform"
 396         depends on ARCH_SPEAR13XX && BROKEN
 397         default n
 398         help
 399          This option enables gadget support for PCIe controller. If
 400          board file defines any controller as PCIe endpoint then a sysfs
 401          entry will be created for that controller. User can use these
 402          sysfs node to configure PCIe EP as per his requirements.
 403
 404 config TI_DAC7512
 405         tristate "Texas Instruments DAC7512"
 406         depends on SPI && SYSFS
 407         help
 408           If you say yes here you get support for the Texas Instruments
 409           DAC7512 16-bit digital-to-analog converter.
 410
 411           This driver can also be built as a module. If so, the module
 412           will be called ti_dac7512.
 413
 414 config VMWARE_BALLOON
 415         tristate "VMware Balloon Driver"
 416         depends on VMWARE_VMCI && X86 && HYPERVISOR_GUEST
 417         help
 418           This is VMware physical memory management driver which acts
 419           like a "balloon" that can be inflated to reclaim physical pages
 420           by reserving them in the guest and invalidating them in the
 421           monitor, freeing up the underlying machine pages so they can
 422           be allocated to other guests. The balloon can also be deflated
 423           to allow the guest to use more physical memory.
 424
 425           If unsure, say N.
 426
 427           To compile this driver as a module, choose M here: the
 428           module will be called vmw_balloon.
 429
 430 config PCH_PHUB
 431         tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
 432         select GENERIC_NET_UTILS
 433         depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
 434         help
 435           This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
 436           Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
 437           processor. The Topcliff has MAC address and Option ROM data in SROM.
 438           This driver can access MAC address and Option ROM data in SROM.
 439
 440           This driver also can be used for LAPIS Semiconductor's IOH,
 441           ML7213/ML7223/ML7831.
 442           ML7213 which is for IVI(In-Vehicle Infotainment) use.
 443           ML7223 IOH is for MP(Media Phone) use.
 444           ML7831 IOH is for general purpose use.
 445           ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
 446           ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
 447
 448           To compile this driver as a module, choose M here: the module will
 449           be called pch_phub.
 450
 451 config USB_SWITCH_FSA9480
 452         tristate "FSA9480 USB Switch"
 453         depends on I2C
 454         help
 455           The FSA9480 is a USB port accessory detector and switch.
 456           The FSA9480 is fully controlled using I2C and enables USB data,
 457           stereo and mono audio, video, microphone and UART data to use
 458           a common connector port.
 459
 460 config LATTICE_ECP3_CONFIG
 461         tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
 462         depends on SPI && SYSFS
 463         select FW_LOADER
 464         default n
 465         help
 466           This option enables support for bitstream configuration (programming
 467           or loading) of the Lattice ECP3 FPGA family via SPI.
 468
 469           If unsure, say N.
 470
 471 config SRAM
 472         bool "Generic on-chip SRAM driver"
 473         depends on HAS_IOMEM
 474         select GENERIC_ALLOCATOR
 475         select SRAM_EXEC if ARM
 476         help
 477           This driver allows you to declare a memory region to be managed by
 478           the genalloc API. It is supposed to be used for small on-chip SRAM
 479           areas found on many SoCs.
 480
 481 config SRAM_EXEC
 482         bool
 483
 484 config VEXPRESS_SYSCFG
 485         bool "Versatile Express System Configuration driver"
 486         depends on VEXPRESS_CONFIG
 487         default y
 488         help
 489           ARM Ltd. Versatile Express uses specialised platform configuration
 490           bus. System Configuration interface is one of the possible means
 491           of generating transactions on this bus.
 492
 493 config ASPEED_LPC_CTRL
 494         depends on (ARCH_ASPEED || COMPILE_TEST) && REGMAP && MFD_SYSCON
 495         tristate "Aspeed ast2400/2500 HOST LPC to BMC bridge control"
 496         ---help---
 497           Control Aspeed ast2400/2500 HOST LPC to BMC mappings through
 498           ioctl()s, the driver also provides a read/write interface to a BMC ram
 499           region where the host LPC read/write region can be buffered.
 500
 501 config ASPEED_LPC_SNOOP
 502         tristate "Aspeed ast2500 HOST LPC snoop support"
 503         depends on (ARCH_ASPEED || COMPILE_TEST) && REGMAP && MFD_SYSCON
 504         help
 505           Provides a driver to control the LPC snoop interface which
 506           allows the BMC to listen on and save the data written by
 507           the host to an arbitrary LPC I/O port.
 508
 509 config PCI_ENDPOINT_TEST
 510         depends on PCI
 511         select CRC32
 512         tristate "PCI Endpoint Test driver"
 513         ---help---
 514            Enable this configuration option to enable the host side test driver
 515            for PCI Endpoint.
 516
 517 source "drivers/misc/c2port/Kconfig"
 518 source "drivers/misc/eeprom/Kconfig"
 519 source "drivers/misc/cb710/Kconfig"
 520 source "drivers/misc/ti-st/Kconfig"
 521 source "drivers/misc/lis3lv02d/Kconfig"
 522 source "drivers/misc/altera-stapl/Kconfig"
 523 source "drivers/misc/mei/Kconfig"
 524 source "drivers/misc/vmw_vmci/Kconfig"
 525 source "drivers/misc/mic/Kconfig"
 526 source "drivers/misc/genwqe/Kconfig"
 527 source "drivers/misc/echo/Kconfig"
 528 source "drivers/misc/cxl/Kconfig"
 529 endmenu