| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1 | # |
| 2 | # PCI configuration |
| 3 | # |
| Dan Williams | f282b970 | 2007-04-18 18:46:20 +1000 | [diff] [blame^] | 4 | config ARCH_SUPPORTS_MSI |
| 5 | bool |
| 6 | default n |
| 7 | |
| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 8 | config PCI_MSI |
| 9 | bool "Message Signaled Interrupts (MSI and MSI-X)" |
| 10 | depends on PCI |
| Dan Williams | f282b970 | 2007-04-18 18:46:20 +1000 | [diff] [blame^] | 11 | depends on ARCH_SUPPORTS_MSI |
| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 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 | |
| Matthew Wilcox | 309e57d | 2006-03-05 22:33:34 -0700 | [diff] [blame] | 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 | |
| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 22 | If you don't know what to do here, say N. |
| 23 | |
| Greg Kroah-Hartman | 0f397f8 | 2006-07-18 10:59:59 -0700 | [diff] [blame] | 24 | config PCI_MULTITHREAD_PROBE |
| 25 | bool "PCI Multi-threaded probe (EXPERIMENTAL)" |
| Andrew Morton | fd8d4b1 | 2006-12-14 16:40:00 -0800 | [diff] [blame] | 26 | depends on PCI && EXPERIMENTAL && BROKEN |
| Greg Kroah-Hartman | 0f397f8 | 2006-07-18 10:59:59 -0700 | [diff] [blame] | 27 | help |
| 28 | Say Y here if you want the PCI core to spawn a new thread for |
| 29 | every PCI device that is probed. This can cause a huge |
| 30 | speedup in boot times on multiprocessor machines, and even a |
| 31 | smaller speedup on single processor machines. |
| 32 | |
| 33 | But it can also cause lots of bad things to happen. A number |
| Matt LaPlante | 3cb2fcc | 2006-11-30 05:22:59 +0100 | [diff] [blame] | 34 | of PCI drivers cannot properly handle running in this way, |
| Greg Kroah-Hartman | 0f397f8 | 2006-07-18 10:59:59 -0700 | [diff] [blame] | 35 | some will just not work properly at all, while others might |
| 36 | decide to blow up power supplies with a huge load all at once, |
| 37 | so use this option at your own risk. |
| 38 | |
| 39 | It is very unwise to use this option if you are not using a |
| 40 | boot process that can handle devices being created in any |
| Jan Engelhardt | 03a67a4 | 2006-11-30 05:32:19 +0100 | [diff] [blame] | 41 | order. A program that can create persistent block and network |
| Greg Kroah-Hartman | 0f397f8 | 2006-07-18 10:59:59 -0700 | [diff] [blame] | 42 | device names (like udev) is a good idea if you wish to use |
| 43 | this option. |
| 44 | |
| 45 | Again, use this option at your own risk, you have been warned! |
| 46 | |
| 47 | When in doubt, say N. |
| 48 | |
| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 49 | config PCI_DEBUG |
| 50 | bool "PCI Debugging" |
| 51 | depends on PCI && DEBUG_KERNEL |
| 52 | help |
| 53 | Say Y here if you want the PCI core to produce a bunch of debug |
| 54 | messages to the system log. Select this if you are having a |
| 55 | problem with PCI support and want to see more of what is going on. |
| 56 | |
| 57 | When in doubt, say N. |
| 58 | |
| Eric W. Biederman | 8b955b0 | 2006-10-04 02:16:55 -0700 | [diff] [blame] | 59 | config HT_IRQ |
| 60 | bool "Interrupts on hypertransport devices" |
| 61 | default y |
| Adrian Bunk | fbab41c | 2006-10-11 01:22:04 -0700 | [diff] [blame] | 62 | depends on PCI && X86_LOCAL_APIC && X86_IO_APIC |
| Eric W. Biederman | 8b955b0 | 2006-10-04 02:16:55 -0700 | [diff] [blame] | 63 | help |
| 64 | This allows native hypertransport devices to use interrupts. |
| 65 | |
| 66 | If unsure say Y. |