# SPDX-License-Identifier: GPL-2.0-only
#
# Misc strange devices
#
menu "Misc devices"
config [31mCONFIG_SENSORS_LIS3LV02D[0m
tristate
depends on [31mCONFIG_INPUT[0m
select [31mCONFIG_INPUT_POLLDEV[0m
config [31mCONFIG_AD525X_DPOT[0m
tristate "Analog Devices Digital Potentiometers"
depends on ([31mCONFIG_I2C[0m || [31mCONFIG_SPI[0m) && [31mCONFIG_SYSFS[0m
help
If you say yes here, you get support for the Analog Devices
AD5258, AD5259, AD5251, AD5252, AD5253, AD5254, AD5255
AD5160, AD5161, AD5162, AD5165, AD5200, AD5201, AD5203,
AD5204, AD5206, AD5207, AD5231, AD5232, AD5233, AD5235,
AD5260, AD5262, AD5263, AD5290, AD5291, AD5292, AD5293,
AD7376, AD8400, AD8402, AD8403, ADN2850, AD5241, AD5242,
AD5243, AD5245, AD5246, AD5247, AD5248, AD5280, AD5282,
ADN2860, AD5273, AD5171, AD5170, AD5172, AD5173, AD5270,
AD5271, [31mCONFIG_AD5272[0m, AD5274
digital potentiometer chips.
See Documentation/misc-devices/ad525x_dpot.txt for the
userspace interface.
This driver can also be built as a module. If so, the module
will be called ad525x_dpot.
config [31mCONFIG_AD525X_DPOT_I2C[0m
tristate "support I2C bus connection"
depends on [31mCONFIG_AD525X_DPOT[0m && [31mCONFIG_I2C[0m
help
Say Y here if you have a digital potentiometers hooked to an [31mCONFIG_I2C[0m bus.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called ad525x_dpot-i2c.
config [31mCONFIG_AD525X_DPOT_SPI[0m
tristate "support SPI bus connection"
depends on [31mCONFIG_AD525X_DPOT[0m && [31mCONFIG_SPI_MASTER[0m
help
Say Y here if you have a digital potentiometers hooked to an [31mCONFIG_SPI[0m bus.
If unsure, say N (but it's safe to say "Y").
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called ad525x_dpot-spi.
config [31mCONFIG_ATMEL_TCLIB[0m
bool "Atmel AT32/AT91 Timer/Counter Library"
depends on [31mCONFIG_ARCH_AT91[0m
help
Select this if you want a library to allocate the Timer/Counter
blocks found on many Atmel processors. This facilitates using
these blocks by different drivers despite processor differences.
config [31mCONFIG_DUMMY_IRQ[0m
tristate "Dummy IRQ handler"
---help---
This module accepts a single 'irq' parameter, which it should register for.
The sole purpose of this module is to help with debugging of systems on
which spurious IRQs would happen on disabled IRQ vector.
config [31mCONFIG_IBM_ASM[0m
tristate "Device driver for IBM RSA service processor"
depends on [31mCONFIG_X86[0m && [31mCONFIG_PCI[0m && [31mCONFIG_INPUT[0m
depends on [31mCONFIG_SERIAL_8250[0m || [31mCONFIG_SERIAL_8250[0m=n
---help---
This option enables device driver support for in-band access to the
IBM RSA (Condor) service processor in eServer xSeries systems.
The ibmasm device driver allows user space application to access
ASM (Advanced Systems Management) functions on the service
processor. The driver is meant to be used in conjunction with
a user space API.
The ibmasm driver also enables the OS to use the UART on the
service processor board as a regular serial port. To make use of
this feature serial driver support (CONFIG_SERIAL_8250) must be
enabled.
WARNING: This software may not be supported or function
correctly on your IBM server. Please consult the IBM ServerProven
website <http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>
for information on the specific driver level and support statement
for your IBM server.
config [31mCONFIG_IBMVMC[0m
tristate "IBM Virtual Management Channel support"
depends on [31mCONFIG_PPC_PSERIES[0m
help
This is the IBM POWER Virtual Management Channel
This driver is to be used for the POWER Virtual
Management Channel virtual adapter on the PowerVM
platform. It provides both request/response and
async message support through the /dev/ibmvmc node.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called ibmvmc.
config [31mCONFIG_PHANTOM[0m
tristate "Sensable PHANToM (PCI)"
depends on [31mCONFIG_PCI[0m
help
Say Y here if you want to build a driver for Sensable PHANToM device.
This driver is only for [31mCONFIG_PCI[0m PHANToMs.
If you choose to build module, its name will be phantom. If unsure,
say N here.
config [31mCONFIG_INTEL_MID_PTI[0m
tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_TTY[0m && ([31mCONFIG_X86_INTEL_MID[0m || [31mCONFIG_COMPILE_TEST[0m)
help
The PTI (Parallel Trace Interface) driver directs
trace data routed from various parts in the system out
through an Intel Penwell PTI port and out of the mobile
device for analysis with a debugging tool (Lauterbach or Fido).
You should select this driver if the target kernel is meant for
an Intel Atom (non-netbook) mobile device containing a MIPI
P1149.7 standard implementation.
config [31mCONFIG_TIFM_CORE[0m
tristate "TI Flash Media interface support"
depends on [31mCONFIG_PCI[0m
help
If you want support for Texas Instruments(R) Flash Media adapters
you should select this option and then also choose an appropriate
host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
support', if you have a TI PCI74xx compatible card reader, for
example.
You will also have to select some flash card format drivers. [31mCONFIG_MMC[0m/SD
cards are supported via '[31mCONFIG_MMC[0m/SD Card support: TI Flash Media [31mCONFIG_MMC[0m/SD
Interface support ([31mCONFIG_MMC_TIFM_SD[0m)'.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module will
be called tifm_core.
config [31mCONFIG_TIFM_7XX1[0m
tristate "TI Flash Media PCI74xx/PCI76xx host adapter support"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_TIFM_CORE[0m
default [31mCONFIG_TIFM_CORE[0m
help
This option enables support for Texas Instruments(R) PCI74xx and
PCI76xx families of Flash Media adapters, found in many laptops.
To make actual use of the device, you will have to select some
flash card format drivers, as outlined in the [31mCONFIG_TIFM_CORE[0m Help.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module will
be called tifm_7xx1.
config [31mCONFIG_ICS932S401[0m
tristate "Integrated Circuits ICS932S401"
depends on [31mCONFIG_I2C[0m
help
If you say yes here you get support for the Integrated Circuits
[31mCONFIG_ICS932S401[0m clock control chips.
This driver can also be built as a module. If so, the module
will be called ics932s401.
config [31mCONFIG_ATMEL_SSC[0m
tristate "Device driver for Atmel SSC peripheral"
depends on [31mCONFIG_HAS_IOMEM[0m && ([31mCONFIG_ARCH_AT91[0m || [31mCONFIG_COMPILE_TEST[0m)
---help---
This option enables device driver support for Atmel Synchronized
Serial Communication peripheral (SSC).
The SSC peripheral supports a wide variety of serial frame based
communications, i.e. I2S, [31mCONFIG_SPI[0m, etc.
If unsure, say N.
config [31mCONFIG_ENCLOSURE_SERVICES[0m
tristate "Enclosure Services"
help
Provides support for intelligent enclosures (bays which
contain storage devices). You also need either a host
driver ([31mCONFIG_SCSI[0m/[31mCONFIG_ATA[0m) which supports enclosures
or a [31mCONFIG_SCSI[0m enclosure device (SES) to use these services.
config [31mCONFIG_SGI_XP[0m
tristate "Support communication between SGI SSIs"
depends on [31mCONFIG_NET[0m
depends on ([31mCONFIG_IA64_SGI_UV[0m || [31mCONFIG_X86_UV[0m) && [31mCONFIG_SMP[0m
depends on [31mCONFIG_X86_64[0m || [31mCONFIG_BROKEN[0m
select [31mCONFIG_SGI_GRU[0m if [31mCONFIG_X86_64[0m && [31mCONFIG_SMP[0m
---help---
An SGI machine can be divided into multiple Single System
Images which act independently of each other and have
hardware based memory protection from the others. Enabling
this feature will allow for direct communication between SSIs
based on a network adapter and DMA messaging.
config [31mCONFIG_CS5535_MFGPT[0m
tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
depends on [31mCONFIG_MFD_CS5535[0m
help
This driver provides access to MFGPT functionality for other
drivers that need timers. MFGPTs are available in the CS5535 and
[31mCONFIG_CS5536[0m companion chips that are found in AMD Geode and several
other platforms. They have a better resolution and max interval
than the generic PIT, and are suitable for use as high-res timers.
You probably don't want to enable this manually; other drivers that
make use of it should enable it.
config [31mCONFIG_CS5535_MFGPT_DEFAULT_IRQ[0m
int
depends on [31mCONFIG_CS5535_MFGPT[0m
default 7
help
MFGPTs on the CS5535 require an interrupt. The selected IRQ
can be overridden as a module option as well as by driver that
use the cs5535_mfgpt_ API; however, different architectures might
want to use a different IRQ by default. This is here for
architectures to set as necessary.
config [31mCONFIG_CS5535_CLOCK_EVENT_SRC[0m
tristate "CS5535/CS5536 high-res timer (MFGPT) events"
depends on [31mCONFIG_GENERIC_CLOCKEVENTS[0m && [31mCONFIG_CS5535_MFGPT[0m
help
This driver provides a clock event source based on the MFGPT
timer(s) in the CS5535 and [31mCONFIG_CS5536[0m companion chips.
MFGPTs have a better resolution and max interval than the
generic PIT, and are suitable for use as high-res timers.
config [31mCONFIG_HP_ILO[0m
tristate "Channel interface driver for the HP iLO processor"
depends on [31mCONFIG_PCI[0m
help
The channel interface driver allows applications to communicate
with iLO management processors present on HP ProLiant servers.
Upon loading, the driver creates /dev/hpilo/dXccbN files, which
can be used to gather data from the management processor, via
read and write system calls.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called hpilo.
config [31mCONFIG_QCOM_COINCELL[0m
tristate "Qualcomm coincell charger support"
depends on [31mCONFIG_MFD_SPMI_PMIC[0m || [31mCONFIG_COMPILE_TEST[0m
help
This driver supports the coincell block found inside of
Qualcomm PMICs. The coincell charger provides a means to
charge a coincell battery or backup capacitor which is used
to maintain PMIC register and [31mCONFIG_RTC[0m state in the absence of
external power.
config [31mCONFIG_QCOM_FASTRPC[0m
tristate "Qualcomm FastRPC"
depends on [31mCONFIG_ARCH_QCOM[0m || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_RPMSG[0m
select [31mCONFIG_DMA_SHARED_BUFFER[0m
help
Provides a communication mechanism that allows for clients to
make remote method invocations across processor boundary to
applications DSP processor. Say [31mCONFIG_M[0m if you want to enable this
module.
config [31mCONFIG_SGI_GRU[0m
tristate "SGI GRU driver"
depends on [31mCONFIG_X86_UV[0m && [31mCONFIG_SMP[0m
select [31mCONFIG_MMU_NOTIFIER[0m
---help---
The GRU is a hardware resource located in the system chipset. The GRU
contains memory that can be mmapped into the user address space. This memory is
used to communicate with the GRU to perform functions such as load/store,
scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user
instructions using user virtual addresses. GRU instructions (ex., bcopy) use
user virtual addresses for operands.
If you are not running on a SGI UV system, say N.
config [31mCONFIG_SGI_GRU_DEBUG[0m
bool "SGI GRU driver debug"
depends on [31mCONFIG_SGI_GRU[0m
---help---
This option enables additional debugging code for the SGI GRU driver.
If you are unsure, say N.
config [31mCONFIG_APDS9802ALS[0m
tristate "Medfield Avago APDS9802 ALS Sensor module"
depends on [31mCONFIG_I2C[0m
help
If you say yes here you get support for the ALS APDS9802 ambient
light sensor.
This driver can also be built as a module. If so, the module
will be called apds9802als.
config [31mCONFIG_ISL29003[0m
tristate "Intersil ISL29003 ambient light sensor"
depends on [31mCONFIG_I2C[0m && [31mCONFIG_SYSFS[0m
help
If you say yes here you get support for the Intersil [31mCONFIG_ISL29003[0m
ambient light sensor.
This driver can also be built as a module. If so, the module
will be called isl29003.
config [31mCONFIG_ISL29020[0m
tristate "Intersil ISL29020 ambient light sensor"
depends on [31mCONFIG_I2C[0m
help
If you say yes here you get support for the Intersil [31mCONFIG_ISL29020[0m
ambient light sensor.
This driver can also be built as a module. If so, the module
will be called isl29020.
config [31mCONFIG_SENSORS_TSL2550[0m
tristate "Taos TSL2550 ambient light sensor"
depends on [31mCONFIG_I2C[0m && [31mCONFIG_SYSFS[0m
help
If you say yes here you get support for the Taos TSL2550
ambient light sensor.
This driver can also be built as a module. If so, the module
will be called tsl2550.
config [31mCONFIG_SENSORS_BH1770[0m
tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
depends on [31mCONFIG_I2C[0m
---help---
Say Y here if you want to build a driver for BH1770GLC (ROHM) or
SFH7770 (Osram) combined ambient light and proximity sensor chip.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called bh1770glc. If unsure, say N here.
config [31mCONFIG_SENSORS_APDS990X[0m
tristate "APDS990X combined als and proximity sensors"
depends on [31mCONFIG_I2C[0m
---help---
Say Y here if you want to build a driver for Avago APDS990x
combined ambient light and proximity sensor chip.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called apds990x. If unsure, say N here.
config [31mCONFIG_HMC6352[0m
tristate "Honeywell HMC6352 compass"
depends on [31mCONFIG_I2C[0m
help
This driver provides support for the Honeywell [31mCONFIG_HMC6352[0m compass,
providing configuration and heading data via sysfs.
config [31mCONFIG_DS1682[0m
tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
depends on [31mCONFIG_I2C[0m
help
If you say yes here you get support for Dallas Semiconductor
[31mCONFIG_DS1682[0m Total Elapsed Time Recorder.
This driver can also be built as a module. If so, the module
will be called ds1682.
config [31mCONFIG_VMWARE_BALLOON[0m
tristate "VMware Balloon Driver"
depends on [31mCONFIG_VMWARE_VMCI[0m && [31mCONFIG_X86[0m && [31mCONFIG_HYPERVISOR_GUEST[0m
select [31mCONFIG_MEMORY_BALLOON[0m
help
This is VMware physical memory management driver which acts
like a "balloon" that can be inflated to reclaim physical pages
by reserving them in the guest and invalidating them in the
monitor, freeing up the underlying machine pages so they can
be allocated to other guests. The balloon can also be deflated
to allow the guest to use more physical memory.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called vmw_balloon.
config [31mCONFIG_PCH_PHUB[0m
tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
select [31mCONFIG_GENERIC_NET_UTILS[0m
depends on [31mCONFIG_PCI[0m && ([31mCONFIG_X86_32[0m || [31mCONFIG_MIPS[0m || [31mCONFIG_COMPILE_TEST[0m)
help
This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
processor. The Topcliff has [31mCONFIG_MAC[0m address and Option [31mCONFIG_ROM[0m data in SROM.
This driver can access [31mCONFIG_MAC[0m address and Option [31mCONFIG_ROM[0m data in SROM.
This driver also can be used for LAPIS Semiconductor's IOH,
ML7213/ML7223/ML7831.
ML7213 which is for IVI(In-Vehicle Infotainment) use.
ML7223 IOH is for MP(Media Phone) use.
ML7831 IOH is for general purpose use.
ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module will
be called pch_phub.
config [31mCONFIG_LATTICE_ECP3_CONFIG[0m
tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
depends on [31mCONFIG_SPI[0m && [31mCONFIG_SYSFS[0m
select [31mCONFIG_FW_LOADER[0m
default n
help
This option enables support for bitstream configuration (programming
or loading) of the Lattice ECP3 [31mCONFIG_FPGA[0m family via [31mCONFIG_SPI[0m.
If unsure, say N.
config [31mCONFIG_SRAM[0m
bool "Generic on-chip SRAM driver"
depends on [31mCONFIG_HAS_IOMEM[0m
select [31mCONFIG_GENERIC_ALLOCATOR[0m
select [31mCONFIG_SRAM_EXEC[0m if [31mCONFIG_ARM[0m
help
This driver allows you to declare a memory region to be managed by
the genalloc API. It is supposed to be used for small on-chip [31mCONFIG_SRAM[0m
areas found on many SoCs.
config [31mCONFIG_SRAM_EXEC[0m
bool
config [31mCONFIG_VEXPRESS_SYSCFG[0m
bool "Versatile Express System Configuration driver"
depends on [31mCONFIG_VEXPRESS_CONFIG[0m
default y
help
[31mCONFIG_ARM[0m Ltd. Versatile Express uses specialised platform configuration
bus. System Configuration interface is one of the possible means
of generating transactions on this bus.
config [31mCONFIG_PCI_ENDPOINT_TEST[0m
depends on [31mCONFIG_PCI[0m
select [31mCONFIG_CRC32[0m
tristate "PCI Endpoint Test driver"
---help---
Enable this configuration option to enable the host side test driver
for [31mCONFIG_PCI[0m Endpoint.
config [31mCONFIG_XILINX_SDFEC[0m
tristate "Xilinx SDFEC 16"
depends on [31mCONFIG_HAS_IOMEM[0m
help
This option enables support for the Xilinx SDFEC (Soft Decision
Forward Error Correction) driver. This enables a char driver
for the SDFEC.
You may select this driver if your design instantiates the
SDFEC(16nm) hardened block. To compile this as a module choose [31mCONFIG_M[0m.
If unsure, say N.
config [31mCONFIG_MISC_RTSX[0m
tristate
default [31mCONFIG_MISC_RTSX_PCI[0m || [31mCONFIG_MISC_RTSX_USB[0m
config [31mCONFIG_PVPANIC[0m
tristate "pvpanic device support"
depends on [31mCONFIG_HAS_IOMEM[0m && ([31mCONFIG_ACPI[0m || [31mCONFIG_OF[0m)
help
This driver provides support for the pvpanic device. pvpanic is
a paravirtualized device provided by QEMU; it lets a virtual machine
(guest) communicate panic events to the host.
source "drivers/misc/c2port/Kconfig"
source "drivers/misc/eeprom/Kconfig"
source "drivers/misc/cb710/Kconfig"
source "drivers/misc/ti-st/Kconfig"
source "drivers/misc/lis3lv02d/Kconfig"
source "drivers/misc/altera-stapl/Kconfig"
source "drivers/misc/mei/Kconfig"
source "drivers/misc/vmw_vmci/Kconfig"
source "drivers/misc/mic/Kconfig"
source "drivers/misc/genwqe/Kconfig"
source "drivers/misc/echo/Kconfig"
source "drivers/misc/cxl/Kconfig"
source "drivers/misc/ocxl/Kconfig"
source "drivers/misc/cardreader/Kconfig"
source "drivers/misc/habanalabs/Kconfig"
endmenu