diff options
| author | Shaohua Li <shaohua.li@intel.com> | 2006-05-26 10:58:27 +0800 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@suse.de> | 2006-06-21 12:00:00 -0700 |
| commit | 99dc804d9bcc2c53f4c20c291bf4e185312a1a0c (patch) | |
| tree | 4798f39176d0f8fe06de446d74cf94ba48423aa9 /drivers/pci/pci.c | |
| parent | 020d502488bebdbc1b2c2828d996f04e563f082a (diff) | |
| download | kernel_samsung_smdk4412-99dc804d9bcc2c53f4c20c291bf4e185312a1a0c.zip kernel_samsung_smdk4412-99dc804d9bcc2c53f4c20c291bf4e185312a1a0c.tar.gz kernel_samsung_smdk4412-99dc804d9bcc2c53f4c20c291bf4e185312a1a0c.tar.bz2 | |
[PATCH] PCI: disable msi mode in pci_disable_device
Brice said the pci_save_msi_state breaks his driver in his special usage
(not in suspend/resume), as pci_save_msi_state will disable msi mode. In
his usage, pci_save_state will be called at runtime, and later (after
the device operates for some time and has an error) pci_restore_state
will be called.
In another hand, suspend/resume needs disable msi mode, as device should
stop working completely. This patch try to workaround this issue.
Drivers are expected call pci_disable_device in suspend time after
pci_save_state.
Signed-off-by: Shaohua Li <shaohua.li@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/pci/pci.c')
| -rw-r--r-- | drivers/pci/pci.c | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c index aa48037..d408a3c 100644 --- a/drivers/pci/pci.c +++ b/drivers/pci/pci.c @@ -551,7 +551,14 @@ void pci_disable_device(struct pci_dev *dev) { u16 pci_command; - + + if (dev->msi_enabled) + disable_msi_mode(dev, pci_find_capability(dev, PCI_CAP_ID_MSI), + PCI_CAP_ID_MSI); + if (dev->msix_enabled) + disable_msi_mode(dev, pci_find_capability(dev, PCI_CAP_ID_MSI), + PCI_CAP_ID_MSIX); + pci_read_config_word(dev, PCI_COMMAND, &pci_command); if (pci_command & PCI_COMMAND_MASTER) { pci_command &= ~PCI_COMMAND_MASTER; |