1# SPDX-License-Identifier: GPL-2.0
  2#
  3# PCI configuration
  4#
  5
  6# select this to offer the PCI prompt
  7config HAVE_PCI
  8	bool
  9
 10# select this to unconditionally force on PCI support
 11config 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
 18config GENERIC_PCI_IOMAP
 19	bool
 20
 21menuconfig PCI
 22	bool "PCI support"
 23	depends on HAVE_PCI
 24	help
 25	  This option enables support for the PCI local bus, including
 26	  support for PCI-X and the foundations for PCI Express support.
 27	  Say 'Y' here unless you know what you are doing.
 28
 29if PCI
 30
 31config PCI_DOMAINS
 32	bool
 33	depends on PCI
 34
 35config PCI_DOMAINS_GENERIC
 36	bool
 37	select PCI_DOMAINS
 38
 39config PCI_SYSCALL
 40	bool
 41
 42source "drivers/pci/pcie/Kconfig"
 43
 44config 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
 59config PCI_MSI_ARCH_FALLBACKS
 60	bool
 61
 62config 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
 70config 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
 80config 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
 92config 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
100config 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
111config 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
121config PCI_ATS
122	bool
123
124config PCI_DOE
125	bool
126
127config PCI_ECAM
128	bool
129
130config PCI_LOCKLESS_CONFIG
131	bool
132
133config PCI_BRIDGE_EMUL
134	bool
135
136config PCI_IOV
137	bool "PCI IOV support"
 
138	select PCI_ATS
139	help
140	  I/O Virtualization is a PCI feature supported by some devices
141	  which allows them to create virtual devices which share their
142	  physical resources.
143
144	  If unsure, say N.
145
146config PCI_NPEM
147	bool "Native PCIe Enclosure Management"
148	depends on LEDS_CLASS=y
149	help
150	  Support for Native PCIe Enclosure Management. It allows managing LED
151	  indications in storage enclosures. Enclosure must support following
152	  indications: OK, Locate, Fail, Rebuild, other indications are
153	  optional.
154
155config PCI_PRI
156	bool "PCI PRI support"
 
157	select PCI_ATS
158	help
159	  PRI is the PCI Page Request Interface. It allows PCI devices that are
160	  behind an IOMMU to recover from page faults.
161
162	  If unsure, say N.
163
164config PCI_PASID
165	bool "PCI PASID support"
 
