From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Shengjiu Wang <shengjiu.wang@nxp.com>
Cc: andersson@kernel.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-remoteproc@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, iuliana.prodan@nxp.com,
daniel.baluta@nxp.com
Subject: Re: [PATCH 2/2] remoteproc: imx_dsp_rproc: Add support of coredump
Date: Mon, 30 Jun 2025 10:56:29 -0600 [thread overview]
Message-ID: <aGLBvXtSRlaKujqM@p14s> (raw)
In-Reply-To: <20250618062644.3895785-3-shengjiu.wang@nxp.com>
On Wed, Jun 18, 2025 at 02:26:44PM +0800, Shengjiu Wang wrote:
> Add call rproc_coredump_set_elf_info() to initialize the elf info for
> coredump, otherwise coredump will report an error "ELF class is not set".
>
> Remove the DSP IRAM and DRAM segment in coredump list, because after
> stop, DSP power is disabled, the IRAM and DRAM can't be accessed.
>
> Signed-off-by: Shengjiu Wang <shengjiu.wang@nxp.com>
> ---
> drivers/remoteproc/imx_dsp_rproc.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/remoteproc/imx_dsp_rproc.c b/drivers/remoteproc/imx_dsp_rproc.c
> index 9b9cddb224b0..9e7efb77b6e5 100644
> --- a/drivers/remoteproc/imx_dsp_rproc.c
> +++ b/drivers/remoteproc/imx_dsp_rproc.c
> @@ -738,9 +738,7 @@ static int imx_dsp_rproc_add_carveout(struct imx_dsp_rproc *priv)
> mem = rproc_mem_entry_init(dev, (void __force *)cpu_addr, (dma_addr_t)att->sa,
> att->size, da, NULL, NULL, "dsp_mem");
>
> - if (mem)
> - rproc_coredump_add_segment(rproc, da, att->size);
> - else
> + if (!mem)
Flag rproc->recovery_disabled is never set to true, meaning that since this
driver was introduced, some kind of recovery was available.
I worry that your work will introduce regression for other users. Daniel and
Iuliana, once again have to ask you to look at this patchset.
Thanks,
Mathieu
> return -ENOMEM;
>
> rproc_add_carveout(rproc, mem);
> @@ -1203,6 +1201,8 @@ static int imx_dsp_rproc_probe(struct platform_device *pdev)
> goto err_detach_domains;
> }
>
> + rproc_coredump_set_elf_info(rproc, ELFCLASS32, EM_XTENSA);
> +
> pm_runtime_enable(dev);
>
> return 0;
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-06-30 16:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 6:26 [PATCH 0/2] remoteproc: imx_dsp_rproc: Add coredump and recovery Shengjiu Wang
2025-06-18 6:26 ` [PATCH 1/2] remoteproc: imx_dsp_rproc: Add support of recovery process Shengjiu Wang
2025-06-23 15:04 ` Mathieu Poirier
2025-06-25 3:25 ` Shengjiu Wang
2025-06-25 14:39 ` Mathieu Poirier
2025-06-26 1:32 ` Shengjiu Wang
2025-06-30 16:49 ` Mathieu Poirier
2025-07-01 2:16 ` Shengjiu Wang
2025-07-01 14:27 ` Mathieu Poirier
2025-06-18 6:26 ` [PATCH 2/2] remoteproc: imx_dsp_rproc: Add support of coredump Shengjiu Wang
2025-06-30 16:56 ` Mathieu Poirier [this message]
2025-07-01 2:28 ` Shengjiu Wang
2025-07-01 15:27 ` Mathieu Poirier
2025-07-02 7:20 ` Shengjiu Wang
2025-07-02 11:48 ` Shengjiu Wang
2025-07-03 9:24 ` Shengjiu Wang
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=aGLBvXtSRlaKujqM@p14s \
--to=mathieu.poirier@linaro.org \
--cc=andersson@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=iuliana.prodan@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=shengjiu.wang@nxp.com \
/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;
as well as URLs for NNTP newsgroup(s).