| .. | .. | 
|---|
 | 1 | +# SPDX-License-Identifier: GPL-2.0-only  | 
|---|
| 1 | 2 |  # | 
|---|
| 2 | 3 |  # Misc strange devices | 
|---|
| 3 | 4 |  # | 
|---|
| 4 | 5 |   | 
|---|
| 5 | 6 |  menu "Misc devices" | 
|---|
| 6 | 7 |   | 
|---|
| 7 |  | -config ROCKCHIP_SCR  | 
|---|
| 8 |  | -	tristate "Rockchip Smartcard Reader Controller support"  | 
|---|
 | 8 | +source "drivers/misc/rk628/Kconfig"  | 
|---|
 | 9 | +  | 
|---|
 | 10 | +config RK803  | 
|---|
 | 11 | +	tristate "RK803"  | 
|---|
| 9 | 12 |  	default n | 
|---|
| 10 | 13 |  	help | 
|---|
| 11 |  | -	  say Y here to enable Rockchip Smartcard Reader Controller driver  | 
|---|
| 12 |  | -	  for Soc such as RK3128,RK322x,RK3288,RK3368,RK3366,RK356x and etc.  | 
|---|
 | 14 | +	  Driver for RK803 which is used for driving porjector and IR flood LED.  | 
|---|
 | 15 | +  | 
|---|
 | 16 | +source "drivers/misc/rockchip/Kconfig"  | 
|---|
 | 17 | +  | 
|---|
 | 18 | +config 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.  | 
|---|
| 13 | 24 |   | 
|---|
| 14 | 25 |  config SENSORS_LIS3LV02D | 
|---|
| 15 | 26 |  	tristate | 
|---|
| 16 | 27 |  	depends on INPUT | 
|---|
| 17 |  | -	select INPUT_POLLDEV  | 
|---|
| 18 |  | -	default n  | 
|---|
| 19 | 28 |   | 
|---|
| 20 | 29 |  config AD525X_DPOT | 
|---|
| 21 | 30 |  	tristate "Analog Devices Digital Potentiometers" | 
|---|
| .. | .. | 
|---|
| 32 | 41 |  	  AD5271, AD5272, AD5274 | 
|---|
| 33 | 42 |  	  digital potentiometer chips. | 
|---|
| 34 | 43 |   | 
|---|
| 35 |  | -	  See Documentation/misc-devices/ad525x_dpot.txt for the  | 
|---|
 | 44 | +	  See Documentation/misc-devices/ad525x_dpot.rst for the  | 
|---|
| 36 | 45 |  	  userspace interface. | 
|---|
| 37 | 46 |   | 
|---|
| 38 | 47 |  	  This driver can also be built as a module.  If so, the module | 
|---|
| .. | .. | 
|---|
| 66 | 75 |  	  blocks found on many Atmel processors.  This facilitates using | 
|---|
| 67 | 76 |  	  these blocks by different drivers despite processor differences. | 
|---|
| 68 | 77 |   | 
|---|
| 69 |  | -config ATMEL_TCB_CLKSRC  | 
|---|
| 70 |  | -	bool "TC Block Clocksource"  | 
|---|
| 71 |  | -	depends on ATMEL_TCLIB  | 
|---|
| 72 |  | -	default y  | 
|---|
| 73 |  | -	help  | 
|---|
| 74 |  | -	  Select this to get a high precision clocksource based on a  | 
|---|
| 75 |  | -	  TC block with a 5+ MHz base clock rate.  Two timer channels  | 
|---|
| 76 |  | -	  are combined to make a single 32-bit timer.  | 
|---|
| 77 |  | -  | 
|---|
| 78 |  | -	  When GENERIC_CLOCKEVENTS is defined, the third timer channel  | 
|---|
| 79 |  | -	  may be used as a clock event device supporting oneshot mode  | 
|---|
| 80 |  | -	  (delays of up to two seconds) based on the 32 KiHz clock.  | 
|---|
| 81 |  | -  | 
|---|
| 82 |  | -config ATMEL_TCB_CLKSRC_BLOCK  | 
|---|
| 83 |  | -	int  | 
|---|
| 84 |  | -	depends on ATMEL_TCB_CLKSRC  | 
|---|
| 85 |  | -	default 0  | 
|---|
| 86 |  | -	range 0 1  | 
|---|
| 87 |  | -	help  | 
|---|
| 88 |  | -	  Some chips provide more than one TC block, so you have the  | 
|---|
| 89 |  | -	  choice of which one to use for the clock framework.  The other  | 
|---|
| 90 |  | -	  TC can be used for other purposes, such as PWM generation and  | 
|---|
| 91 |  | -	  interval timing.  | 
|---|
| 92 |  | -  | 
|---|
| 93 | 78 |  config DUMMY_IRQ | 
|---|
| 94 | 79 |  	tristate "Dummy IRQ handler" | 
|---|
| 95 |  | -	default n  | 
|---|
| 96 |  | -	---help---  | 
|---|
 | 80 | +	help  | 
