diff options
author | Naveen Naidu <naveennaidu479@gmail.com> | 2021-11-18 17:03:30 +0300 |
---|---|---|
committer | Bjorn Helgaas <bhelgaas@google.com> | 2021-11-18 23:13:18 +0300 |
commit | aa66ea10ba843d35582afaadc0b2f60af063b806 (patch) | |
tree | 18c80cefd9fb607fcf484a81c1352a4b041ea9b4 /scripts/gdb/linux/utils.py | |
parent | 0242132da26a928801cbb6ab96daf77e7815e084 (diff) | |
download | linux-aa66ea10ba843d35582afaadc0b2f60af063b806.tar.xz |
PCI/PME: 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/679ce049bccf10df3ca9ef4918ee2c3235afdaea.1637243717.git.naveennaidu479@gmail.com
Signed-off-by: Naveen Naidu <naveennaidu479@gmail.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions