| author | Suman Anna <s-anna@ti.com> | |
| Thu, 11 May 2017 05:55:59 +0000 (05:55 +0000) | ||
| committer | Suman Anna <s-anna@ti.com> | |
| Mon, 11 Mar 2019 17:02:01 +0000 (12:02 -0500) | ||
| commit | 9582a7a2a16e4096b96b370e180e4f137053a7b4 | |
| tree | 05c2bbe639755d2c30d38f1008c91be91dd5cc15 | tree | snapshot (tar.xz tar.gz zip) |
| parent | 81d5a33c5aa79a15d3e1ebca8c5f226bb68b954a | commit | diff |
remoteproc/omap: fix auto-suspend failure warning during crashed state
The runtime autosuspend on a OMAP remoteproc device is attempted when
the suspend timer expires (autosuspend delay elapsed since the last
time the device is busy). This is the normal autosuspend scenario
for a device functioning normally. This timer can also expire during
the debugging of a remoteproc crash when the remoteproc recovery is
disabled. This is an invalid pre-condition though, so check for the
RPROC_CRASHED state and bail out before the actual check for the
RPROC_RUNNING state. The auto-suspend is also not re-attempted until
the remoteproc is recovered and restored to normal functional state.
Signed-off-by: Suman Anna <s-anna@ti.com>
The runtime autosuspend on a OMAP remoteproc device is attempted when
the suspend timer expires (autosuspend delay elapsed since the last
time the device is busy). This is the normal autosuspend scenario
for a device functioning normally. This timer can also expire during
the debugging of a remoteproc crash when the remoteproc recovery is
disabled. This is an invalid pre-condition though, so check for the
RPROC_CRASHED state and bail out before the actual check for the
RPROC_RUNNING state. The auto-suspend is also not re-attempted until
the remoteproc is recovered and restored to normal functional state.
Signed-off-by: Suman Anna <s-anna@ti.com>
| drivers/remoteproc/omap_remoteproc.c | diff | blob | history |