summaryrefslogtreecommitdiff
path: root/tools/lib/python/kdoc/python_version.py
diff options
context:
space:
mode:
authorDaniel Machon <daniel.machon@microchip.com>2026-09-28 21:32:57 +0200
committerJakub Kicinski <kuba@kernel.org>2026-10-02 13:08:55 -0700
commit58e73ef6a1e50b1516560ea981a18606633add26 (patch)
treecdd6e7f8c2621b6e1cdd76a60b735bf5ebb56a83 /tools/lib/python/kdoc/python_version.py
parent5a97c2c00b8e02aa2b27f5d445c004b1e7af9499 (diff)
net: lan966x: clear FDMA interrupt stickies after switch reset
When in PCI mode, the GCB soft reset issued by the reset controller can latch spurious bits in the FDMA error stickies. The latched bits sit in FDMA_INTR_ERR until the FDMA IRQ is requested later in probe, at which point the handler fires immediately and WARNs. Clear FDMA_ERRORS, FDMA_INTR_ERR and FDMA_INTR_DB right after the switch reset so the FDMA comes out clean and the IRQ handler does not see ghost errors on probe. The clear runs on both the PCI and platform paths. On the platform path it has no effect — there are no spurious stickies to clear — but keeping it unconditional avoids a PCI-specific code path here. Tested-by: Herve Codina <herve.codina@bootlin.com> Signed-off-by: Daniel Machon <daniel.machon@microchip.com> Reviewed-by: Simon Horman <horms@kernel.org> Link: https://patch.msgid.link/20260928-lan966x-pci-fdma-v9-9-a17caf60f89a@microchip.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions