remoteproc/omap: report device exceptions and trigger recovery

The OMAP remote processors send a special mailbox message
(RP_MBOX_CRASH) when they crash and detect an internal device
exception.

Add support to the mailbox handling function upon detection of
this special message to report this crash to the remoteproc core.
The remoteproc core can trigger a recovery using the prevailing
recovery mechanism, already in use for MMU Fault recovery.

Signed-off-by: Subramaniam Chanderashekarapuram <subramaniam.ca@ti.com>
Signed-off-by: Suman Anna <s-anna@ti.com>

diff --git a/drivers/remoteproc/omap_remoteproc.c b/drivers/remoteproc/omap_remoteproc.c
index 2016de9e650d34d11934578369f169b99682a4d5..db39527bde0b5d6494b79d13390ef659a21a9c1f 100644 (file)
--- a/drivers/remoteproc/omap_remoteproc.c
+++ b/drivers/remoteproc/omap_remoteproc.c
@@ -356,8 +356,12 @@ static void omap_rproc_mbox_callback(struct mbox_client *client, void *data)
 
        switch (msg) {
        case RP_MBOX_CRASH:
-               /* just log this for now. later, we'll also do recovery */
+               /*
+                * remoteproc detected an exception, notify the rproc core.
+                * The remoteproc core will handle the recovery.
+                */
                dev_err(dev, "omap rproc %s crashed\n", name);
+               rproc_report_crash(oproc->rproc, RPROC_FATAL_ERROR);
                break;
        case RP_MBOX_ECHO_REPLY:
                dev_info(dev, "received echo reply from %s\n", name);