From: Chrispine Tinega <dev@chrispinetinega.com>
To: andersson@kernel.org, mathieu.poirier@linaro.org
Cc: linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
francesco@valla.it, Chrispine Tinega <dev@chrispinetinega.com>
Subject: [PATCH v2 0/2] remoteproc: k3: Recover a crashed remote core
Date: Mon, 16 Nov 2026 21:41:43 +0300 [thread overview]
Message-ID: <20261116184146.1897281-1-dev@chrispinetinega.com> (raw)
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@chrispinetinega.com/
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
next reply other threads:[~2026-11-16 18:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 18:41 Chrispine Tinega [this message]
2026-11-16 18:41 ` [PATCH v2 1/2] remoteproc: k3: Report a remote crash to the remoteproc core Chrispine Tinega
2026-11-16 18:41 ` [PATCH v2 2/2] remoteproc: k3-m4: Enable crash recovery for a core Linux booted Chrispine Tinega
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261116184146.1897281-1-dev@chrispinetinega.com \
--to=dev@chrispinetinega.com \
--cc=andersson@kernel.org \
--cc=francesco@valla.it \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®