1*4882a593Smuzhiyun# SPDX-License-Identifier: GPL-2.0-only 2*4882a593Smuzhiyun# 3*4882a593Smuzhiyun# Misc strange devices 4*4882a593Smuzhiyun# 5*4882a593Smuzhiyun 6*4882a593Smuzhiyunmenu "Misc devices" 7*4882a593Smuzhiyun 8*4882a593Smuzhiyunsource "drivers/misc/rk628/Kconfig" 9*4882a593Smuzhiyun 10*4882a593Smuzhiyunconfig RK803 11*4882a593Smuzhiyun tristate "RK803" 12*4882a593Smuzhiyun default n 13*4882a593Smuzhiyun help 14*4882a593Smuzhiyun Driver for RK803 which is used for driving porjector and IR flood LED. 15*4882a593Smuzhiyun 16*4882a593Smuzhiyunsource "drivers/misc/rockchip/Kconfig" 17*4882a593Smuzhiyun 18*4882a593Smuzhiyunconfig LT7911D_FB_NOTIFIER 19*4882a593Smuzhiyun tristate "Lontium LT7911D FB Notifier" 20*4882a593Smuzhiyun depends on FB 21*4882a593Smuzhiyun help 22*4882a593Smuzhiyun Enable this configuration option to enable the FB notifier driver 23*4882a593Smuzhiyun for Lontium LT7911D. 24*4882a593Smuzhiyun 25*4882a593Smuzhiyunconfig SENSORS_LIS3LV02D 26*4882a593Smuzhiyun tristate 27*4882a593Smuzhiyun depends on INPUT 28*4882a593Smuzhiyun 29*4882a593Smuzhiyunconfig AD525X_DPOT 30*4882a593Smuzhiyun tristate "Analog Devices Digital Potentiometers" 31*4882a593Smuzhiyun depends on (I2C || SPI) && SYSFS 32*4882a593Smuzhiyun help 33*4882a593Smuzhiyun If you say yes here, you get support for the Analog Devices 34*4882a593Smuzhiyun AD5258, AD5259, AD5251, AD5252, AD5253, AD5254, AD5255 35*4882a593Smuzhiyun AD5160, AD5161, AD5162, AD5165, AD5200, AD5201, AD5203, 36*4882a593Smuzhiyun AD5204, AD5206, AD5207, AD5231, AD5232, AD5233, AD5235, 37*4882a593Smuzhiyun AD5260, AD5262, AD5263, AD5290, AD5291, AD5292, AD5293, 38*4882a593Smuzhiyun AD7376, AD8400, AD8402, AD8403, ADN2850, AD5241, AD5242, 39*4882a593Smuzhiyun AD5243, AD5245, AD5246, AD5247, AD5248, AD5280, AD5282, 40*4882a593Smuzhiyun ADN2860, AD5273, AD5171, AD5170, AD5172, AD5173, AD5270, 41*4882a593Smuzhiyun AD5271, AD5272, AD5274 42*4882a593Smuzhiyun digital potentiometer chips. 43*4882a593Smuzhiyun 44*4882a593Smuzhiyun See Documentation/misc-devices/ad525x_dpot.rst for the 45*4882a593Smuzhiyun userspace interface. 46*4882a593Smuzhiyun 47*4882a593Smuzhiyun This driver can also be built as a module. If so, the module 48*4882a593Smuzhiyun will be called ad525x_dpot. 49*4882a593Smuzhiyun 50*4882a593Smuzhiyunconfig AD525X_DPOT_I2C 51*4882a593Smuzhiyun tristate "support I2C bus connection" 52*4882a593Smuzhiyun depends on AD525X_DPOT && I2C 53*4882a593Smuzhiyun help 54*4882a593Smuzhiyun Say Y here if you have a digital potentiometers hooked to an I2C bus. 55*4882a593Smuzhiyun 56*4882a593Smuzhiyun To compile this driver as a module, choose M here: the 57*4882a593Smuzhiyun module will be called ad525x_dpot-i2c. 58*4882a593Smuzhiyun 59*4882a593Smuzhiyunconfig AD525X_DPOT_SPI 60*4882a593Smuzhiyun tristate "support SPI bus connection" 61*4882a593Smuzhiyun depends on AD525X_DPOT && SPI_MASTER 62*4882a593Smuzhiyun help 63*4882a593Smuzhiyun Say Y here if you have a digital potentiometers hooked to an SPI bus. 64*4882a593Smuzhiyun 65*4882a593Smuzhiyun If unsure, say N (but it's safe to say "Y"). 66*4882a593Smuzhiyun 67*4882a593Smuzhiyun To compile this driver as a module, choose M here: the 68*4882a593Smuzhiyun module will be called ad525x_dpot-spi. 69*4882a593Smuzhiyun 70*4882a593Smuzhiyunconfig ATMEL_TCLIB 71*4882a593Smuzhiyun bool "Atmel AT32/AT91 Timer/Counter Library" 72*4882a593Smuzhiyun depends on ARCH_AT91 73*4882a593Smuzhiyun help 74*4882a593Smuzhiyun Select this if you want a library to allocate the Timer/Counter 75*4882a593Smuzhiyun blocks found on many Atmel processors. This facilitates using 76*4882a593Smuzhiyun these blocks by different drivers despite processor differences. 77*4882a593Smuzhiyun 78*4882a593Smuzhiyunconfig DUMMY_IRQ 79*4882a593Smuzhiyun tristate "Dummy IRQ handler" 80*4882a593Smuzhiyun help 81*4882a593Smuzhiyun This module accepts a single 'irq' parameter, which it should register for. 82*4882a593Smuzhiyun The sole purpose of this module is to help with debugging of systems on 83*4882a593Smuzhiyun which spurious IRQs would happen on disabled IRQ vector. 84*4882a593Smuzhiyun 85*4882a593Smuzhiyunconfig IBM_ASM 86*4882a593Smuzhiyun tristate "Device driver for IBM RSA service processor" 87*4882a593Smuzhiyun depends on X86 && PCI && INPUT 88*4882a593Smuzhiyun depends on SERIAL_8250 || SERIAL_8250=n 89*4882a593Smuzhiyun help 90*4882a593Smuzhiyun This option enables device driver support for in-band access to the 91*4882a593Smuzhiyun IBM RSA (Condor) service processor in eServer xSeries systems. 92*4882a593Smuzhiyun The ibmasm device driver allows user space application to access 93*4882a593Smuzhiyun ASM (Advanced Systems Management) functions on the service 94*4882a593Smuzhiyun processor. The driver is meant to be used in conjunction with 95*4882a593Smuzhiyun a user space API. 96*4882a593Smuzhiyun The ibmasm driver also enables the OS to use the UART on the 97*4882a593Smuzhiyun service processor board as a regular serial port. To make use of 98*4882a593Smuzhiyun this feature serial driver support (CONFIG_SERIAL_8250) must be 99*4882a593Smuzhiyun enabled. 100*4882a593Smuzhiyun 101*4882a593Smuzhiyun WARNING: This software may not be supported or function 102*4882a593Smuzhiyun correctly on your IBM server. Please consult the IBM ServerProven 103*4882a593Smuzhiyun website <https://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/> 104*4882a593Smuzhiyun for information on the specific driver level and support statement 105*4882a593Smuzhiyun for your IBM server. 106*4882a593Smuzhiyun 107*4882a593Smuzhiyunconfig IBMVMC 108*4882a593Smuzhiyun tristate "IBM Virtual Management Channel support" 109*4882a593Smuzhiyun depends on PPC_PSERIES 110*4882a593Smuzhiyun help 111*4882a593Smuzhiyun This is the IBM POWER Virtual Management Channel 112*4882a593Smuzhiyun 113*4882a593Smuzhiyun This driver is to be used for the POWER Virtual 114*4882a593Smuzhiyun Management Channel virtual adapter on the PowerVM 115*4882a593Smuzhiyun platform. It provides both request/response and 116*4882a593Smuzhiyun async message support through the /dev/ibmvmc node. 117*4882a593Smuzhiyun 118*4882a593Smuzhiyun To compile this driver as a module, choose M here: the 119*4882a593Smuzhiyun module will be called ibmvmc. 120*4882a593Smuzhiyun 121*4882a593Smuzhiyunconfig PHANTOM 122*4882a593Smuzhiyun tristate "Sensable PHANToM (PCI)" 123*4882a593Smuzhiyun depends on PCI 124*4882a593Smuzhiyun help 125*4882a593Smuzhiyun Say Y here if you want to build a driver for Sensable PHANToM device. 126*4882a593Smuzhiyun 127*4882a593Smuzhiyun This driver is only for PCI PHANToMs. 128*4882a593Smuzhiyun 129*4882a593Smuzhiyun If you choose to build module, its name will be phantom. If unsure, 130*4882a593Smuzhiyun say N here. 131*4882a593Smuzhiyun 132*4882a593Smuzhiyunconfig INTEL_MID_PTI 133*4882a593Smuzhiyun tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard" 134*4882a593Smuzhiyun depends on PCI && TTY && (X86_INTEL_MID || COMPILE_TEST) 135*4882a593Smuzhiyun help 136*4882a593Smuzhiyun The PTI (Parallel Trace Interface) driver directs 137*4882a593Smuzhiyun trace data routed from various parts in the system out 138*4882a593Smuzhiyun through an Intel Penwell PTI port and out of the mobile 139*4882a593Smuzhiyun device for analysis with a debugging tool (Lauterbach or Fido). 140*4882a593Smuzhiyun 141*4882a593Smuzhiyun You should select this driver if the target kernel is meant for 142*4882a593Smuzhiyun an Intel Atom (non-netbook) mobile device containing a MIPI 143*4882a593Smuzhiyun P1149.7 standard implementation. 144*4882a593Smuzhiyun 145*4882a593Smuzhiyunconfig TIFM_CORE 146*4882a593Smuzhiyun tristate "TI Flash Media interface support" 147*4882a593Smuzhiyun depends on PCI 148*4882a593Smuzhiyun help 149*4882a593Smuzhiyun If you want support for Texas Instruments(R) Flash Media adapters 150*4882a593Smuzhiyun you should select this option and then also choose an appropriate 151*4882a593Smuzhiyun host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter 152*4882a593Smuzhiyun support', if you have a TI PCI74xx compatible card reader, for 153*4882a593Smuzhiyun example. 154*4882a593Smuzhiyun You will also have to select some flash card format drivers. MMC/SD 155*4882a593Smuzhiyun cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD 156*4882a593Smuzhiyun Interface support (MMC_TIFM_SD)'. 157*4882a593Smuzhiyun 158*4882a593Smuzhiyun To compile this driver as a module, choose M here: the module will 159*4882a593Smuzhiyun be called tifm_core. 160*4882a593Smuzhiyun 161*4882a593Smuzhiyunconfig TIFM_7XX1 162*4882a593Smuzhiyun tristate "TI Flash Media PCI74xx/PCI76xx host adapter support" 163*4882a593Smuzhiyun depends on PCI && TIFM_CORE 164*4882a593Smuzhiyun default TIFM_CORE 165*4882a593Smuzhiyun help 166*4882a593Smuzhiyun This option enables support for Texas Instruments(R) PCI74xx and 167*4882a593Smuzhiyun PCI76xx families of Flash Media adapters, found in many laptops. 168*4882a593Smuzhiyun To make actual use of the device, you will have to select some 169*4882a593Smuzhiyun flash card format drivers, as outlined in the TIFM_CORE Help. 170*4882a593Smuzhiyun 171*4882a593Smuzhiyun To compile this driver as a module, choose M here: the module will 172*4882a593Smuzhiyun be called tifm_7xx1. 173*4882a593Smuzhiyun 174*4882a593Smuzhiyunconfig ICS932S401 175*4882a593Smuzhiyun tristate "Integrated Circuits ICS932S401" 176*4882a593Smuzhiyun depends on I2C 177*4882a593Smuzhiyun help 178*4882a593Smuzhiyun If you say yes here you get support for the Integrated Circuits 179*4882a593Smuzhiyun ICS932S401 clock control chips. 180*4882a593Smuzhiyun 181*4882a593Smuzhiyun This driver can also be built as a module. If so, the module 182*4882a593Smuzhiyun will be called ics932s401. 183*4882a593Smuzhiyun 184*4882a593Smuzhiyunconfig ATMEL_SSC 185*4882a593Smuzhiyun tristate "Device driver for Atmel SSC peripheral" 186*4882a593Smuzhiyun depends on HAS_IOMEM && (ARCH_AT91 || COMPILE_TEST) 187*4882a593Smuzhiyun help 188*4882a593Smuzhiyun This option enables device driver support for Atmel Synchronized 189*4882a593Smuzhiyun Serial Communication peripheral (SSC). 190*4882a593Smuzhiyun 191*4882a593Smuzhiyun The SSC peripheral supports a wide variety of serial frame based 192*4882a593Smuzhiyun communications, i.e. I2S, SPI, etc. 193*4882a593Smuzhiyun 194*4882a593Smuzhiyun If unsure, say N. 195*4882a593Smuzhiyun 196*4882a593Smuzhiyunconfig ENCLOSURE_SERVICES 197*4882a593Smuzhiyun tristate "Enclosure Services" 198*4882a593Smuzhiyun help 199*4882a593Smuzhiyun Provides support for intelligent enclosures (bays which 200*4882a593Smuzhiyun contain storage devices). You also need either a host 201*4882a593Smuzhiyun driver (SCSI/ATA) which supports enclosures 202*4882a593Smuzhiyun or a SCSI enclosure device (SES) to use these services. 203*4882a593Smuzhiyun 204*4882a593Smuzhiyunconfig SGI_XP 205*4882a593Smuzhiyun tristate "Support communication between SGI SSIs" 206*4882a593Smuzhiyun depends on NET 207*4882a593Smuzhiyun depends on (IA64_SGI_UV || X86_UV) && SMP 208*4882a593Smuzhiyun depends on X86_64 || BROKEN 209*4882a593Smuzhiyun select SGI_GRU if X86_64 && SMP 210*4882a593Smuzhiyun help 211*4882a593Smuzhiyun An SGI machine can be divided into multiple Single System 212*4882a593Smuzhiyun Images which act independently of each other and have 213*4882a593Smuzhiyun hardware based memory protection from the others. Enabling 214*4882a593Smuzhiyun this feature will allow for direct communication between SSIs 215*4882a593Smuzhiyun based on a network adapter and DMA messaging. 216*4882a593Smuzhiyun 217*4882a593Smuzhiyunconfig CS5535_MFGPT 218*4882a593Smuzhiyun tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support" 219*4882a593Smuzhiyun depends on MFD_CS5535 220*4882a593Smuzhiyun help 221*4882a593Smuzhiyun This driver provides access to MFGPT functionality for other 222*4882a593Smuzhiyun drivers that need timers. MFGPTs are available in the CS5535 and 223*4882a593Smuzhiyun CS5536 companion chips that are found in AMD Geode and several 224*4882a593Smuzhiyun other platforms. They have a better resolution and max interval 225*4882a593Smuzhiyun than the generic PIT, and are suitable for use as high-res timers. 226*4882a593Smuzhiyun You probably don't want to enable this manually; other drivers that 227*4882a593Smuzhiyun make use of it should enable it. 228*4882a593Smuzhiyun 229*4882a593Smuzhiyunconfig CS5535_MFGPT_DEFAULT_IRQ 230*4882a593Smuzhiyun int 231*4882a593Smuzhiyun depends on CS5535_MFGPT 232*4882a593Smuzhiyun default 7 233*4882a593Smuzhiyun help 234*4882a593Smuzhiyun MFGPTs on the CS5535 require an interrupt. The selected IRQ 235*4882a593Smuzhiyun can be overridden as a module option as well as by driver that 236*4882a593Smuzhiyun use the cs5535_mfgpt_ API; however, different architectures might 237*4882a593Smuzhiyun want to use a different IRQ by default. This is here for 238*4882a593Smuzhiyun architectures to set as necessary. 239*4882a593Smuzhiyun 240*4882a593Smuzhiyunconfig CS5535_CLOCK_EVENT_SRC 241*4882a593Smuzhiyun tristate "CS5535/CS5536 high-res timer (MFGPT) events" 242*4882a593Smuzhiyun depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT 243*4882a593Smuzhiyun help 244*4882a593Smuzhiyun This driver provides a clock event source based on the MFGPT 245*4882a593Smuzhiyun timer(s) in the CS5535 and CS5536 companion chips. 246*4882a593Smuzhiyun MFGPTs have a better resolution and max interval than the 247*4882a593Smuzhiyun generic PIT, and are suitable for use as high-res timers. 248*4882a593Smuzhiyun 249*4882a593Smuzhiyunconfig HP_ILO 250*4882a593Smuzhiyun tristate "Channel interface driver for the HP iLO processor" 251*4882a593Smuzhiyun depends on PCI 252*4882a593Smuzhiyun help 253*4882a593Smuzhiyun The channel interface driver allows applications to communicate 254*4882a593Smuzhiyun with iLO management processors present on HP ProLiant servers. 255*4882a593Smuzhiyun Upon loading, the driver creates /dev/hpilo/dXccbN files, which 256*4882a593Smuzhiyun can be used to gather data from the management processor, via 257*4882a593Smuzhiyun read and write system calls. 258*4882a593Smuzhiyun 259*4882a593Smuzhiyun To compile this driver as a module, choose M here: the 260*4882a593Smuzhiyun module will be called hpilo. 261*4882a593Smuzhiyun 262*4882a593Smuzhiyunconfig QCOM_COINCELL 263*4882a593Smuzhiyun tristate "Qualcomm coincell charger support" 264*4882a593Smuzhiyun depends on MFD_SPMI_PMIC || COMPILE_TEST 265*4882a593Smuzhiyun help 266*4882a593Smuzhiyun This driver supports the coincell block found inside of 267*4882a593Smuzhiyun Qualcomm PMICs. The coincell charger provides a means to 268*4882a593Smuzhiyun charge a coincell battery or backup capacitor which is used 269*4882a593Smuzhiyun to maintain PMIC register and RTC state in the absence of 270*4882a593Smuzhiyun external power. 271*4882a593Smuzhiyun 272*4882a593Smuzhiyunconfig QCOM_FASTRPC 273*4882a593Smuzhiyun tristate "Qualcomm FastRPC" 274*4882a593Smuzhiyun depends on ARCH_QCOM || COMPILE_TEST 275*4882a593Smuzhiyun depends on RPMSG 276*4882a593Smuzhiyun select DMA_SHARED_BUFFER 277*4882a593Smuzhiyun help 278*4882a593Smuzhiyun Provides a communication mechanism that allows for clients to 279*4882a593Smuzhiyun make remote method invocations across processor boundary to 280*4882a593Smuzhiyun applications DSP processor. Say M if you want to enable this 281*4882a593Smuzhiyun module. 282*4882a593Smuzhiyun 283*4882a593Smuzhiyunconfig SGI_GRU 284*4882a593Smuzhiyun tristate "SGI GRU driver" 285*4882a593Smuzhiyun depends on X86_UV && SMP 286*4882a593Smuzhiyun select MMU_NOTIFIER 287*4882a593Smuzhiyun help 288*4882a593Smuzhiyun The GRU is a hardware resource located in the system chipset. The GRU 289*4882a593Smuzhiyun contains memory that can be mmapped into the user address space. This memory is 290*4882a593Smuzhiyun used to communicate with the GRU to perform functions such as load/store, 291*4882a593Smuzhiyun scatter/gather, bcopy, AMOs, etc. The GRU is directly accessed by user 292*4882a593Smuzhiyun instructions using user virtual addresses. GRU instructions (ex., bcopy) use 293*4882a593Smuzhiyun user virtual addresses for operands. 294*4882a593Smuzhiyun 295*4882a593Smuzhiyun If you are not running on a SGI UV system, say N. 296*4882a593Smuzhiyun 297*4882a593Smuzhiyunconfig SGI_GRU_DEBUG 298*4882a593Smuzhiyun bool "SGI GRU driver debug" 299*4882a593Smuzhiyun depends on SGI_GRU 300*4882a593Smuzhiyun help 301*4882a593Smuzhiyun This option enables additional debugging code for the SGI GRU driver. 302*4882a593Smuzhiyun If you are unsure, say N. 303*4882a593Smuzhiyun 304*4882a593Smuzhiyunconfig APDS9802ALS 305*4882a593Smuzhiyun tristate "Medfield Avago APDS9802 ALS Sensor module" 306*4882a593Smuzhiyun depends on I2C 307*4882a593Smuzhiyun help 308*4882a593Smuzhiyun If you say yes here you get support for the ALS APDS9802 ambient 309*4882a593Smuzhiyun light sensor. 310*4882a593Smuzhiyun 311*4882a593Smuzhiyun This driver can also be built as a module. If so, the module 312*4882a593Smuzhiyun will be called apds9802als. 313*4882a593Smuzhiyun 314*4882a593Smuzhiyunconfig ISL29003 315*4882a593Smuzhiyun tristate "Intersil ISL29003 ambient light sensor" 316*4882a593Smuzhiyun depends on I2C && SYSFS 317*4882a593Smuzhiyun help 318*4882a593Smuzhiyun If you say yes here you get support for the Intersil ISL29003 319*4882a593Smuzhiyun ambient light sensor. 320*4882a593Smuzhiyun 321*4882a593Smuzhiyun This driver can also be built as a module. If so, the module 322*4882a593Smuzhiyun will be called isl29003. 323*4882a593Smuzhiyun 324*4882a593Smuzhiyunconfig ISL29020 325*4882a593Smuzhiyun tristate "Intersil ISL29020 ambient light sensor" 326*4882a593Smuzhiyun depends on I2C 327*4882a593Smuzhiyun help 328*4882a593Smuzhiyun If you say yes here you get support for the Intersil ISL29020 329*4882a593Smuzhiyun ambient light sensor. 330*4882a593Smuzhiyun 331*4882a593Smuzhiyun This driver can also be built as a module. If so, the module 332*4882a593Smuzhiyun will be called isl29020. 333*4882a593Smuzhiyun 334*4882a593Smuzhiyunconfig SENSORS_TSL2550 335*4882a593Smuzhiyun tristate "Taos TSL2550 ambient light sensor" 336*4882a593Smuzhiyun depends on I2C && SYSFS 337*4882a593Smuzhiyun help 338*4882a593Smuzhiyun If you say yes here you get support for the Taos TSL2550 339*4882a593Smuzhiyun ambient light sensor. 340*4882a593Smuzhiyun 341*4882a593Smuzhiyun This driver can also be built as a module. If so, the module 342*4882a593Smuzhiyun will be called tsl2550. 343*4882a593Smuzhiyun 344*4882a593Smuzhiyunconfig SENSORS_BH1770 345*4882a593Smuzhiyun tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor" 346*4882a593Smuzhiyun depends on I2C 347*4882a593Smuzhiyun help 348*4882a593Smuzhiyun Say Y here if you want to build a driver for BH1770GLC (ROHM) or 349*4882a593Smuzhiyun SFH7770 (Osram) combined ambient light and proximity sensor chip. 350*4882a593Smuzhiyun 351*4882a593Smuzhiyun To compile this driver as a module, choose M here: the 352*4882a593Smuzhiyun module will be called bh1770glc. If unsure, say N here. 353*4882a593Smuzhiyun 354*4882a593Smuzhiyunconfig SENSORS_APDS990X 355*4882a593Smuzhiyun tristate "APDS990X combined als and proximity sensors" 356*4882a593Smuzhiyun depends on I2C 357*4882a593Smuzhiyun help 358*4882a593Smuzhiyun Say Y here if you want to build a driver for Avago APDS990x 359*4882a593Smuzhiyun combined ambient light and proximity sensor chip. 360*4882a593Smuzhiyun 361*4882a593Smuzhiyun To compile this driver as a module, choose M here: the 362*4882a593Smuzhiyun module will be called apds990x. If unsure, say N here. 363*4882a593Smuzhiyun 364*4882a593Smuzhiyunconfig HMC6352 365*4882a593Smuzhiyun tristate "Honeywell HMC6352 compass" 366*4882a593Smuzhiyun depends on I2C 367*4882a593Smuzhiyun help 368*4882a593Smuzhiyun This driver provides support for the Honeywell HMC6352 compass, 369*4882a593Smuzhiyun providing configuration and heading data via sysfs. 370*4882a593Smuzhiyun 371*4882a593Smuzhiyunconfig DS1682 372*4882a593Smuzhiyun tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm" 373*4882a593Smuzhiyun depends on I2C 374*4882a593Smuzhiyun help 375*4882a593Smuzhiyun If you say yes here you get support for Dallas Semiconductor 376*4882a593Smuzhiyun DS1682 Total Elapsed Time Recorder. 377*4882a593Smuzhiyun 378*4882a593Smuzhiyun This driver can also be built as a module. If so, the module 379*4882a593Smuzhiyun will be called ds1682. 380*4882a593Smuzhiyun 381*4882a593Smuzhiyunconfig VMWARE_BALLOON 382*4882a593Smuzhiyun tristate "VMware Balloon Driver" 383*4882a593Smuzhiyun depends on VMWARE_VMCI && X86 && HYPERVISOR_GUEST 384*4882a593Smuzhiyun select MEMORY_BALLOON 385*4882a593Smuzhiyun help 386*4882a593Smuzhiyun This is VMware physical memory management driver which acts 387*4882a593Smuzhiyun like a "balloon" that can be inflated to reclaim physical pages 388*4882a593Smuzhiyun by reserving them in the guest and invalidating them in the 389*4882a593Smuzhiyun monitor, freeing up the underlying machine pages so they can 390*4882a593Smuzhiyun be allocated to other guests. The balloon can also be deflated 391*4882a593Smuzhiyun to allow the guest to use more physical memory. 392*4882a593Smuzhiyun 393*4882a593Smuzhiyun If unsure, say N. 394*4882a593Smuzhiyun 395*4882a593Smuzhiyun To compile this driver as a module, choose M here: the 396*4882a593Smuzhiyun module will be called vmw_balloon. 397*4882a593Smuzhiyun 398*4882a593Smuzhiyunconfig PCH_PHUB 399*4882a593Smuzhiyun tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB" 400*4882a593Smuzhiyun select GENERIC_NET_UTILS 401*4882a593Smuzhiyun depends on PCI && (X86_32 || MIPS || COMPILE_TEST) 402*4882a593Smuzhiyun help 403*4882a593Smuzhiyun This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of 404*4882a593Smuzhiyun Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded 405*4882a593Smuzhiyun processor. The Topcliff has MAC address and Option ROM data in SROM. 406*4882a593Smuzhiyun This driver can access MAC address and Option ROM data in SROM. 407*4882a593Smuzhiyun 408*4882a593Smuzhiyun This driver also can be used for LAPIS Semiconductor's IOH, 409*4882a593Smuzhiyun ML7213/ML7223/ML7831. 410*4882a593Smuzhiyun ML7213 which is for IVI(In-Vehicle Infotainment) use. 411*4882a593Smuzhiyun ML7223 IOH is for MP(Media Phone) use. 412*4882a593Smuzhiyun ML7831 IOH is for general purpose use. 413*4882a593Smuzhiyun ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series. 414*4882a593Smuzhiyun ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH. 415*4882a593Smuzhiyun 416*4882a593Smuzhiyun To compile this driver as a module, choose M here: the module will 417*4882a593Smuzhiyun be called pch_phub. 418*4882a593Smuzhiyun 419*4882a593Smuzhiyunconfig LATTICE_ECP3_CONFIG 420*4882a593Smuzhiyun tristate "Lattice ECP3 FPGA bitstream configuration via SPI" 421*4882a593Smuzhiyun depends on SPI && SYSFS 422*4882a593Smuzhiyun select FW_LOADER 423*4882a593Smuzhiyun default n 424*4882a593Smuzhiyun help 425*4882a593Smuzhiyun This option enables support for bitstream configuration (programming 426*4882a593Smuzhiyun or loading) of the Lattice ECP3 FPGA family via SPI. 427*4882a593Smuzhiyun 428*4882a593Smuzhiyun If unsure, say N. 429*4882a593Smuzhiyun 430*4882a593Smuzhiyunconfig SRAM 431*4882a593Smuzhiyun bool "Generic on-chip SRAM driver" 432*4882a593Smuzhiyun depends on HAS_IOMEM 433*4882a593Smuzhiyun select GENERIC_ALLOCATOR 434*4882a593Smuzhiyun select SRAM_EXEC if ARM 435*4882a593Smuzhiyun help 436*4882a593Smuzhiyun This driver allows you to declare a memory region to be managed by 437*4882a593Smuzhiyun the genalloc API. It is supposed to be used for small on-chip SRAM 438*4882a593Smuzhiyun areas found on many SoCs. 439*4882a593Smuzhiyun 440*4882a593Smuzhiyunconfig SRAM_EXEC 441*4882a593Smuzhiyun bool 442*4882a593Smuzhiyun 443*4882a593Smuzhiyunconfig PCI_ENDPOINT_TEST 444*4882a593Smuzhiyun depends on PCI 445*4882a593Smuzhiyun select CRC32 446*4882a593Smuzhiyun tristate "PCI Endpoint Test driver" 447*4882a593Smuzhiyun help 448*4882a593Smuzhiyun Enable this configuration option to enable the host side test driver 449*4882a593Smuzhiyun for PCI Endpoint. 450*4882a593Smuzhiyun 451*4882a593Smuzhiyunconfig XILINX_SDFEC 452*4882a593Smuzhiyun tristate "Xilinx SDFEC 16" 453*4882a593Smuzhiyun depends on HAS_IOMEM 454*4882a593Smuzhiyun help 455*4882a593Smuzhiyun This option enables support for the Xilinx SDFEC (Soft Decision 456*4882a593Smuzhiyun Forward Error Correction) driver. This enables a char driver 457*4882a593Smuzhiyun for the SDFEC. 458*4882a593Smuzhiyun 459*4882a593Smuzhiyun You may select this driver if your design instantiates the 460*4882a593Smuzhiyun SDFEC(16nm) hardened block. To compile this as a module choose M. 461*4882a593Smuzhiyun 462*4882a593Smuzhiyun If unsure, say N. 463*4882a593Smuzhiyun 464*4882a593Smuzhiyunconfig MISC_RTSX 465*4882a593Smuzhiyun tristate 466*4882a593Smuzhiyun default MISC_RTSX_PCI || MISC_RTSX_USB 467*4882a593Smuzhiyun 468*4882a593Smuzhiyunconfig UID_SYS_STATS 469*4882a593Smuzhiyun bool "Per-UID statistics" 470*4882a593Smuzhiyun depends on PROFILING && TASK_XACCT && TASK_IO_ACCOUNTING 471*4882a593Smuzhiyun help 472*4882a593Smuzhiyun Per UID based cpu time statistics exported to /proc/uid_cputime 473*4882a593Smuzhiyun Per UID based io statistics exported to /proc/uid_io 474*4882a593Smuzhiyun Per UID based procstat control in /proc/uid_procstat 475*4882a593Smuzhiyun 476*4882a593Smuzhiyunconfig UID_SYS_STATS_DEBUG 477*4882a593Smuzhiyun bool "Per-TASK statistics" 478*4882a593Smuzhiyun depends on UID_SYS_STATS 479*4882a593Smuzhiyun default n 480*4882a593Smuzhiyun help 481*4882a593Smuzhiyun Per TASK based io statistics exported to /proc/uid_io 482*4882a593Smuzhiyun 483*4882a593Smuzhiyunconfig PVPANIC 484*4882a593Smuzhiyun tristate "pvpanic device support" 485*4882a593Smuzhiyun depends on HAS_IOMEM && (ACPI || OF) 486*4882a593Smuzhiyun help 487*4882a593Smuzhiyun This driver provides support for the pvpanic device. pvpanic is 488*4882a593Smuzhiyun a paravirtualized device provided by QEMU; it lets a virtual machine 489*4882a593Smuzhiyun (guest) communicate panic events to the host. 490*4882a593Smuzhiyun 491*4882a593Smuzhiyunconfig HISI_HIKEY_USB 492*4882a593Smuzhiyun tristate "USB GPIO Hub on HiSilicon Hikey 960/970 Platform" 493*4882a593Smuzhiyun depends on (OF && GPIOLIB) || COMPILE_TEST 494*4882a593Smuzhiyun depends on USB_ROLE_SWITCH 495*4882a593Smuzhiyun help 496*4882a593Smuzhiyun If you say yes here this adds support for the on-board USB GPIO hub 497*4882a593Smuzhiyun found on HiKey 960/970 boards, which is necessary to support 498*4882a593Smuzhiyun switching between the dual-role USB-C port and the USB-A host ports 499*4882a593Smuzhiyun using only one USB controller. 500*4882a593Smuzhiyun 501*4882a593Smuzhiyunsource "drivers/misc/c2port/Kconfig" 502*4882a593Smuzhiyunsource "drivers/misc/eeprom/Kconfig" 503*4882a593Smuzhiyunsource "drivers/misc/cb710/Kconfig" 504*4882a593Smuzhiyunsource "drivers/misc/ti-st/Kconfig" 505*4882a593Smuzhiyunsource "drivers/misc/lis3lv02d/Kconfig" 506*4882a593Smuzhiyunsource "drivers/misc/altera-stapl/Kconfig" 507*4882a593Smuzhiyunsource "drivers/misc/mei/Kconfig" 508*4882a593Smuzhiyunsource "drivers/misc/vmw_vmci/Kconfig" 509*4882a593Smuzhiyunsource "drivers/misc/genwqe/Kconfig" 510*4882a593Smuzhiyunsource "drivers/misc/echo/Kconfig" 511*4882a593Smuzhiyunsource "drivers/misc/cxl/Kconfig" 512*4882a593Smuzhiyunsource "drivers/misc/ocxl/Kconfig" 513*4882a593Smuzhiyunsource "drivers/misc/cardreader/Kconfig" 514*4882a593Smuzhiyunsource "drivers/misc/habanalabs/Kconfig" 515*4882a593Smuzhiyunsource "drivers/misc/uacce/Kconfig" 516*4882a593Smuzhiyunendmenu 517