From: Chrispine Tinega <dev@chrispinetinega.com>
To: francesco@valla.it
Cc: andersson@kernel.org, mathieu.poirier@linaro.org,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
Chrispine Tinega <dev@chrispinetinega.com>
Subject: Re: [PATCH 2/2] remoteproc: k3-m4: Leave crash recovery enabled
Date: Mon, 16 Nov 2026 21:49:43 +0300 [thread overview]
Message-ID: <20261116184943.1900328-1-dev@chrispinetinega.com> (raw)
In-Reply-To: <avodrGAJY6tZtrpP@bywater>
Hi Francesco,
On Sun, Nov 15, 2026 at 10:04:00PM +0100, Francesco Valla wrote:
> This can be fine for a core started by Linux, but it's not for a core
> working in IPC-only mode, where Linux only attaches. In that case, a
> recovery action might start a firware living on the Linux userspace that
> is different from the one originally started outside of it (and if this
> is enabled by default, the user might not even notice this).
You are right. In v2, which I have just sent, recovery is enabled only
when Linux booted the M4F. In IPC-only mode the driver keeps it
disabled, so a crash there moves the core to "crashed" and nothing is
loaded in its place. A user who knows the firmware matches can still
turn recovery on through /sys/class/remoteproc/remoteprocN/recovery.
Thanks,
Chrispine
next prev parent reply other threads:[~2026-11-16 18:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 5:48 [PATCH 0/2] remoteproc: k3: Recover a crashed remote core Chrispine Tinega
2026-11-09 5:48 ` [PATCH 1/2] remoteproc: k3: Report a remote crash to the remoteproc core Chrispine Tinega
2026-11-11 22:21 ` Francesco Valla
2026-11-12 12:39 ` Chrispine Tinega
2026-11-09 5:48 ` [PATCH 2/2] remoteproc: k3-m4: Leave crash recovery enabled Chrispine Tinega
2026-11-15 21:04 ` Francesco Valla
2026-11-16 18:49 ` Chrispine Tinega [this message]
2026-11-09 6:59 ` [PATCH 0/2] remoteproc: k3: Recover a crashed remote core Francesco Valla
2026-11-09 16:04 ` Chrispine Tinega
2026-11-09 23:55 ` Francesco Valla
2026-11-15 21:11 ` Francesco Valla
2026-11-16 18:50 ` 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=20261116184943.1900328-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®