From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=104.207.68.34 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1794854525; b=HPodWDcZKzSs44EQkND9lPMyYNjeLhY25mf0PRmkBnQY+DWoaFnCTPy8gfPPC/4f0AB2 D4N8CoWYXlxxZRAWKIsrFprgP/NgoW+IIAx5MQ0NZmh9vp1PYTI7viKghr0RK6JGtY01R eAcMhRusXRVdWbsPiAtdGOYSrZ0HvZL7f76lfQHnmJg3rWWPadXlGMU4510iJ/bxlK38h 6MBc7s41r1ZTTcqmMT9A5Pi1DH4WROsM9cBMcnm5bSFZ0W606CaPITojivZ1W6shbBuX0 3rUwYaD+lrKmUfS1w60E7nb42RyJRKsfIevSVvx93VSoW4HAhxhmIZ9O7qLT0L8NzYA== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1794854525; h=DMARC-Filter:Received:DKIM-Signature:From:To:Cc:Subject:Date: Message-ID:X-Mailer:MIME-Version:Content-Transfer-Encoding: X-Envelope-From; bh=q0InDNKnpgiQTfM6ZmzG57ILR9PKesybT9FFdKyUp84=; b=KXPlq1B4K+LGQwJhRHgX21opcwQ0P5eY6zlEswjoBxKsjt0xXdT7k+waxs41F/DLe9Zw dnG6JyBcAzj8mi4GB3xuOSm7Bk+0+i/0jTE+NrJWtimBKW+UqxgS02+CjhpQ1AcVdv8qx niIuDJSpUgQPUW0W2xPvxKQ8pDF89WFgWmuOj1/w85s+U7gm92SW3ZeYT0PLg0g68K6ky Expu6FiltIx2IMXCKVc/gTBRZOnqhbzzYzrqzxOkLlwcuo10UVCYkndAC1fE3KEPMM3mg xI3N82wROdEERM0DGN90NrprMqoW7M2itVcUriYL5w/ekVawAteT3KKHPiSr6JK+gDw== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass header.from=chrispinetinega.com; spf=pass smtp.mailfrom=chrispinetinega.com; dkim=pass header.d=chrispinetinega.com header.i=@chrispinetinega.com header.a=rsa-sha256 header.s=default header.b=SJCYkk8T; arc=none smtp.remote-ip=104.207.68.34 Received: from out-93wp-a34.jellyfish.systems (out-93wp-a34.jellyfish.systems [104.207.68.34]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 8C1A1606A323 for ; Mon, 16 Nov 2026 18:42:04 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org 8C1A1606A323 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=chrispinetinega.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=chrispinetinega.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key, unprotected) header.d=chrispinetinega.com header.i=@chrispinetinega.com header.a=rsa-sha256 header.s=default header.b=SJCYkk8T Received: from mail.privateemail.com (unknown [62.8.90.37]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.privateemail.com (Postfix) with ESMTPSA id 4jSxY415DFz2x9J; Mon, 16 Nov 2026 18:41:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chrispinetinega.com; s=default; t=1794854522; bh=q0InDNKnpgiQTfM6ZmzG57ILR9PKesybT9FFdKyUp84=; h=From:To:Cc:Subject:Date:From; b=SJCYkk8T9Qk9hYwS+JkMQ3Rt2BzerwbKv6trhmzmrJZliN6ZBL4XOw8bEPZbpPBBx pLf9K86XXRo+QALjVKe+hhyy5iQRnTPH5KgLDxAU++FN4rz03x6n08tEsT0yq/Wxnl hHGU5xGMX4KoVV7VLr5UGQ8iFe0DXe/N1rSyCEEw3+2k5R8VDBBWaKToPYddpQVRO2 5zSuEkcy98vNYNedgsuYFyjVzMaiyG/TPBnS9R+yQOvoWD27e9ggKtmSw/zl7ZkETF iJu2sM45KRFN33j0N3mi7mro5kDFfh2XezX81CTBAuJrm9spUPlrnpxXI68iepw2nK WQVs4mmIYqhNA== From: Chrispine Tinega To: andersson@kernel.org, mathieu.poirier@linaro.org Cc: linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org, francesco@valla.it, Chrispine Tinega Subject: [PATCH v2 0/2] remoteproc: k3: Recover a crashed remote core Date: Mon, 16 Nov 2026 21:41:43 +0300 Message-ID: <20261116184146.1897281-1-dev@chrispinetinega.com> X-Mailer: git-send-email 2.53.0 X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Envelope-From: dev@chrispinetinega.com 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