|---|
| 97 | 81 |  	  This module accepts a single 'irq' parameter, which it should register for. | 
|---|
| 98 | 82 |  	  The sole purpose of this module is to help with debugging of systems on | 
|---|
| 99 | 83 |  	  which spurious IRQs would happen on disabled IRQ vector. | 
|---|
| .. | .. | 
|---|
| 102 | 86 |  	tristate "Device driver for IBM RSA service processor" | 
|---|
| 103 | 87 |  	depends on X86 && PCI && INPUT | 
|---|
| 104 | 88 |  	depends on SERIAL_8250 || SERIAL_8250=n | 
|---|
| 105 |  | -	---help---  | 
|---|
 | 89 | +	help  | 
|---|
| 106 | 90 |  	  This option enables device driver support for in-band access to the | 
|---|
| 107 | 91 |  	  IBM RSA (Condor) service processor in eServer xSeries systems. | 
|---|
| 108 | 92 |  	  The ibmasm device driver allows user space application to access | 
|---|
| .. | .. | 
|---|
| 116 | 100 |   | 
|---|
| 117 | 101 |  	  WARNING: This software may not be supported or function | 
|---|
| 118 | 102 |  	  correctly on your IBM server. Please consult the IBM ServerProven | 
|---|
| 119 |  | -	  website <http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>  | 
|---|
 | 103 | +	  website <https://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/>  | 
|---|
| 120 | 104 |  	  for information on the specific driver level and support statement | 
|---|
| 121 | 105 |  	  for your IBM server. | 
|---|
| 122 | 106 |   | 
|---|
| .. | .. | 
|---|
| 148 | 132 |  config INTEL_MID_PTI | 
|---|
| 149 | 133 |  	tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard" | 
|---|
| 150 | 134 |  	depends on PCI && TTY && (X86_INTEL_MID || COMPILE_TEST) | 
|---|
| 151 |  | -	default n  | 
|---|
| 152 | 135 |  	help | 
|---|
| 153 | 136 |  	  The PTI (Parallel Trace Interface) driver directs | 
|---|
| 154 | 137 |  	  trace data routed from various parts in the system out | 
|---|
| .. | .. | 
|---|
| 158 | 141 |  	  You should select this driver if the target kernel is meant for | 
|---|
| 159 | 142 |  	  an Intel Atom (non-netbook) mobile device containing a MIPI | 
|---|
| 160 | 143 |  	  P1149.7 standard implementation. | 
|---|
| 161 |  | -  | 
|---|
| 162 |  | -config SGI_IOC4  | 
|---|
| 163 |  | -	tristate "SGI IOC4 Base IO support"  | 
|---|
| 164 |  | -	depends on PCI  | 
|---|
| 165 |  | -	---help---  | 
|---|
| 166 |  | -	  This option enables basic support for the IOC4 chip on certain  | 
|---|
| 167 |  | -	  SGI IO controller cards (IO9, IO10, and PCI-RT).  This option  | 
|---|
| 168 |  | -	  does not enable any specific functions on such a card, but provides  | 
|---|
| 169 |  | -	  necessary infrastructure for other drivers to utilize.  | 
|---|
| 170 |  | -  | 
|---|
| 171 |  | -	  If you have an SGI Altix with an IOC4-based card say Y.  | 
|---|
| 172 |  | -	  Otherwise say N.  | 
|---|
| 173 | 144 |   | 
|---|
| 174 | 145 |  config TIFM_CORE | 
|---|
| 175 | 146 |  	tristate "TI Flash Media interface support" | 
|---|
| .. | .. | 
|---|
| 213 | 184 |  config ATMEL_SSC | 
|---|
| 214 | 185 |  	tristate "Device driver for Atmel SSC peripheral" | 
|---|
| 215 | 186 |  	depends on HAS_IOMEM && (ARCH_AT91 || COMPILE_TEST) | 
|---|
| 216 |  | -	---help---  | 
|---|
 | 187 | +	help  | 
