2005-04-17 00:20:36 +02:00
|
|
|
#
|
|
|
|
# PCI configuration
|
|
|
|
#
|
2007-04-18 10:46:20 +02:00
|
|
|
config ARCH_SUPPORTS_MSI
|
|
|
|
bool
|
|
|
|
default n
|
|
|
|
|
2005-04-17 00:20:36 +02:00
|
|
|
config PCI_MSI
|
|
|
|
bool "Message Signaled Interrupts (MSI and MSI-X)"
|
|
|
|
depends on PCI
|
2007-04-18 10:46:20 +02:00
|
|
|
depends on ARCH_SUPPORTS_MSI
|
2005-04-17 00:20:36 +02: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 06:33:34 +01: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.
|
|
|
|
|
2005-04-17 00:20:36 +02:00
|
|
|
If you don't know what to do here, say N.
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
2006-10-04 11:16:55 +02:00
|
|
|
config HT_IRQ
|
|
|
|
bool "Interrupts on hypertransport devices"
|
|
|
|
default y
|
2006-10-11 10:22:04 +02:00
|
|
|
depends on PCI && X86_LOCAL_APIC && X86_IO_APIC
|
2006-10-04 11:16:55 +02:00
|
|
|
help
|
|
|
|
This allows native hypertransport devices to use interrupts.
|
|
|
|
|
|
|
|
If unsure say Y.
|