From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
To: bjorn.andersson@linaro.org, mathieu.poirier@linaro.org,
shawnguo@kernel.org, s.hauer@pengutronix.de,
shengjiu.wang@nxp.com
Cc: linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
linux-arm-kernel@lists.infradead.org, Peng Fan <peng.fan@nxp.com>
Subject: [PATCH 0/2] remoteproc: elf: ignore PT_LOAD type segment with memsz as 0
Date: Wed, 23 Mar 2022 14:49:42 +0800 [thread overview]
Message-ID: <20220323064944.1351923-1-peng.fan@oss.nxp.com> (raw)
From: Peng Fan <peng.fan@nxp.com>
i.MX DSP firmware has segments with PT_LOAD and memsz/filesz as zero.
It is valid case the memsz set to zero according to elf spec:
https://refspecs.linuxbase.org/elf/elf.pdf page 40
So we could let remoteproc elf loader handle this case, then no
duplicate code in imx dsp rproc driver
Tested i.MX8MP DSP and M7 remoteproc
Peng Fan (2):
remoteproc: elf_loader: skip segment with memsz as zero
remoteproc: imx_dsp_rproc: use common rproc_elf_load_segments
drivers/remoteproc/imx_dsp_rproc.c | 95 +---------------------
drivers/remoteproc/remoteproc_elf_loader.c | 9 +-
2 files changed, 9 insertions(+), 95 deletions(-)
--
2.25.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-03-23 6:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 6:49 Peng Fan (OSS) [this message]
2022-03-23 6:49 ` [PATCH 1/2] remoteproc: elf_loader: skip segment with memsz as zero Peng Fan (OSS)
2022-04-12 17:47 ` Mathieu Poirier
2022-03-23 6:49 ` [PATCH 2/2] remoteproc: imx_dsp_rproc: use common rproc_elf_load_segments Peng Fan (OSS)
2022-04-06 10:05 ` Daniel Baluta
2022-04-06 10:58 ` Peng Fan
2022-04-06 11:25 ` Daniel Baluta
2022-04-07 8:05 ` Daniel Baluta
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=20220323064944.1351923-1-peng.fan@oss.nxp.com \
--to=peng.fan@oss.nxp.com \
--cc=bjorn.andersson@linaro.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=peng.fan@nxp.com \
--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).