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