diff options
author | Naveen Naidu <naveennaidu479@gmail.com> | 2021-11-18 19:33:26 +0530 |
---|---|---|
committer | Bjorn Helgaas <bhelgaas@google.com> | 2021-11-18 14:12:57 -0600 |
commit | fa52b6447ce1cc0157c89dac7762f1693deeb10e (patch) | |
tree | 21b89ed676e47cf141e603a574372634add9edfd /drivers/pci/controller/vmd.c | |
parent | ba25d181caaa230107531ed440c3163fc814d4b1 (diff) | |
download | linux-fa52b6447ce1cc0157c89dac7762f1693deeb10e.tar.bz2 |
PCI/ERR: Use PCI_POSSIBLE_ERROR() to check config reads
When config pci_ops.read() can detect failed PCI transactions, the data
returned to the CPU is PCI_ERROR_RESPONSE (~0 or 0xffffffff).
Obviously a successful PCI config read may *also* return that data if a
config register happens to contain ~0, so it doesn't definitively indicate
an error unless we know the register cannot contain ~0.
Use PCI_POSSIBLE_ERROR() to check the response we get when we read data
from hardware. This unifies PCI error response checking and makes error
checks consistent and easier to find.
Link: https://lore.kernel.org/r/f4d18d470cb90f9cb52ea155b01528ba2e76e8d6.1637243717.git.naveennaidu479@gmail.com
Signed-off-by: Naveen Naidu <naveennaidu479@gmail.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Diffstat (limited to 'drivers/pci/controller/vmd.c')
0 files changed, 0 insertions, 0 deletions