|---|
| 217 | 188 |  	  This option enables device driver support for Atmel Synchronized | 
|---|
| 218 | 189 |  	  Serial Communication peripheral (SSC). | 
|---|
| 219 | 190 |   | 
|---|
| .. | .. | 
|---|
| 224 | 195 |   | 
|---|
| 225 | 196 |  config ENCLOSURE_SERVICES | 
|---|
| 226 | 197 |  	tristate "Enclosure Services" | 
|---|
| 227 |  | -	default n  | 
|---|
| 228 | 198 |  	help | 
|---|
| 229 | 199 |  	  Provides support for intelligent enclosures (bays which | 
|---|
| 230 | 200 |  	  contain storage devices).  You also need either a host | 
|---|
| .. | .. | 
|---|
| 234 | 204 |  config SGI_XP | 
|---|
| 235 | 205 |  	tristate "Support communication between SGI SSIs" | 
|---|
| 236 | 206 |  	depends on NET | 
|---|
| 237 |  | -	depends on (IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || X86_UV) && SMP  | 
|---|
| 238 |  | -	select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2  | 
|---|
| 239 |  | -	select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2  | 
|---|
 | 207 | +	depends on (IA64_SGI_UV || X86_UV) && SMP  | 
|---|
 | 208 | +	depends on X86_64 || BROKEN  | 
|---|
| 240 | 209 |  	select SGI_GRU if X86_64 && SMP | 
|---|
| 241 |  | -	---help---  | 
|---|
 | 210 | +	help  | 
|---|
| 242 | 211 |  	  An SGI machine can be divided into multiple Single System | 
|---|
| 243 | 212 |  	  Images which act independently of each other and have | 
|---|
| 244 | 213 |  	  hardware based memory protection from the others.  Enabling | 
|---|
| .. | .. | 
|---|
| 248 | 217 |  config CS5535_MFGPT | 
|---|
| 249 | 218 |  	tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support" | 
|---|
| 250 | 219 |  	depends on MFD_CS5535 | 
|---|
| 251 |  | -	default n  | 
|---|
| 252 | 220 |  	help | 
|---|
| 253 | 221 |  	  This driver provides access to MFGPT functionality for other | 
|---|
| 254 | 222 |  	  drivers that need timers.  MFGPTs are available in the CS5535 and | 
|---|
| .. | .. | 
|---|
| 281 | 249 |  config HP_ILO | 
|---|
| 282 | 250 |  	tristate "Channel interface driver for the HP iLO processor" | 
|---|
| 283 | 251 |  	depends on PCI | 
|---|
| 284 |  | -	default n  | 
|---|
| 285 | 252 |  	help | 
|---|
| 286 | 253 |  	  The channel interface driver allows applications to communicate | 
|---|
| 287 | 254 |  	  with iLO management processors present on HP ProLiant servers. | 
|---|
| .. | .. | 
|---|
| 302 | 269 |  	  to maintain PMIC register and RTC state in the absence of | 
|---|
| 303 | 270 |  	  external power. | 
|---|
| 304 | 271 |   | 
|---|
 | 272 | +config 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 | +  | 
