Kconfig 22 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663
  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. help
  90. Unified RPMB unit interface for RPMB capable devices such as eMMC and
  91. UFS. Provides interface for in-kernel security controllers to access
  92. RPMB unit.
  93. If unsure, select N.
  94. config TI_FPC202
  95. tristate "TI FPC202 Dual Port Controller"
  96. depends on I2C
  97. select GPIOLIB
  98. select I2C_ATR
  99. help
  100. If you say yes here you get support for the Texas Instruments FPC202
  101. Dual Port Controller.
  102. This driver can also be built as a module. If so, the module will be
  103. called fpc202.
  104. config TIFM_CORE
  105. tristate "TI Flash Media interface support"
  106. depends on PCI
  107. help
  108. If you want support for Texas Instruments(R) Flash Media adapters
  109. you should select this option and then also choose an appropriate
  110. host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
  111. support', if you have a TI PCI74xx compatible card reader, for
  112. example.
  113. You will also have to select some flash card format drivers. MMC/SD
  114. cards are supported via 'MMC/SD Card support: TI Flash Media MMC/SD
  115. Interface support (MMC_TIFM_SD)'.
  116. To compile this driver as a module, choose M here: the module will
  117. be called tifm_core.
  118. config TIFM_7XX1
  119. tristate "TI Flash Media PCI74xx/PCI76xx host adapter support"
  120. depends on PCI && TIFM_CORE
  121. default TIFM_CORE
  122. help
  123. This option enables support for Texas Instruments(R) PCI74xx and
  124. PCI76xx families of Flash Media adapters, found in many laptops.
  125. To make actual use of the device, you will have to select some
  126. flash card format drivers, as outlined in the TIFM_CORE Help.
  127. To compile this driver as a module, choose M here: the module will
  128. be called tifm_7xx1.
  129. config ICS932S401
  130. tristate "Integrated Circuits ICS932S401"
  131. depends on I2C
  132. help
  133. If you say yes here you get support for the Integrated Circuits
  134. ICS932S401 clock control chips.
  135. This driver can also be built as a module. If so, the module
  136. will be called ics932s401.
  137. config ATMEL_SSC
  138. tristate "Device driver for Atmel SSC peripheral"
  139. depends on HAS_IOMEM && (ARCH_AT91 || COMPILE_TEST)
  140. help
  141. This option enables device driver support for Atmel Synchronized
  142. Serial Communication peripheral (SSC).
  143. The SSC peripheral supports a wide variety of serial frame based
  144. communications, i.e. I2S, SPI, etc.
  145. If unsure, say N.
  146. config ENCLOSURE_SERVICES
  147. tristate "Enclosure Services"
  148. help
  149. Provides support for intelligent enclosures (bays which
  150. contain storage devices). You also need either a host
  151. driver (SCSI/ATA) which supports enclosures
  152. or a SCSI enclosure device (SES) to use these services.
  153. config SGI_XP
  154. tristate "Support communication between SGI SSIs"
  155. depends on NET
  156. depends on X86_UV && SMP
  157. depends on X86_64 || BROKEN
  158. select SGI_GRU if X86_64 && SMP
  159. help
  160. An SGI machine can be divided into multiple Single System
  161. Images which act independently of each other and have
  162. hardware based memory protection from the others. Enabling
  163. this feature will allow for direct communication between SSIs
  164. based on a network adapter and DMA messaging.
  165. config SMPRO_ERRMON
  166. tristate "Ampere Computing SMPro error monitor driver"
  167. depends on MFD_SMPRO || COMPILE_TEST
  168. help
  169. Say Y here to get support for the SMpro error monitor function
  170. provided by Ampere Computing's Altra and Altra Max SoCs. Upon
  171. loading, the driver creates sysfs files which can be use to gather
  172. multiple HW error data reported via read and write system calls.
  173. To compile this driver as a module, say M here. The driver will be
  174. called smpro-errmon.
  175. config SMPRO_MISC
  176. tristate "Ampere Computing SMPro miscellaneous driver"
  177. depends on MFD_SMPRO || COMPILE_TEST
  178. help
  179. Say Y here to get support for the SMpro error miscellalenous function
  180. provided by Ampere Computing's Altra and Altra Max SoCs.
  181. To compile this driver as a module, say M here. The driver will be
  182. called smpro-misc.
  183. config CS5535_MFGPT
  184. tristate "CS5535/CS5536 Geode Multi-Function General Purpose Timer (MFGPT) support"
  185. depends on MFD_CS5535
  186. help
  187. This driver provides access to MFGPT functionality for other
  188. drivers that need timers. MFGPTs are available in the CS5535 and
  189. CS5536 companion chips that are found in AMD Geode and several
  190. other platforms. They have a better resolution and max interval
  191. than the generic PIT, and are suitable for use as high-res timers.
  192. You probably don't want to enable this manually; other drivers that
  193. make use of it should enable it.
  194. config CS5535_MFGPT_DEFAULT_IRQ
  195. int
  196. depends on CS5535_MFGPT
  197. default 7
  198. help
  199. MFGPTs on the CS5535 require an interrupt. The selected IRQ
  200. can be overridden as a module option as well as by driver that
  201. use the cs5535_mfgpt_ API; however, different architectures might
  202. want to use a different IRQ by default. This is here for
  203. architectures to set as necessary.
  204. config CS5535_CLOCK_EVENT_SRC
  205. tristate "CS5535/CS5536 high-res timer (MFGPT) events"
  206. depends on GENERIC_CLOCKEVENTS && CS5535_MFGPT
  207. help
  208. This driver provides a clock event source based on the MFGPT
  209. timer(s) in the CS5535 and CS5536 companion chips.
  210. MFGPTs have a better resolution and max interval than the
  211. generic PIT, and are suitable for use as high-res timers.
  212. config GEHC_ACHC
  213. tristate "GEHC ACHC support"
  214. depends on SPI && SYSFS
  215. depends on SOC_IMX53 || COMPILE_TEST
  216. select FW_LOADER
  217. help
  218. Support for GE ACHC microcontroller, that is part of the GE
  219. PPD device.
  220. To compile this driver as a module, choose M here: the
  221. module will be called gehc-achc.
  222. config HI6421V600_IRQ
  223. tristate "HiSilicon Hi6421v600 IRQ and powerkey"
  224. depends on OF
  225. depends on SPMI
  226. depends on HAS_IOMEM
  227. select MFD_CORE
  228. select REGMAP_SPMI
  229. help
  230. This driver provides IRQ handling for Hi6421v600, used on
  231. some Kirin chipsets, like the one at Hikey 970.
  232. config HP_ILO
  233. tristate "Channel interface driver for the HP iLO processor"
  234. depends on PCI
  235. help
  236. The channel interface driver allows applications to communicate
  237. with iLO management processors present on HP ProLiant servers.
  238. Upon loading, the driver creates /dev/hpilo/dXccbN files, which
  239. can be used to gather data from the management processor, via
  240. read and write system calls.
  241. To compile this driver as a module, choose M here: the
  242. module will be called hpilo.
  243. config QCOM_COINCELL
  244. tristate "Qualcomm coincell charger support"
  245. depends on MFD_SPMI_PMIC || COMPILE_TEST
  246. help
  247. This driver supports the coincell block found inside of
  248. Qualcomm PMICs. The coincell charger provides a means to
  249. charge a coincell battery or backup capacitor which is used
  250. to maintain PMIC register and RTC state in the absence of
  251. external power.
  252. config QCOM_FASTRPC
  253. tristate "Qualcomm FastRPC"
  254. depends on ARCH_QCOM || COMPILE_TEST
  255. depends on RPMSG
  256. select DMA_SHARED_BUFFER
  257. select QCOM_SCM
  258. help
  259. Provides a communication mechanism that allows for clients to
  260. make remote method invocations across processor boundary to
  261. applications DSP processor. Say M if you want to enable this
  262. module.
  263. config SGI_GRU
  264. tristate "SGI GRU driver"
  265. depends on X86_UV && SMP
  266. select MMU_NOTIFIER
  267. help
  268. The GRU is a hardware resource located in the system chipset. The GRU
  269. contains memory that can be mmapped into the user address space.
  270. This memory is used to communicate with the GRU to perform functions
  271. such as load/store, scatter/gather, bcopy, AMOs, etc. The GRU is
  272. directly accessed by user instructions using user virtual addresses.
  273. GRU instructions (ex., bcopy) use user virtual addresses for operands.
  274. If you are not running on a SGI UV system, say N.
  275. config SGI_GRU_DEBUG
  276. bool "SGI GRU driver debug"
  277. depends on SGI_GRU
  278. help
  279. This option enables additional debugging code for the SGI GRU driver.
  280. If you are unsure, say N.
  281. config APDS9802ALS
  282. tristate "Medfield Avago APDS9802 ALS Sensor module"
  283. depends on I2C
  284. help
  285. If you say yes here you get support for the ALS APDS9802 ambient
  286. light sensor.
  287. This driver can also be built as a module. If so, the module
  288. will be called apds9802als.
  289. config ISL29003
  290. tristate "Intersil ISL29003 ambient light sensor"
  291. depends on I2C && SYSFS
  292. help
  293. If you say yes here you get support for the Intersil ISL29003
  294. ambient light sensor.
  295. This driver can also be built as a module. If so, the module
  296. will be called isl29003.
  297. config ISL29020
  298. tristate "Intersil ISL29020 ambient light sensor"
  299. depends on I2C
  300. help
  301. If you say yes here you get support for the Intersil ISL29020
  302. ambient light sensor.
  303. This driver can also be built as a module. If so, the module
  304. will be called isl29020.
  305. config SENSORS_TSL2550
  306. tristate "Taos TSL2550 ambient light sensor"
  307. depends on I2C && SYSFS
  308. help
  309. If you say yes here you get support for the Taos TSL2550
  310. ambient light sensor.
  311. This driver can also be built as a module. If so, the module
  312. will be called tsl2550.
  313. config SENSORS_BH1770
  314. tristate "BH1770GLC / SFH7770 combined ALS - Proximity sensor"
  315. depends on I2C
  316. help
  317. Say Y here if you want to build a driver for BH1770GLC (ROHM) or
  318. SFH7770 (Osram) combined ambient light and proximity sensor chip.
  319. To compile this driver as a module, choose M here: the
  320. module will be called bh1770glc. If unsure, say N here.
  321. config SENSORS_APDS990X
  322. tristate "APDS990X combined als and proximity sensors"
  323. depends on I2C
  324. help
  325. Say Y here if you want to build a driver for Avago APDS990x
  326. combined ambient light and proximity sensor chip.
  327. To compile this driver as a module, choose M here: the
  328. module will be called apds990x. If unsure, say N here.
  329. config HMC6352
  330. tristate "Honeywell HMC6352 compass"
  331. depends on I2C
  332. help
  333. This driver provides support for the Honeywell HMC6352 compass,
  334. providing configuration and heading data via sysfs.
  335. config DS1682
  336. tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
  337. depends on I2C
  338. help
  339. If you say yes here you get support for Dallas Semiconductor
  340. DS1682 Total Elapsed Time Recorder.
  341. This driver can also be built as a module. If so, the module
  342. will be called ds1682.
  343. config VMWARE_BALLOON
  344. tristate "VMware Balloon Driver"
  345. depends on VMWARE_VMCI && X86 && HYPERVISOR_GUEST
  346. select BALLOON
  347. help
  348. This is VMware physical memory management driver which acts
  349. like a "balloon" that can be inflated to reclaim physical pages
  350. by reserving them in the guest and invalidating them in the
  351. monitor, freeing up the underlying machine pages so they can
  352. be allocated to other guests. The balloon can also be deflated
  353. to allow the guest to use more physical memory.
  354. If unsure, say N.
  355. To compile this driver as a module, choose M here: the
  356. module will be called vmw_balloon.
  357. config PCH_PHUB
  358. tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) PHUB"
  359. select GENERIC_NET_UTILS
  360. depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
  361. help
  362. This driver is for PCH(Platform controller Hub) PHUB(Packet Hub) of
  363. Intel Topcliff which is an IOH(Input/Output Hub) for x86 embedded
  364. processor. The Topcliff has MAC address and Option ROM data in SROM.
  365. This driver can access MAC address and Option ROM data in SROM.
  366. This driver also can be used for LAPIS Semiconductor's IOH,
  367. ML7213/ML7223/ML7831.
  368. ML7213 which is for IVI(In-Vehicle Infotainment) use.
  369. ML7223 IOH is for MP(Media Phone) use.
  370. ML7831 IOH is for general purpose use.
  371. ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
  372. ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
  373. To compile this driver as a module, choose M here: the module will
  374. be called pch_phub.
  375. config LATTICE_ECP3_CONFIG
  376. tristate "Lattice ECP3 FPGA bitstream configuration via SPI"
  377. depends on SPI && SYSFS
  378. select FW_LOADER
  379. help
  380. This option enables support for bitstream configuration (programming
  381. or loading) of the Lattice ECP3 FPGA family via SPI.
  382. If unsure, say N.
  383. config SRAM
  384. bool "Generic on-chip SRAM driver"
  385. depends on HAS_IOMEM
  386. select GENERIC_ALLOCATOR
  387. select SRAM_EXEC if ARM
  388. help
  389. This driver allows you to declare a memory region to be managed by
  390. the genalloc API. It is supposed to be used for small on-chip SRAM
  391. areas found on many SoCs.
  392. config SRAM_EXEC
  393. bool
  394. config DW_XDATA_PCIE
  395. depends on PCI
  396. tristate "Synopsys DesignWare xData PCIe driver"
  397. help
  398. This driver allows controlling Synopsys DesignWare PCIe traffic
  399. generator IP also known as xData, present in Synopsys DesignWare
  400. PCIe Endpoint prototype.
  401. If unsure, say N.
  402. config PCI_ENDPOINT_TEST
  403. depends on PCI
  404. select CRC32
  405. tristate "PCI Endpoint Test driver"
  406. help
  407. Enable this configuration option to enable the host side test driver
  408. for PCI Endpoint.
  409. config XILINX_SDFEC
  410. tristate "Xilinx SDFEC 16"
  411. depends on HAS_IOMEM
  412. help
  413. This option enables support for the Xilinx SDFEC (Soft Decision
  414. Forward Error Correction) driver. This enables a char driver
  415. for the SDFEC.
  416. You may select this driver if your design instantiates the
  417. SDFEC(16nm) hardened block. To compile this as a module choose M.
  418. If unsure, say N.
  419. config MISC_RTSX
  420. tristate
  421. default MISC_RTSX_PCI || MISC_RTSX_USB
  422. config HISI_HIKEY_USB
  423. tristate "USB GPIO Hub on HiSilicon Hikey 960/970 Platform"
  424. depends on (OF && GPIOLIB) || COMPILE_TEST
  425. depends on USB_ROLE_SWITCH
  426. help
  427. If you say yes here this adds support for the on-board USB GPIO hub
  428. found on HiKey 960/970 boards, which is necessary to support
  429. switching between the dual-role USB-C port and the USB-A host ports
  430. using only one USB controller.
  431. config OPEN_DICE
  432. tristate "Open Profile for DICE driver"
  433. depends on OF_RESERVED_MEM
  434. depends on HAS_IOMEM
  435. help
  436. This driver exposes a DICE reserved memory region to userspace via
  437. a character device. The memory region contains Compound Device
  438. Identifiers (CDIs) generated by firmware as an output of DICE
  439. measured boot flow. Userspace can use CDIs for remote attestation
  440. and sealing.
  441. If unsure, say N.
  442. config NTSYNC
  443. tristate "NT synchronization primitive emulation"
  444. help
  445. This module provides kernel support for emulation of Windows NT
  446. synchronization primitives. It is not a hardware driver.
  447. To compile this driver as a module, choose M here: the
  448. module will be called ntsync.
  449. If unsure, say N.
  450. config VCPU_STALL_DETECTOR
  451. tristate "Guest vCPU stall detector"
  452. depends on OF && HAS_IOMEM
  453. help
  454. When this driver is bound inside a KVM guest, it will
  455. periodically "pet" an MMIO stall detector device from each vCPU
  456. and allow the host to detect vCPU stalls.
  457. To compile this driver as a module, choose M here: the module
  458. will be called vcpu_stall_detector.
  459. If you do not intend to run this kernel as a guest, say N.
  460. config TMR_MANAGER
  461. tristate "Select TMR Manager"
  462. depends on MICROBLAZE && MB_MANAGER
  463. help
  464. This option enables the driver developed for TMR Manager.
  465. The Triple Modular Redundancy(TMR) manager provides support for
  466. fault detection.
  467. Say N here unless you know what you are doing.
  468. config TMR_INJECT
  469. tristate "Select TMR Inject"
  470. depends on TMR_MANAGER && FAULT_INJECTION_DEBUG_FS
  471. help
  472. This option enables the driver developed for TMR Inject.
  473. The Triple Modular Redundancy(TMR) Inject provides
  474. fault injection.
  475. Say N here unless you know what you are doing.
  476. config TPS6594_ESM
  477. tristate "TI TPS6594 Error Signal Monitor support"
  478. depends on MFD_TPS6594
  479. default MFD_TPS6594
  480. help
  481. Support ESM (Error Signal Monitor) on TPS6594 PMIC devices.
  482. ESM is used typically to reboot the board in error condition.
  483. This driver can also be built as a module. If so, the module
  484. will be called tps6594-esm.
  485. config TPS6594_PFSM
  486. tristate "TI TPS6594 Pre-configurable Finite State Machine support"
  487. depends on MFD_TPS6594
  488. default MFD_TPS6594
  489. help
  490. Support PFSM (Pre-configurable Finite State Machine) on TPS6594 PMIC devices.
  491. These devices integrate a finite state machine engine, which manages the state
  492. of the device during operating state transition.
  493. This driver can also be built as a module. If so, the module
  494. will be called tps6594-pfsm.
  495. config NSM
  496. tristate "Nitro (Enclaves) Security Module support"
  497. depends on VIRTIO
  498. select HW_RANDOM
  499. help
  500. This driver provides support for the Nitro Security Module
  501. in AWS EC2 Nitro based Enclaves. The driver exposes a /dev/nsm
  502. device user space can use to communicate with the hypervisor.
  503. To compile this driver as a module, choose M here.
  504. The module will be called nsm.
  505. config MARVELL_CN10K_DPI
  506. tristate "Octeon CN10K DPI driver"
  507. depends on PCI && PCI_IOV
  508. depends on ARCH_THUNDER || (COMPILE_TEST && 64BIT)
  509. help
  510. Enables Octeon CN10K DMA packet interface (DPI) driver which
  511. intializes DPI hardware's physical function (PF) device's
  512. global configuration and its virtual function (VFs) resource
  513. configuration to enable DMA transfers. DPI PF device does not
  514. have any data movement functionality, it only serves VF's
  515. resource configuration requests.
  516. To compile this driver as a module, choose M here: the module
  517. will be called mrvl_cn10k_dpi.
  518. config MCHP_LAN966X_PCI
  519. tristate "Microchip LAN966x PCIe Support"
  520. depends on PCI
  521. depends on OF_OVERLAY
  522. select IRQ_DOMAIN
  523. help
  524. This enables the support for the LAN966x PCIe device.
  525. This is used to drive the LAN966x PCIe device from the host system
  526. to which it is connected. The driver uses a device tree overlay to
  527. load other drivers to support for LAN966x internal components.
  528. Even if this driver does not depend on those other drivers, in order
  529. to have a fully functional board, the following drivers are needed:
  530. - fixed-clock (COMMON_CLK)
  531. - lan966x-oic (LAN966X_OIC)
  532. - lan966x-cpu-syscon (MFD_SYSCON)
  533. - lan966x-switch-reset (RESET_MCHP_SPARX5)
  534. - lan966x-pinctrl (PINCTRL_OCELOT)
  535. - lan966x-serdes (PHY_LAN966X_SERDES)
  536. - lan966x-miim (MDIO_MSCC_MIIM)
  537. - lan966x-switch (LAN966X_SWITCH)
  538. source "drivers/misc/c2port/Kconfig"
  539. source "drivers/misc/eeprom/Kconfig"
  540. source "drivers/misc/cb710/Kconfig"
  541. source "drivers/misc/lis3lv02d/Kconfig"
  542. source "drivers/misc/altera-stapl/Kconfig"
  543. source "drivers/misc/mei/Kconfig"
  544. source "drivers/misc/vmw_vmci/Kconfig"
  545. source "drivers/misc/genwqe/Kconfig"
  546. source "drivers/misc/ocxl/Kconfig"
  547. source "drivers/misc/bcm-vk/Kconfig"
  548. source "drivers/misc/cardreader/Kconfig"
  549. source "drivers/misc/uacce/Kconfig"
  550. source "drivers/misc/pvpanic/Kconfig"
  551. source "drivers/misc/mchp_pci1xxxx/Kconfig"
  552. source "drivers/misc/keba/Kconfig"
  553. source "drivers/misc/amd-sbi/Kconfig"
  554. source "drivers/misc/rp1/Kconfig"
  555. endmenu