Kconfig 21 KB

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