|---|
| 305 | 283 |  config SGI_GRU | 
|---|
| 306 | 284 |  	tristate "SGI GRU driver" | 
|---|
| 307 | 285 |  	depends on X86_UV && SMP | 
|---|
| 308 |  | -	default n  | 
|---|
| 309 | 286 |  	select MMU_NOTIFIER | 
|---|
| 310 |  | -	---help---  | 
|---|
 | 287 | +	help  | 
|---|
| 311 | 288 |  	The GRU is a hardware resource located in the system chipset. The GRU | 
|---|
| 312 | 289 |  	contains memory that can be mmapped into the user address space. This memory is | 
|---|
| 313 | 290 |  	used to communicate with the GRU to perform functions such as load/store, | 
|---|
| .. | .. | 
|---|
| 320 | 297 |  config SGI_GRU_DEBUG | 
|---|
| 321 | 298 |  	bool  "SGI GRU driver debug" | 
|---|
| 322 | 299 |  	depends on SGI_GRU | 
|---|
| 323 |  | -	default n  | 
|---|
| 324 |  | -	---help---  | 
|---|
 | 300 | +	help  | 
|---|
| 325 | 301 |  	This option enables additional debugging code for the SGI GRU driver. | 
|---|
| 326 | 302 |  	If you are unsure, say N. | 
|---|
| 327 | 303 |   | 
|---|
| .. | .. | 
|---|
| 366 | 342 |  	  will be called tsl2550. | 
|---|
| 367 | 343 |   | 
|---|
| 368 | 344 |  config SENSORS_BH1770 | 
|---|
| 369 |  | -         tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"  | 
|---|
| 370 |  | -         depends on I2C  | 
|---|
| 371 |  | -         ---help---  | 
|---|
| 372 |  | -           Say Y here if you want to build a driver for BH1770GLC (ROHM) or  | 
|---|
 | 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  | 
|---|
| 373 | 349 |  	   SFH7770 (Osram) combined ambient light and proximity sensor chip. | 
|---|
| 374 | 350 |   | 
|---|
| 375 |  | -           To compile this driver as a module, choose M here: the  | 
|---|
| 376 |  | -           module will be called bh1770glc. If unsure, say N here.  | 
|---|
 | 351 | +	   To compile this driver as a module, choose M here: the  | 
|---|
 | 352 | +	   module will be called bh1770glc. If unsure, say N here.  | 
|---|
| 377 | 353 |   | 
|---|
| 378 | 354 |  config SENSORS_APDS990X | 
|---|
| 379 | 355 |  	 tristate "APDS990X combined als and proximity sensors" | 
|---|
| 380 | 356 |  	 depends on I2C | 
|---|
| 381 |  | -	 default n  | 
|---|
| 382 |  | -	 ---help---  | 
|---|
 | 357 | +	help  | 
|---|
| 383 | 358 |  	   Say Y here if you want to build a driver for Avago APDS990x | 
|---|
| 384 | 359 |  	   combined ambient light and proximity sensor chip. | 
|---|
| 385 | 360 |   | 
|---|
| .. | .. | 
|---|
| 403 | 378 |  	  This driver can also be built as a module.  If so, the module | 
|---|
| 404 | 379 |  	  will be called ds1682. | 
|---|
| 405 | 380 |   | 
|---|
| 406 |  | -config SPEAR13XX_PCIE_GADGET  | 
|---|
| 407 |  | -	bool "PCIe gadget support for SPEAr13XX platform"  | 
|---|
| 408 |  | -	depends on ARCH_SPEAR13XX && BROKEN  | 
|---|
| 409 |  | -	default n  | 
|---|
| 410 |  | -	help  | 
|---|
| 411 |  | -	 This option enables gadget support for PCIe controller. If  | 
|---|
| 412 |  | -	 board file defines any controller as PCIe endpoint then a sysfs  | 
|---|
| 413 |  | -	 entry will be created for that controller. User can use these  | 
|---|
| 414 |  | -	 sysfs node to configure PCIe EP as per his requirements.  | 
|---|
| 415 |  | -  | 
|---|
| 416 | 381 |  config VMWARE_BALLOON | 
|---|
| 417 | 382 |  	tristate "VMware Balloon Driver" | 
|---|
| 418 | 383 |  	depends on VMWARE_VMCI && X86 && HYPERVISOR_GUEST | 
|---|
 | 384 | +	select MEMORY_BALLOON  | 
