1# SPDX-License-Identifier: GPL-2.0 2# 3# PCI configuration 4# 5 6source "drivers/pci/pcie/Kconfig" 7 8config PCI_MSI 9 bool "Message Signaled Interrupts (MSI and MSI-X)" 10 depends on PCI 11 select GENERIC_MSI_IRQ 12 help 13 This allows device drivers to enable MSI (Message Signaled 14 Interrupts). Message Signaled Interrupts enable a device to 15 generate an interrupt using an inbound Memory Write on its 16 PCI bus instead of asserting a device IRQ pin. 17 18 Use of PCI MSI interrupts can be disabled at kernel boot time 19 by using the 'pci=nomsi' option. This disables MSI for the 20 entire system. 21 22 If you don't know what to do here, say Y. 23 24config PCI_MSI_IRQ_DOMAIN 25 def_bool ARC || ARM || ARM64 || X86 26 depends on PCI_MSI 27 select GENERIC_MSI_IRQ_DOMAIN 28 29config PCI_QUIRKS 30 default y 31 bool "Enable PCI quirk workarounds" if EXPERT 32 depends on PCI 33 help 34 This enables workarounds for various PCI chipset bugs/quirks. 35 Disable this only if your target machine is unaffected by PCI 36 quirks. 37 38config PCI_DEBUG 39 bool "PCI Debugging" 40 depends on PCI && DEBUG_KERNEL 41 help 42 Say Y here if you want the PCI core to produce a bunch of debug 43 messages to the system log. Select this if you are having a 44 problem with PCI support and want to see more of what is going on. 45 46 When in doubt, say N. 47 48config PCI_REALLOC_ENABLE_AUTO 49 bool "Enable PCI resource re-allocation detection" 50 depends on PCI 51 depends on PCI_IOV 52 help 53 Say Y here if you want the PCI core to detect if PCI resource 54 re-allocation needs to be enabled. You can always use pci=realloc=on 55 or pci=realloc=off to override it. It will automatically 56 re-allocate PCI resources if SR-IOV BARs have not been allocated by 57 the BIOS. 58 59 When in doubt, say N. 60 61config PCI_STUB 62 tristate "PCI Stub driver" 63 depends on PCI 64 help 65 Say Y or M here if you want be able to reserve a PCI device 66 when it is going to be assigned to a guest operating system. 67 68 When in doubt, say N. 69 70config PCI_PF_STUB 71 tristate "PCI PF Stub driver" 72 depends on PCI 73 depends on PCI_IOV 74 help 75 Say Y or M here if you want to enable support for devices that 76 require SR-IOV support, while at the same time the PF itself is 77 not providing any actual services on the host itself such as 78 storage or networking. 79 80 When in doubt, say N. 81 82config XEN_PCIDEV_FRONTEND 83 tristate "Xen PCI Frontend" 84 depends on PCI && X86 && XEN 85 select PCI_XEN 86 select XEN_XENBUS_FRONTEND 87 default y 88 help 89 The PCI device frontend driver allows the kernel to import arbitrary 90 PCI devices from a PCI backend to support PCI driver domains. 91 92config PCI_ATS 93 bool 94 95config PCI_ECAM 96 bool 97 98config PCI_LOCKLESS_CONFIG 99 bool 100 101config PCI_BRIDGE_EMUL 102 bool 103 104config PCI_IOV 105 bool "PCI IOV support" 106 depends on PCI 107 select PCI_ATS 108 help 109 I/O Virtualization is a PCI feature supported by some devices 110 which allows them to create virtual devices which share their 111 physical resources. 112 113 If unsure, say N. 114 115config PCI_PRI 116 bool "PCI PRI support" 117 depends on PCI 118 select PCI_ATS 119 help 120 PRI is the PCI Page Request Interface. It allows PCI devices that are 121 behind an IOMMU to recover from page faults. 122 123 If unsure, say N. 124 125config PCI_PASID 126 bool "PCI PASID support" 127 depends on PCI 128 select PCI_ATS 129 help 130 Process Address Space Identifiers (PASIDs) can be used by PCI devices 131 to access more than one IO address space at the same time. To make 132 use of this feature an IOMMU is required which also supports PASIDs. 133 Select this option if you have such an IOMMU and want to compile the 134 driver for it into your kernel. 135 136 If unsure, say N. 137 138config PCI_P2PDMA 139 bool "PCI peer-to-peer transfer support" 140 depends on PCI && ZONE_DEVICE 141 select GENERIC_ALLOCATOR 142 help 143 Enableѕ drivers to do PCI peer-to-peer transactions to and from 144 BARs that are exposed in other devices that are the part of 145 the hierarchy where peer-to-peer DMA is guaranteed by the PCI 146 specification to work (ie. anything below a single PCI bridge). 147 148 Many PCIe root complexes do not support P2P transactions and 149 it's hard to tell which support it at all, so at this time, 150 P2P DMA transations must be between devices behind the same root 151 port. 152 153 If unsure, say N. 154 155config PCI_LABEL 156 def_bool y if (DMI || ACPI) 157 depends on PCI 158 select NLS 159 160config PCI_HYPERV 161 tristate "Hyper-V PCI Frontend" 162 depends on PCI && X86 && HYPERV && PCI_MSI && PCI_MSI_IRQ_DOMAIN && X86_64 163 help 164 The PCI device frontend driver allows the kernel to import arbitrary 165 PCI devices from a PCI backend to support PCI driver domains. 166 167source "drivers/pci/hotplug/Kconfig" 168source "drivers/pci/controller/Kconfig" 169source "drivers/pci/endpoint/Kconfig" 170source "drivers/pci/switch/Kconfig" 171