summaryrefslogtreecommitdiffstats
path: root/drivers/pci/pcie
diff options
context:
space:
mode:
authorNaveen Naidu <naveennaidu479@gmail.com>2021-11-18 19:33:28 +0530
committerBjorn Helgaas <bhelgaas@google.com>2021-11-18 14:13:18 -0600
commita3b0f10db148f57591bd4559f01246a06a6a7e72 (patch)
treeb6dc0e4da07e1351c2b63b58c91f877682fc0948 /drivers/pci/pcie
parent242f288e82a34b4c10f87e121b0755056675e55d (diff)
downloadlinux-a3b0f10db148f57591bd4559f01246a06a6a7e72.tar.bz2
PCI: pciehp: 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. Compile tested only. Link: https://lore.kernel.org/r/e185b052fbfd530df703a36dd31126cb870eed95.1637243717.git.naveennaidu479@gmail.com Signed-off-by: Naveen Naidu <naveennaidu479@gmail.com> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com> Acked-by: Lukas Wunner <lukas@wunner.de>
Diffstat (limited to 'drivers/pci/pcie')
0 files changed, 0 insertions, 0 deletions