|---|
| 419 | 385 |  	help | 
|---|
| 420 | 386 |  	  This is VMware physical memory management driver which acts | 
|---|
| 421 | 387 |  	  like a "balloon" that can be inflated to reclaim physical pages | 
|---|
| .. | .. | 
|---|
| 450 | 416 |  	  To compile this driver as a module, choose M here: the module will | 
|---|
| 451 | 417 |  	  be called pch_phub. | 
|---|
| 452 | 418 |   | 
|---|
| 453 |  | -config USB_SWITCH_FSA9480  | 
|---|
| 454 |  | -	tristate "FSA9480 USB Switch"  | 
|---|
| 455 |  | -	depends on I2C  | 
|---|
| 456 |  | -	help  | 
|---|
| 457 |  | -	  The FSA9480 is a USB port accessory detector and switch.  | 
|---|
| 458 |  | -	  The FSA9480 is fully controlled using I2C and enables USB data,  | 
|---|
| 459 |  | -	  stereo and mono audio, video, microphone and UART data to use  | 
|---|
| 460 |  | -	  a common connector port.  | 
|---|
| 461 |  | -  | 
|---|
| 462 | 419 |  config LATTICE_ECP3_CONFIG | 
|---|
| 463 | 420 |  	tristate "Lattice ECP3 FPGA bitstream configuration via SPI" | 
|---|
| 464 | 421 |  	depends on SPI && SYSFS | 
|---|
| .. | .. | 
|---|
| 483 | 440 |  config SRAM_EXEC | 
|---|
| 484 | 441 |  	bool | 
|---|
| 485 | 442 |   | 
|---|
| 486 |  | -config VEXPRESS_SYSCFG  | 
|---|
| 487 |  | -	bool "Versatile Express System Configuration driver"  | 
|---|
| 488 |  | -	depends on VEXPRESS_CONFIG  | 
|---|
| 489 |  | -	default y  | 
|---|
| 490 |  | -	help  | 
|---|
| 491 |  | -	  ARM Ltd. Versatile Express uses specialised platform configuration  | 
|---|
| 492 |  | -	  bus. System Configuration interface is one of the possible means  | 
|---|
| 493 |  | -	  of generating transactions on this bus.  | 
|---|
| 494 |  | -  | 
|---|
| 495 |  | -config ASPEED_LPC_CTRL  | 
|---|
| 496 |  | -	depends on (ARCH_ASPEED || COMPILE_TEST) && REGMAP && MFD_SYSCON  | 
|---|
| 497 |  | -	tristate "Aspeed ast2400/2500 HOST LPC to BMC bridge control"  | 
|---|
| 498 |  | -	---help---  | 
|---|
| 499 |  | -	  Control Aspeed ast2400/2500 HOST LPC to BMC mappings through  | 
|---|
| 500 |  | -	  ioctl()s, the driver also provides a read/write interface to a BMC ram  | 
|---|
| 501 |  | -	  region where the host LPC read/write region can be buffered.  | 
|---|
| 502 |  | -  | 
|---|
| 503 |  | -config ASPEED_LPC_SNOOP  | 
|---|
| 504 |  | -	tristate "Aspeed ast2500 HOST LPC snoop support"  | 
|---|
| 505 |  | -	depends on (ARCH_ASPEED || COMPILE_TEST) && REGMAP && MFD_SYSCON  | 
|---|
| 506 |  | -	help  | 
|---|
| 507 |  | -	  Provides a driver to control the LPC snoop interface which  | 
|---|
| 508 |  | -	  allows the BMC to listen on and save the data written by  | 
|---|
| 509 |  | -	  the host to an arbitrary LPC I/O port.  | 
|---|
| 510 |  | -  | 
|---|
| 511 | 443 |  config PCI_ENDPOINT_TEST | 
|---|
| 512 | 444 |  	depends on PCI | 
|---|
| 513 | 445 |  	select CRC32 | 
|---|
| 514 | 446 |  	tristate "PCI Endpoint Test driver" | 
|---|
| 515 |  | -	---help---  | 
|---|
| 516 |  | -           Enable this configuration option to enable the host side test driver  | 
|---|
| 517 |  | -           for PCI Endpoint.  | 
|---|
 | 447 | +	help  | 
