[PATCH v2 0/2] remoteproc: k3: Recover a crashed remote core
From: Chrispine Tinega
Date: Mon Nov 16 2026 - 13:42:08 EST
A K3 remote core can tell Linux it has crashed by sending RP_MBOX_CRASH,
but the K3 drivers only log it. Nothing reaches the remoteproc core, so
the crash is not counted and recovery never runs. The core stays halted
until the next boot, with its rpmsg channels dead.
Patch 1 reports the crash with rproc_report_crash(). This applies to
every K3 remote that uses the common mailbox callback.
Patch 2 enables recovery on the M4F when Linux booted it. Its stop is a
plain reset, so recovery does not need the crashed core to answer. In
IPC-only mode recovery stays disabled, because it would boot the
firmware Linux has, which need not be the one started before Linux.
The R5F and DSP drivers keep recovery disabled. A crashed core there
moves to RPROC_CRASHED, and can be stopped and started again through
sysfs. On the R5F, recovery itself would not restart the core yet: the
reset it needs is applied in unprepare(), which recovery does not call.
Tested on an AM625 board (BLIIoT BL350) running TI's 6.12 kernel with
the equivalent change. The M4F runs Zephyr, whose fatal-error handler
sends RP_MBOX_CRASH. After a forced fault, recovery reset and rebooted
the M4F in 71 ms, and Linux kept running. Mainline's M4F stop is the
same plain reset that this test used for a crashed core. The Zephyr
side is https://github.com/zephyrproject-rtos/zephyr/pull/125770.
Changes in v2:
- Patch 1: drop the duplicate crash print, and note the R5F limit in
the commit message. (Francesco)
- Patch 2: keep recovery disabled in IPC-only mode. (Francesco)
- Rebased onto rproc-next.
v1: https://lore.kernel.org/all/20261109054830.42715-1-dev@xxxxxxxxxxxxxxxxxxx/
Chrispine Tinega (2):
remoteproc: k3: Report a remote crash to the remoteproc core
remoteproc: k3-m4: Enable crash recovery for a core Linux booted
drivers/remoteproc/ti_k3_common.c | 6 +-----
drivers/remoteproc/ti_k3_m4_remoteproc.c | 6 +++++-
2 files changed, 6 insertions(+), 6 deletions(-)
base-commit: 3035b6708f61259c93a368238e206dcec313e584
--
2.53.0