diff options
author | 2007-10-03 11:15:11 -0700 | |
---|---|---|
committer | 2007-10-12 15:03:17 -0700 | |
commit | cbf5d9e6b9bcf03291cbb51db144b3e2773a8a2d (patch) | |
tree | 494d61012a0d5f23f2af9be72a2e17a1c7f344fc /drivers/pci | |
parent | PCI: Fix incorrect argument order to list_add_tail() in PCI dynamic ID code (diff) | |
download | linux-cbf5d9e6b9bcf03291cbb51db144b3e2773a8a2d.tar.gz linux-cbf5d9e6b9bcf03291cbb51db144b3e2773a8a2d.tar.bz2 linux-cbf5d9e6b9bcf03291cbb51db144b3e2773a8a2d.zip |
MSI: Use correct data offset for 32-bit MSI in read_msi_msg()
While reading the MSI code trying to find a reason why MSI wouldn't
work for devices that have a 32-bit MSI address capability, I noticed
that read_msi_msg() seems to read the message data from the wrong
offset in this case.
Signed-off-by: Roland Dreier <roland@digitalvampire.org>
Acked-by: Eric W. Biederman <ebiederm@xmission.com>
Cc: stable <stable@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/pci')
-rw-r--r-- | drivers/pci/msi.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/pci/msi.c b/drivers/pci/msi.c index be1df85e5e2d..87e01615053d 100644 --- a/drivers/pci/msi.c +++ b/drivers/pci/msi.c @@ -132,7 +132,7 @@ void read_msi_msg(unsigned int irq, struct msi_msg *msg) pci_read_config_word(dev, msi_data_reg(pos, 1), &data); } else { msg->address_hi = 0; - pci_read_config_word(dev, msi_data_reg(pos, 1), &data); + pci_read_config_word(dev, msi_data_reg(pos, 0), &data); } msg->data = data; break; |