|---|
 | 448 | +	   Enable this configuration option to enable the host side test driver  | 
|---|
 | 449 | +	   for PCI Endpoint.  | 
|---|
 | 450 | +  | 
|---|
 | 451 | +config 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.  | 
|---|
| 518 | 463 |   | 
|---|
| 519 | 464 |  config MISC_RTSX | 
|---|
| 520 | 465 |  	tristate | 
|---|
| .. | .. | 
|---|
| 535 | 480 |  	help | 
|---|
| 536 | 481 |  	  Per TASK based io statistics exported to /proc/uid_io | 
|---|
| 537 | 482 |   | 
|---|
| 538 |  | -config PIR_ASCHIP  | 
|---|
| 539 |  | -	bool "Aschip PIR(Passive Infrared Sensor)"  | 
|---|
| 540 |  | -	default n  | 
|---|
 | 483 | +config PVPANIC  | 
|---|
 | 484 | +	tristate "pvpanic device support"  | 
|---|
 | 485 | +	depends on HAS_IOMEM && (ACPI || OF)  | 
|---|
| 541 | 486 |  	help | 
|---|
| 542 |  | -	  Provides a driver to control the sensibility of the Aschip PIR detection  | 
|---|
| 543 |  | -	  sensor.  | 
|---|
 | 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.  | 
|---|
| 544 | 490 |   | 
|---|
| 545 |  | -config RK803  | 
|---|
| 546 |  | -	tristate "RK803"  | 
|---|
| 547 |  | -	default n  | 
|---|
 | 491 | +config 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  | 
|---|
| 548 | 495 |  	help | 
|---|
| 549 |  | -	  Driver for RK803 which is used for driving porjector and IR flood LED.  | 
|---|
 | 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.  | 
|---|
| 550 | 500 |   | 
|---|
| 551 | 501 |  source "drivers/misc/c2port/Kconfig" | 
|---|
| 552 | 502 |  source "drivers/misc/eeprom/Kconfig" | 
|---|
| .. | .. | 
|---|
| 556 | 506 |  source "drivers/misc/altera-stapl/Kconfig" | 
|---|
| 557 | 507 |  source "drivers/misc/mei/Kconfig" | 
|---|
| 558 | 508 |  source "drivers/misc/vmw_vmci/Kconfig" | 
|---|
| 559 |  | -source "drivers/misc/mic/Kconfig"  | 
|---|
| 560 | 509 |  source "drivers/misc/genwqe/Kconfig" | 
|---|
| 561 | 510 |  source "drivers/misc/echo/Kconfig" | 
|---|
| 562 | 511 |  source "drivers/misc/cxl/Kconfig" | 
|---|
| 563 | 512 |  source "drivers/misc/ocxl/Kconfig" | 
|---|
| 564 | 513 |  source "drivers/misc/cardreader/Kconfig" | 
|---|
 | 514 | +source "drivers/misc/habanalabs/Kconfig"  | 
|---|
 | 515 | +source "drivers/misc/uacce/Kconfig"  | 
|---|
| 565 | 516 |  endmenu | 
|---|