summaryrefslogtreecommitdiff
path: root/drivers/pci/controller/dwc/pcie-designware.c
diff options
context:
space:
mode:
authorJim Quinlan <james.quinlan@broadcom.com>2025-10-29 15:36:15 -0400
committerBjorn Helgaas <bhelgaas@google.com>2025-11-13 10:47:16 -0600
commit8d4ec3fbb15e97b58c395398c743453012bbb93f (patch)
tree1d10e256da385730802db7b524eb1af6b90d0d6e /drivers/pci/controller/dwc/pcie-designware.c
parenta3f00f24d67014721e4efed9238be77b5b67f6fe (diff)
PCI: brcmstb: Add panic/die handler to driver
Most PCIe HW returns 0xffffffff for failed reads on PCIe, but by default Broadcom's STB PCIe controller effects an abort. Some SoCs -- 7216 and its descendants -- have new HW that identifies error details. Add a simple handler to print diagnostic info in case the PCIe controller was the cause of the abort. Unfortunately, an abort still occurs. Read the error registers only when the PCIe bridge is active and the PCIe registers are accessible. Otherwise, a "die" event caused by something other than PCIe could cause an abort if the PCIe "die" handler tried to access registers when the bridge is off. Example error output: brcm-pcie 8b20000.pcie: Error: Mem Acc: 32bit, read, @0x38000000 brcm-pcie 8b20000.pcie: Type: TO=0 Abt=0 UnspReq=1 AccDsble=0 BadAddr=0 Signed-off-by: Jim Quinlan <james.quinlan@broadcom.com> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com> Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com> Link: https://patch.msgid.link/20251029193616.3670003-3-james.quinlan@broadcom.com
Diffstat (limited to 'drivers/pci/controller/dwc/pcie-designware.c')
0 files changed, 0 insertions, 0 deletions