diff options
| author | David S. Miller <davem@davemloft.net> | 2017-02-13 09:30:22 -0500 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2017-02-13 09:30:22 -0500 |
| commit | caa137eea6927e6412c9cfe5cb3e20abb5575101 (patch) | |
| tree | decc33265ddacc252aafe6ec735daa70377a13a7 | |
| parent | 3b03cc0783b03ddd668ff3f86419bc67d0664e89 (diff) | |
| parent | 61303736638aa923b40c9e107b64e6d2b7af499d (diff) | |
Merge branch 'mv88e6xxx-Watchdog-support'
Andrew Lunn says:
====================
mv88e6xxx Watchdog support
The Marvell switches have an in built watchdog over some of the
internal state machine. The watchdog can be configured to raise an
interrupt on error. The problem the watchdog found is then logged to
the kernel log.
The older switches can automagically perform a software reset when the
watchdog triggers. This just resets the internal state machine, but
leaves the switch configuration unchanged.
The 6390 family of switches cannot both raise an interrupt and
automagically perform a software reset. So the interrupt handler has
to perform the switch reset, and then re-enable the watchdog
interrupts.
This has been tested using hacked together debugfs code which allows
the "force" bit to be set, so cause a watchdog interrupt.
v2: Remove g2_prefix
====================
Signed-off-by: David S. Miller <davem@davemloft.net>