2005-04-17 02:20:36 +04:00
|
|
|
#
|
|
|
|
|
# PCI configuration
|
|
|
|
|
#
|
2007-04-18 12:46:20 +04:00
|
|
|
config ARCH_SUPPORTS_MSI
|
|
|
|
|
bool
|
|
|
|
|
|
2005-04-17 02:20:36 +04:00
|
|
|
config PCI_MSI
|
|
|
|
|
bool "Message Signaled Interrupts (MSI and MSI-X)"
|
|
|
|
|
depends on PCI
|
2007-04-18 12:46:20 +04:00
|
|
|
depends on ARCH_SUPPORTS_MSI
|
2005-04-17 02:20:36 +04:00
|
|
|
help
|
|
|
|
|
This allows device drivers to enable MSI (Message Signaled
|
|
|
|
|
Interrupts). Message Signaled Interrupts enable a device to
|
|
|
|
|
generate an interrupt using an inbound Memory Write on its
|
|
|
|
|
PCI bus instead of asserting a device IRQ pin.
|
|
|
|
|
|
2006-03-06 08:33:34 +03:00
|
|
|
Use of PCI MSI interrupts can be disabled at kernel boot time
|
|
|
|
|
by using the 'pci=nomsi' option. This disables MSI for the
|
|
|
|
|
entire system.
|
|
|
|
|
|
2010-04-08 20:38:47 +04:00
|
|
|
If you don't know what to do here, say Y.
|
2005-04-17 02:20:36 +04:00
|
|
|
|
|
|
|
|
config PCI_DEBUG
|
|
|
|
|
bool "PCI Debugging"
|
|
|
|
|
depends on PCI && DEBUG_KERNEL
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want the PCI core to produce a bunch of debug
|
|
|
|
|
messages to the system log. Select this if you are having a
|
|
|
|
|
problem with PCI support and want to see more of what is going on.
|
|
|
|
|
|
|
|
|
|
When in doubt, say N.
|
|
|
|
|
|
2012-02-24 07:23:32 +04:00
|
|
|
config PCI_REALLOC_ENABLE_AUTO
|
|
|
|
|
bool "Enable PCI resource re-allocation detection"
|
|
|
|
|
depends on PCI
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you want the PCI core to detect if PCI resource
|
|
|
|
|
re-allocation needs to be enabled. You can always use pci=realloc=on
|
|
|
|
|
or pci=realloc=off to override it. Note this feature is a no-op
|
|
|
|
|
unless PCI_IOV support is also enabled; in that case it will
|
|
|
|
|
automatically re-allocate PCI resources if SR-IOV BARs have not
|
|
|
|
|
been allocated by the BIOS.
|
|
|
|
|
|
|
|
|
|
When in doubt, say N.
|
|
|
|
|
|
2008-11-26 08:17:13 +03:00
|
|
|
config PCI_STUB
|
|
|
|
|
tristate "PCI Stub driver"
|
|
|
|
|
depends on PCI
|
|
|
|
|
help
|
|
|
|
|
Say Y or M here if you want be able to reserve a PCI device
|
|
|
|
|
when it is going to be assigned to a guest operating system.
|
|
|
|
|
|
|
|
|
|
When in doubt, say N.
|
|
|
|
|
|
2010-08-03 05:31:05 +04:00
|
|
|
config XEN_PCIDEV_FRONTEND
|
|
|
|
|
tristate "Xen PCI Frontend"
|
|
|
|
|
depends on PCI && X86 && XEN
|
|
|
|
|
select HOTPLUG
|
|
|
|
|
select PCI_XEN
|
2010-12-11 06:33:15 +03:00
|
|
|
select XEN_XENBUS_FRONTEND
|
2010-08-03 05:31:05 +04:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
The PCI device frontend driver allows the kernel to import arbitrary
|
|
|
|
|
PCI devices from a PCI backend to support PCI driver domains.
|
|
|
|
|
|
2006-10-04 13:16:55 +04:00
|
|
|
config HT_IRQ
|
|
|
|
|
bool "Interrupts on hypertransport devices"
|
|
|
|
|
default y
|
2006-10-11 12:22:04 +04:00
|
|
|
depends on PCI && X86_LOCAL_APIC && X86_IO_APIC
|
2006-10-04 13:16:55 +04:00
|
|
|
help
|
|
|
|
|
This allows native hypertransport devices to use interrupts.
|
|
|
|
|
|
|
|
|
|
If unsure say Y.
|
2009-03-20 06:25:11 +03:00
|
|
|
|
2011-09-27 17:57:13 +04:00
|
|
|
config PCI_ATS
|
|
|
|
|
bool
|
|
|
|
|
|
2009-03-20 06:25:11 +03:00
|
|
|
config PCI_IOV
|
|
|
|
|
bool "PCI IOV support"
|
|
|
|
|
depends on PCI
|
2011-09-27 17:57:13 +04:00
|
|
|
select PCI_ATS
|
2009-03-20 06:25:11 +03:00
|
|
|
help
|
|
|
|
|
I/O Virtualization is a PCI feature supported by some devices
|
|
|
|
|
which allows them to create virtual devices which share their
|
|
|
|
|
physical resources.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
PCI hotplug: move IOAPIC support from acpiphp to ioapic driver
This patch moves PCI I/O APIC support from acpiphp to a separate driver.
Like pciehp and shpchp, acpiphp handles PCI hotplug, i.e., addition and
removal of PCI adapters. But in addition, acpiphp handles some ACPI
hotplug, such as the addition of new host bridges, and the I/O APIC
support was tangled up with that.
I don't think the I/O APIC support needs to be in acpiphp; PCI I/O APICs
usually appear as a function on a PCI host bridge, and we'll enumerate the
APIC before any of the devices behind the bridge that use it.
As far as I know, nobody actually uses I/O APIC hotplug. It depends on
acpi_register_ioapic(), which is only implemented for ia64, and I don't
think any vendors have supported I/O chassis hotplug yet.
Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
Reviewed-by: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
CC: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
CC: MUNEDA Takahiro <muneda.takahiro@jp.fujitsu.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2009-10-26 20:20:47 +03:00
|
|
|
|
2011-09-27 17:57:15 +04:00
|
|
|
config PCI_PRI
|
|
|
|
|
bool "PCI PRI support"
|
2011-10-30 19:35:07 +04:00
|
|
|
depends on PCI
|
2011-09-27 17:57:15 +04:00
|
|
|
select PCI_ATS
|
|
|
|
|
help
|
|
|
|
|
PRI is the PCI Page Request Interface. It allows PCI devices that are
|
|
|
|
|
behind an IOMMU to recover from page faults.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2011-09-27 17:57:16 +04:00
|
|
|
config PCI_PASID
|
|
|
|
|
bool "PCI PASID support"
|
|
|
|
|
depends on PCI
|
|
|
|
|
select PCI_ATS
|
|
|
|
|
help
|
|
|
|
|
Process Address Space Identifiers (PASIDs) can be used by PCI devices
|
|
|
|
|
to access more than one IO address space at the same time. To make
|
|
|
|
|
use of this feature an IOMMU is required which also supports PASIDs.
|
|
|
|
|
Select this option if you have such an IOMMU and want to compile the
|
|
|
|
|
driver for it into your kernel.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
PCI hotplug: move IOAPIC support from acpiphp to ioapic driver
This patch moves PCI I/O APIC support from acpiphp to a separate driver.
Like pciehp and shpchp, acpiphp handles PCI hotplug, i.e., addition and
removal of PCI adapters. But in addition, acpiphp handles some ACPI
hotplug, such as the addition of new host bridges, and the I/O APIC
support was tangled up with that.
I don't think the I/O APIC support needs to be in acpiphp; PCI I/O APICs
usually appear as a function on a PCI host bridge, and we'll enumerate the
APIC before any of the devices behind the bridge that use it.
As far as I know, nobody actually uses I/O APIC hotplug. It depends on
acpi_register_ioapic(), which is only implemented for ia64, and I don't
think any vendors have supported I/O chassis hotplug yet.
Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
Reviewed-by: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
CC: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
CC: MUNEDA Takahiro <muneda.takahiro@jp.fujitsu.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2009-10-26 20:20:47 +03:00
|
|
|
config PCI_IOAPIC
|
2011-12-06 11:49:30 +04:00
|
|
|
tristate "PCI IO-APIC hotplug support" if X86
|
PCI hotplug: move IOAPIC support from acpiphp to ioapic driver
This patch moves PCI I/O APIC support from acpiphp to a separate driver.
Like pciehp and shpchp, acpiphp handles PCI hotplug, i.e., addition and
removal of PCI adapters. But in addition, acpiphp handles some ACPI
hotplug, such as the addition of new host bridges, and the I/O APIC
support was tangled up with that.
I don't think the I/O APIC support needs to be in acpiphp; PCI I/O APICs
usually appear as a function on a PCI host bridge, and we'll enumerate the
APIC before any of the devices behind the bridge that use it.
As far as I know, nobody actually uses I/O APIC hotplug. It depends on
acpi_register_ioapic(), which is only implemented for ia64, and I don't
think any vendors have supported I/O chassis hotplug yet.
Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
Reviewed-by: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
CC: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
CC: MUNEDA Takahiro <muneda.takahiro@jp.fujitsu.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2009-10-26 20:20:47 +03:00
|
|
|
depends on PCI
|
|
|
|
|
depends on ACPI
|
|
|
|
|
depends on HOTPLUG
|
2011-12-06 11:49:30 +04:00
|
|
|
default !X86
|
2011-03-02 20:04:17 +03:00
|
|
|
|
2011-03-29 20:45:57 +04:00
|
|
|
config PCI_LABEL
|
|
|
|
|
def_bool y if (DMI || ACPI)
|
|
|
|
|
select NLS
|