166	select PCI_ATS
167	help
168	  Process Address Space Identifiers (PASIDs) can be used by PCI devices
169	  to access more than one IO address space at the same time. To make
170	  use of this feature an IOMMU is required which also supports PASIDs.
171	  Select this option if you have such an IOMMU and want to compile the
172	  driver for it into your kernel.
173
174	  If unsure, say N.
175
176config PCIE_TPH
177	bool "TLP Processing Hints"
178	help
179	  This option adds support for PCIe TLP Processing Hints (TPH).
180	  TPH allows endpoint devices to provide optimization hints, such as
181	  desired caching behavior, for requests that target memory space.
182	  These hints, called Steering Tags, can empower the system hardware
183	  to optimize the utilization of platform resources.
184
185config PCI_P2PDMA
186	bool "PCI peer-to-peer transfer support"
187	depends on ZONE_DEVICE
188	#
189	# The need for the scatterlist DMA bus address flag means PCI P2PDMA
190	# requires 64bit
191	#
192	depends on 64BIT
193	select GENERIC_ALLOCATOR
194	select NEED_SG_DMA_FLAGS
195	help
196	  Enables drivers to do PCI peer-to-peer transactions to and from
197	  BARs that are exposed in other devices that are the part of
198	  the hierarchy where peer-to-peer DMA is guaranteed by the PCI
199	  specification to work (ie. anything below a single PCI bridge).
200
201	  Many PCIe root complexes do not support P2P transactions and
202	  it's hard to tell which support it at all, so at this time,
203	  P2P DMA transactions must be between devices behind the same root
204	  port.
205
206	  If unsure, say N.
207
208config PCI_LABEL
209	def_bool y if (DMI || ACPI)
210	select NLS
211
212config PCI_HYPERV
213	tristate "Hyper-V PCI Frontend"
214	depends on ((X86 && X86_64) || ARM64) && HYPERV && PCI_MSI && SYSFS
215	select PCI_HYPERV_INTERFACE
216	help
217	  The PCI device frontend driver allows the kernel to import arbitrary
218	  PCI devices from a PCI backend to support PCI driver domains.
219
220config PCI_DYNAMIC_OF_NODES
221	bool "Create Device tree nodes for PCI devices"
222	depends on OF_IRQ
223	select OF_DYNAMIC
224	help
225	  This option enables support for generating device tree nodes for some
226	  PCI devices. Thus, the driver of this kind can load and overlay
227	  flattened device tree for its downstream devices.
228
229	  Once this option is selected, the device tree nodes will be generated
230	  for all PCI bridges.
231
232choice
233	prompt "PCI Express hierarchy optimization setting"
234	default PCIE_BUS_DEFAULT
235	depends on PCI && EXPERT
236	help
237	  MPS (Max Payload Size) and MRRS (Max Read Request Size) are PCIe
238	  device parameters that affect performance and the ability to
239	  support hotplug and peer-to-peer DMA.
240
241	  The following choices set the MPS and MRRS optimization strategy
242	  at compile-time.  The choices are the same as those offered for
243	  the kernel command-line parameter 'pci', i.e.,
244	  'pci=pcie_bus_tune_off', 'pci=pcie_bus_safe',
245	  'pci=pcie_bus_perf', and 'pci=pcie_bus_peer2peer'.
246
247	  This is a compile-time setting and can be overridden by the above
248	  command-line parameters.  If unsure, choose PCIE_BUS_DEFAULT.
249
250config PCIE_BUS_TUNE_OFF
251	bool "Tune Off"
252	depends on PCI
253	help
254	  Use the BIOS defaults; don't touch MPS at all.  This is the same
255	  as booting with 'pci=pcie_bus_tune_off'.
256
257config PCIE_BUS_DEFAULT
258	bool "Default"
259	depends on PCI
260	help
261	  Default choice; ensure that the MPS matches upstream bridge.
262
263config PCIE_BUS_SAFE
264	bool "Safe"
265	depends on PCI
266	help
267	  Use largest MPS that boot-time devices support.  If you have a
268	  closed system with no possibility of adding new devices, this
269	  will use the largest MPS that's supported by all devices.  This
270	  is the same as booting with 'pci=pcie_bus_safe'.
271
272config PCIE_BUS_PERFORMANCE
273	bool "Performance"
274	depends on PCI
275	help
276	  Use MPS and MRRS for best performance.  Ensure that a given
277	  device's MPS is no larger than its parent MPS, which allows us to
278	  keep all switches/bridges to the max MPS supported by their
279	  parent.  This is the same as booting with 'pci=pcie_bus_perf'.
280
281config PCIE_BUS_PEER2PEER
282	bool "Peer2peer"
283	depends on PCI
284	help
285	  Set MPS = 128 for all devices.  MPS configuration effected by the
286	  other options could cause the MPS on one root port to be
287	  different than that of the MPS on another, which may cause
288	  hot-added devices or peer-to-peer DMA to fail.  Set MPS to the
289	  smallest possible value (128B) system-wide to avoid these issues.
290	  This is the same as booting with 'pci=pcie_bus_peer2peer'.
291
292endchoice
293
294config VGA_ARB
295	bool "VGA Arbitration" if EXPERT
296	default y
297	depends on (PCI && !S390)
298	help
299	  Some "legacy" VGA devices implemented on PCI typically have the same
300	  hard-decoded addresses as they did on ISA. When multiple PCI devices
301	  are accessed at same time they need some kind of coordination. Please
302	  see Documentation/gpu/vgaarbiter.rst for more details. Select this to
303	  enable VGA arbiter.
304
305config VGA_ARB_MAX_GPUS
306	int "Maximum number of GPUs"
307	default 16
308	depends on VGA_ARB
309	help
310	  Reserves space in the kernel to maintain resource locking for
311	  multiple GPUS.  The overhead for each GPU is very small.
312
313source "drivers/pci/hotplug/Kconfig"
314source "drivers/pci/controller/Kconfig"
315source "drivers/pci/endpoint/Kconfig"
316source "drivers/pci/switch/Kconfig"
317source "drivers/pci/pwrctrl/Kconfig"
318
319endif

 
  1#
  2# PCI configuration
  3#
  4
  5source "drivers/pci/pcie/Kconfig"
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
  6
  7config PCI_BUS_ADDR_T_64BIT
  8	def_bool y if (ARCH_DMA_ADDR_T_64BIT || 64BIT)
  9	depends on PCI
 10
 
 
 
 
 
 
 
 
 
 11config PCI_MSI
 12	bool "Message Signaled Interrupts (MSI and MSI-X)"
 13	depends on PCI
 14	select GENERIC_MSI_IRQ
 15	help
 16	   This allows device drivers to enable MSI (Message Signaled
 17	   Interrupts).  Message Signaled Interrupts enable a device to
 18	   generate an interrupt using an inbound Memory Write on its
 19	   PCI bus instead of asserting a device IRQ pin.
 20
 21	   Use of PCI MSI interrupts can be disabled at kernel boot time
 22	   by using the 'pci=nomsi' option.  This disables MSI for the
 23	   entire system.
 24
 25	   If you don't know what to do here, say Y.
 26
 27config PCI_MSI_IRQ_DOMAIN
 28	def_bool ARC || ARM || ARM64 || X86
 29	depends on PCI_MSI
 30	select GENERIC_MSI_IRQ_DOMAIN
 
 
 
 
 
 
 31
 32config PCI_DEBUG
 33	bool "PCI Debugging"
 34	depends on PCI && DEBUG_KERNEL
 35	help
 36	  Say Y here if you want the PCI core to produce a bunch of debug
 37	  messages to the system log.  Select this if you are having a
 38	  problem with PCI support and want to see more of what is going on.
 39
 40	  When in doubt, say N.
 41
 42config PCI_REALLOC_ENABLE_AUTO
 43	bool "Enable PCI resource re-allocation detection"
 44	depends on PCI
 45	help
 46	  Say Y here if you want the PCI core to detect if PCI resource
 47	  re-allocation needs to be enabled. You can always use pci=realloc=on
 48          or pci=realloc=off to override it.  Note this feature is a no-op
 49          unless PCI_IOV support is also enabled; in that case it will
 50          automatically re-allocate PCI resources if SR-IOV BARs have not
 51          been allocated by the BIOS.
 52
 53	  When in doubt, say N.
 54
 55config PCI_STUB
 56	tristate "PCI Stub driver"
 57	depends on PCI
 58	help
 59	  Say Y or M here if you want be able to reserve a PCI device
 60	  when it is going to be assigned to a guest operating system.
 61
 62	  When in doubt, say N.
 63
 
 
 
 
 
 
 
 
 
 
 
 64config XEN_PCIDEV_FRONTEND
 65        tristate "Xen PCI Frontend"
 66        depends on PCI && X86 && XEN
 67        select PCI_XEN
 68	select XEN_XENBUS_FRONTEND
 69        default y
 70        help
 71          The PCI device frontend driver allows the kernel to import arbitrary
 72          PCI devices from a PCI backend to support PCI driver domains.
 73
 74config HT_IRQ
 75	bool "Interrupts on hypertransport devices"
 76	default y
 77	depends on PCI && X86_LOCAL_APIC
 78	help
 79	   This allows native hypertransport devices to use interrupts.
 
 80
 81	   If unsure say Y.
 
 82
 83config PCI_ATS
 84	bool
 85
 86config PCI_ECAM
 87	bool
 88
 
 
 
 
 
 
 89config PCI_IOV
 90	bool "PCI IOV support"
 91	depends on PCI
 92	select PCI_ATS
 93	help
 94	  I/O Virtualization is a PCI feature supported by some devices
 95	  which allows them to create virtual devices which share their
 96	  physical resources.
 97
 98	  If unsure, say N.
 99
 
 
 
 
 
 
 
 
 
100config PCI_PRI
101	bool "PCI PRI support"
102	depends on PCI
103	select PCI_ATS
104	help
105	  PRI is the PCI Page Request Interface. It allows PCI devices that are
106	  behind an IOMMU to recover from page faults.
107
108	  If unsure, say N.
109
110config PCI_PASID
111	bool "PCI PASID support"
112	depends on PCI
113	select PCI_ATS
114	help
115	  Process Address Space Identifiers (PASIDs) can be used by PCI devices
116	  to access more than one IO address space at the same time. To make
117	  use of this feature an IOMMU is required which also supports PASIDs.
118	  Select this option if you have such an IOMMU and want to compile the
119	  driver for it into your kernel.
120
121	  If unsure, say N.
122
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
123config PCI_LABEL
124	def_bool y if (DMI || ACPI)
125	select NLS
126
127config PCI_HYPERV
128        tristate "Hyper-V PCI Frontend"
129        depends on PCI && X86 && HYPERV && PCI_MSI && PCI_MSI_IRQ_DOMAIN && X86_64
130        help
131          The PCI device frontend driver allows the kernel to import arbitrary
132          PCI devices from a PCI backend to support PCI driver domains.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
133
134source "drivers/pci/hotplug/Kconfig"
135source "drivers/pci/host/Kconfig"