diff options
| author | David S. Miller <davem@davemloft.net> | 2020-05-14 23:25:47 +0300 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2020-05-14 23:25:47 +0300 |
| commit | 86b6ba171d4bcce72ffbdc33b42b0b4c0e6d99d0 (patch) | |
| tree | 34e134e5883863ee99868245e5a64af5d41582ef /drivers/net/ethernet/ti | |
| parent | c8a867a38fc8d88a096ebf8813d02bbf50f7335e (diff) | |
| parent | 8f76812e1cc4d561c3efc3b2586c686b5428d31f (diff) | |
| download | linux-86b6ba171d4bcce72ffbdc33b42b0b4c0e6d99d0.tar.xz | |
Merge branch 'net-qed-qede-critical-hw-error-handling'
Igor Russkikh says:
====================
net: qed/qede: critical hw error handling
FastLinQ devices as a complex systems may observe various hardware
level error conditions, both severe and recoverable.
Driver is able to detect and report this, but so far it only did
trace/dmesg based reporting.
Here we implement an extended hw error detection, service task
handler captures a dump for the later analysis.
I also resubmit a patch from Denis Bolotin on tx timeout handler,
addressing David's comment regarding recovery procedure as an extra
reaction on this event.
v2:
Removing the patch with ethtool dump and udev magic. Its quite isolated,
I'm working on devlink based logic for this separately.
v1:
https://patchwork.ozlabs.org/project/netdev/cover/cover.1588758463.git.irusskikh@marvell.com/
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/ethernet/ti')
0 files changed, 0 insertions, 0 deletions