| 1 | # SPDX-License-Identifier: GPL-2.0 |
| 2 | # |
| 3 | # PCI configuration |
| 4 | # |
| 5 | |
| 6 | # select this to offer the PCI prompt |
| 7 | config HAVE_PCI |
| 8 | bool |
| 9 | |
| 10 | # select this to unconditionally force on PCI support |
| 11 | config FORCE_PCI |
| 12 | bool |
| 13 | select HAVE_PCI |
| 14 | select PCI |
| 15 | |
| 16 | # select this to provide a generic PCI iomap, |
| 17 | # without PCI itself having to be defined |
| 18 | config GENERIC_PCI_IOMAP |
| 19 | bool |
| 20 | |
| 21 | menuconfig PCI |
| 22 | bool "PCI support" |
| 23 | depends on HAVE_PCI |
| 24 | depends on MMU |
| 25 | help |
| 26 | This option enables support for the PCI local bus, including |
| 27 | support for PCI-X and the foundations for PCI Express support. |
| 28 | Say 'Y' here unless you know what you are doing. |
| 29 | |
| 30 | if PCI |
| 31 | |
| 32 | config PCI_DOMAINS |
| 33 | bool |
| 34 | |
| 35 | config PCI_DOMAINS_GENERIC |
| 36 | bool |
| 37 | select PCI_DOMAINS |
| 38 | |
| 39 | config PCI_SYSCALL |
| 40 | bool |
| 41 | |
| 42 | source "drivers/pci/pcie/Kconfig" |
| 43 | |
| 44 | config PCI_MSI |
| 45 | bool "Message Signaled Interrupts (MSI and MSI-X)" |
| 46 | select GENERIC_MSI_IRQ |
| 47 | help |
| 48 | This allows device drivers to enable MSI (Message Signaled |
| 49 | Interrupts). Message Signaled Interrupts enable a device to |
| 50 | generate an interrupt using an inbound Memory Write on its |
| 51 | PCI bus instead of asserting a device IRQ pin. |
| 52 | |
| 53 | Use of PCI MSI interrupts can be disabled at kernel boot time |
| 54 | by using the 'pci=nomsi' option. This disables MSI for the |
| 55 | entire system. |
| 56 | |
| 57 | If you don't know what to do here, say Y. |
| 58 | |
| 59 | config PCI_MSI_ARCH_FALLBACKS |
| 60 | bool |
| 61 | |
| 62 | config PCI_QUIRKS |
| 63 | default y |
| 64 | bool "Enable PCI quirk workarounds" if EXPERT |
| 65 | help |
| 66 | This enables workarounds for various PCI chipset bugs/quirks. |
| 67 | Disable this only if your target machine is unaffected by PCI |
| 68 | quirks. |
| 69 | |
| 70 | config PCI_DEBUG |
| 71 | bool "PCI Debugging" |
| 72 | depends on DEBUG_KERNEL |
| 73 | help |
| 74 | Say Y here if you want the PCI core to produce a bunch of debug |
| 75 | messages to the system log. Select this if you are having a |
| 76 | problem with PCI support and want to see more of what is going on. |
| 77 | |
| 78 | When in doubt, say N. |
| 79 | |
| 80 | config PCI_REALLOC_ENABLE_AUTO |
| 81 | bool "Enable PCI resource re-allocation detection" |
| 82 | depends on PCI_IOV |
| 83 | help |
| 84 | Say Y here if you want the PCI core to detect if PCI resource |
| 85 | re-allocation needs to be enabled. You can always use pci=realloc=on |
| 86 | or pci=realloc=off to override it. It will automatically |
| 87 | re-allocate PCI resources if SR-IOV BARs have not been allocated by |
| 88 | the BIOS. |
| 89 | |
| 90 | When in doubt, say N. |
| 91 | |
| 92 | config PCI_STUB |
| 93 | tristate "PCI Stub driver" |
| 94 | help |
| 95 | Say Y or M here if you want be able to reserve a PCI device |
| 96 | when it is going to be assigned to a guest operating system. |
| 97 | |
| 98 | When in doubt, say N. |
| 99 | |
| 100 | config PCI_PF_STUB |
| 101 | tristate "PCI PF Stub driver" |
| 102 | depends on PCI_IOV |
| 103 | help |
| 104 | Say Y or M here if you want to enable support for devices that |
| 105 | require SR-IOV support, while at the same time the PF (Physical |
| 106 | Function) itself is not providing any actual services on the |
| 107 | host itself such as storage or networking. |
| 108 | |
| 109 | When in doubt, say N. |
| 110 | |
| 111 | config XEN_PCIDEV_FRONTEND |
| 112 | tristate "Xen PCI Frontend" |
| 113 | depends on XEN_PV |
| 114 | select PCI_XEN |
| 115 | select XEN_XENBUS_FRONTEND |
| 116 | default y |
| 117 | help |
| 118 | The PCI device frontend driver allows the kernel to import arbitrary |
| 119 | PCI devices from a PCI backend to support PCI driver domains. |
| 120 | |
| 121 | config PCI_ATS |
| 122 | bool |
| 123 | |
| 124 | config PCI_IDE |
| 125 | bool |
| 126 | |
| 127 | config PCI_TSM |
| 128 | bool "PCI TSM: Device security protocol support" |
| 129 | select PCI_IDE |
| 130 | select PCI_DOE |
| 131 | select TSM |
| 132 | help |
| 133 | The TEE (Trusted Execution Environment) Device Interface |
| 134 | Security Protocol (TDISP) defines a "TSM" as a platform agent |
| 135 | that manages device authentication, link encryption, link |
| 136 | integrity protection, and assignment of PCI device functions |
| 137 | (virtual or physical) to confidential computing VMs that can |
| 138 | access (DMA) guest private memory. |
| 139 | |
| 140 | Enable a platform TSM driver to use this capability. |
| 141 | |
| 142 | config PCI_DOE |
| 143 | bool "Enable PCI Data Object Exchange (DOE) support" |
| 144 | help |
| 145 | Say Y here if you want be able to communicate with PCIe DOE |
| 146 | mailboxes. |
| 147 | |
| 148 | config PCI_ECAM |
| 149 | bool |
| 150 | |
| 151 | config PCI_LOCKLESS_CONFIG |
| 152 | bool |
| 153 | |
| 154 | config PCI_BRIDGE_EMUL |
| 155 | bool |
| 156 | |
| 157 | config PCI_IOV |
| 158 | bool "PCI IOV support" |
| 159 | select PCI_ATS |
| 160 | help |
| 161 | I/O Virtualization is a PCI feature supported by some devices |
| 162 | which allows them to create virtual devices which share their |
| 163 | physical resources. |
| 164 | |
| 165 | If unsure, say N. |
| 166 | |
| 167 | config PCI_NPEM |
| 168 | bool "Native PCIe Enclosure Management" |
| 169 | depends on LEDS_CLASS=y |
| 170 | help |
| 171 | Support for Native PCIe Enclosure Management. It allows managing LED |
| 172 | indications in storage enclosures. Enclosure must support following |
| 173 | indications: OK, Locate, Fail, Rebuild, other indications are |
| 174 | optional. |
| 175 | |
| 176 | config PCI_PRI |
| 177 | bool "PCI PRI support" |
| 178 | select PCI_ATS |
| 179 | help |
| 180 | PRI is the PCI Page Request Interface. It allows PCI devices that are |
| 181 | behind an IOMMU to recover from page faults. |
| 182 | |
| 183 | If unsure, say N. |
| 184 | |
| 185 | config PCI_PASID |
| 186 | bool "PCI PASID support" |
| 187 | select PCI_ATS |
| 188 | help |
| 189 | Process Address Space Identifiers (PASIDs) can be used by PCI devices |
| 190 | to access more than one IO address space at the same time. To make |
| 191 | use of this feature an IOMMU is required which also supports PASIDs. |
| 192 | Select this option if you have such an IOMMU and want to compile the |
| 193 | driver for it into your kernel. |
| 194 | |
| 195 | If unsure, say N. |
| 196 | |
| 197 | config PCIE_TPH |
| 198 | bool "TLP Processing Hints" |
| 199 | help |
| 200 | This option adds support for PCIe TLP Processing Hints (TPH). |
| 201 | TPH allows endpoint devices to provide optimization hints, such as |
| 202 | desired caching behavior, for requests that target memory space. |
| 203 | These hints, called Steering Tags, can empower the system hardware |
| 204 | to optimize the utilization of platform resources. |
| 205 | |
| 206 | config PCI_P2PDMA |
| 207 | bool "PCI peer-to-peer transfer support" |
| 208 | depends on ZONE_DEVICE |
| 209 | # |
| 210 | # The need for the scatterlist DMA bus address flag means PCI P2PDMA |
| 211 | # requires 64bit |
| 212 | # |
| 213 | depends on 64BIT |
| 214 | select GENERIC_ALLOCATOR |
| 215 | select NEED_SG_DMA_FLAGS |
| 216 | help |
| 217 | Enables drivers to do PCI peer-to-peer transactions to and from |
| 218 | BARs that are exposed in other devices that are the part of |
| 219 | the hierarchy where peer-to-peer DMA is guaranteed by the PCI |
| 220 | specification to work (ie. anything below a single PCI bridge). |
| 221 | |
| 222 | Many PCIe root complexes do not support P2P transactions and |
| 223 | it's hard to tell which support it at all, so at this time, |
| 224 | P2P DMA transactions must be between devices behind the same root |
| 225 | port. |
| 226 | |
| 227 | If unsure, say N. |
| 228 | |
| 229 | config PCI_LABEL |
| 230 | def_bool y if (DMI || ACPI) |
| 231 | select NLS |
| 232 | |
| 233 | config PCI_HYPERV |
| 234 | tristate "Hyper-V PCI Frontend" |
| 235 | depends on ((X86 && X86_64) || ARM64) && HYPERV_VMBUS && PCI_MSI && SYSFS |
| 236 | select PCI_HYPERV_INTERFACE |
| 237 | select IRQ_MSI_LIB |
| 238 | help |
| 239 | The PCI device frontend driver allows the kernel to import arbitrary |
| 240 | PCI devices from a PCI backend to support PCI driver domains. |
| 241 | |
| 242 | config PCI_DYNAMIC_OF_NODES |
| 243 | bool "Create Device tree nodes for PCI devices" |
| 244 | depends on OF_IRQ |
| 245 | select OF_DYNAMIC |
| 246 | help |
| 247 | This option enables support for generating device tree nodes for some |
| 248 | PCI devices. Thus, the driver of this kind can load and overlay |
| 249 | flattened device tree for its downstream devices. |
| 250 | |
| 251 | Once this option is selected, the device tree nodes will be generated |
| 252 | for all PCI bridges. |
| 253 | |
| 254 | config VGA_ARB |
| 255 | bool "VGA Arbitration" if EXPERT |
| 256 | default y |
| 257 | depends on !S390 |
| 258 | select SCREEN_INFO if X86 |
| 259 | help |
| 260 | Some "legacy" VGA devices implemented on PCI typically have the same |
| 261 | hard-decoded addresses as they did on ISA. When multiple PCI devices |
| 262 | are accessed at same time they need some kind of coordination. Please |
| 263 | see Documentation/gpu/vgaarbiter.rst for more details. Select this to |
| 264 | enable VGA arbiter. |
| 265 | |
| 266 | config VGA_ARB_MAX_GPUS |
| 267 | int "Maximum number of GPUs" |
| 268 | default 16 |
| 269 | depends on VGA_ARB |
| 270 | help |
| 271 | Reserves space in the kernel to maintain resource locking for |
| 272 | multiple GPUS. The overhead for each GPU is very small. |
| 273 | |
| 274 | source "drivers/pci/hotplug/Kconfig" |
| 275 | source "drivers/pci/controller/Kconfig" |
| 276 | source "drivers/pci/endpoint/Kconfig" |
| 277 | source "drivers/pci/switch/Kconfig" |
| 278 | source "drivers/pci/pwrctrl/Kconfig" |
| 279 | |
| 280 | endif # PCI |