> The issue is, if pci_enable_msix() fails, we want to fall back to MSI, > so you need to call pci_enable_msi() for that (after calling > pci_disable_msi() before calling pci_enable_msix(), what a mess...) It is messy in that case, but still preferable to having MSI code in every driver. I suppose most devices will not use MSI-X for some time... -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [RFC PATCH] PCI: remove access to pci_[enable|disable]_msi() for drivers
- From: Grant Grundler <[email protected]>
- Re: [RFC PATCH] PCI: remove access to pci_[enable|disable]_msi() for drivers
- References:
- [RFC PATCH] PCI: remove access to pci_[enable|disable]_msi() for drivers
- From: Greg KH <[email protected]>
- Re: [RFC PATCH] PCI: remove access to pci_[enable|disable]_msi() for drivers
- From: Andrew Vasquez <[email protected]>
- Re: [RFC PATCH] PCI: remove access to pci_[enable|disable]_msi() for drivers
- From: Greg KH <[email protected]>
- Re: [RFC PATCH] PCI: remove access to pci_[enable|disable]_msi() for drivers
- From: Arjan van de Ven <[email protected]>
- Re: [RFC PATCH] PCI: remove access to pci_[enable|disable]_msi() for drivers
- From: Greg KH <[email protected]>
- [RFC PATCH] PCI: remove access to pci_[enable|disable]_msi() for drivers
- Prev by Date: segfaults suddenly appearing
- Next by Date: Re: [Penance PATCH] PCI: clean up the MSI code a bit
- Previous by thread: Re: [RFC PATCH] PCI: remove access to pci_[enable|disable]_msi() for drivers
- Next by thread: Re: [RFC PATCH] PCI: remove access to pci_[enable|disable]_msi() for drivers
- Index(es):
 |