From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: andersson@kernel.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, arnaud.pouliquen@foss.st.com,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
linux-remoteproc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>,
iuliana.prodan@nxp.com, daniel.baluta@nxp.com
Subject: Re: [PATCH V2 6/6] remoteproc: imx_rproc: set address of .interrupts section as bootaddr
Date: Thu, 2 Feb 2023 15:05:57 -0700 [thread overview]
Message-ID: <20230202220557.GD1147631@p14s> (raw)
In-Reply-To: <20230127092246.1470865-7-peng.fan@oss.nxp.com>
On Fri, Jan 27, 2023 at 05:22:46PM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> i.MX93 M33 has ROM, it needs the ".interrupts" section address to start
> M33 firmware. In current design, the Arm Trusted Firmware(ATF) use TCML
> start address when the 2nd arg is 0 when SMC call. So When the M33 firmware
> is built with TCML address, it works well.
>
> However when M33 firmware is built to run in DDR, we need pass the
> ".interrupts" address as 2nd arg to ATF to start M33 firmwrae.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> drivers/remoteproc/imx_rproc.c | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/remoteproc/imx_rproc.c b/drivers/remoteproc/imx_rproc.c
> index f5ee0c9bb09d..59cca5ac3045 100644
> --- a/drivers/remoteproc/imx_rproc.c
> +++ b/drivers/remoteproc/imx_rproc.c
> @@ -374,7 +374,8 @@ static int imx_rproc_start(struct rproc *rproc)
> dcfg->src_start);
> break;
> case IMX_RPROC_SMC:
> - arm_smccc_smc(IMX_SIP_RPROC, IMX_SIP_RPROC_START, 0, 0, 0, 0, 0, 0, &res);
> + arm_smccc_smc(IMX_SIP_RPROC, IMX_SIP_RPROC_START, rproc->bootaddr,
> + 0, 0, 0, 0, 0, &res);
> ret = res.a0;
> break;
> case IMX_RPROC_SCU_API:
> @@ -664,6 +665,13 @@ static u64 imx_rproc_get_boot_addr(struct rproc *rproc, const struct firmware *f
> */
> writel(*(u32 *)(elf_data + offset), va);
> writel(*(u32 *)(elf_data + offset + 4), va + 4);
> + } else if (priv->dcfg->devtype == IMX_RPROC_IMX93) {
> + /* i.MX93 Cortex-M33 has ROM, it only needs the section address */
> + shdr = rproc_elf_find_shdr(rproc, fw, ".interrupts");
> + if (!shdr)
> + return bootaddr;
This contradicts what you wrote in the cover letter of the patchset about an
".interrupts" section always being present.
There is enough in this patchset to make me look for a second opinion. As such
I am CC'ing Iuliana and Daniel. Please respin this, adding both of them to the
recipient list. I will do another revision only when they have provided an RB
tag.
Thanks,
Mathieu
> +
> + return elf_shdr_get_sh_addr(class, shdr);
> }
>
> return bootaddr;
> --
> 2.37.1
>
WARNING: multiple messages have this Message-ID (diff)
From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: andersson@kernel.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, arnaud.pouliquen@foss.st.com,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
linux-remoteproc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>,
iuliana.prodan@nxp.com, daniel.baluta@nxp.com
Subject: Re: [PATCH V2 6/6] remoteproc: imx_rproc: set address of .interrupts section as bootaddr
Date: Thu, 2 Feb 2023 15:05:57 -0700 [thread overview]
Message-ID: <20230202220557.GD1147631@p14s> (raw)
In-Reply-To: <20230127092246.1470865-7-peng.fan@oss.nxp.com>
On Fri, Jan 27, 2023 at 05:22:46PM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> i.MX93 M33 has ROM, it needs the ".interrupts" section address to start
> M33 firmware. In current design, the Arm Trusted Firmware(ATF) use TCML
> start address when the 2nd arg is 0 when SMC call. So When the M33 firmware
> is built with TCML address, it works well.
>
> However when M33 firmware is built to run in DDR, we need pass the
> ".interrupts" address as 2nd arg to ATF to start M33 firmwrae.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> drivers/remoteproc/imx_rproc.c | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/remoteproc/imx_rproc.c b/drivers/remoteproc/imx_rproc.c
> index f5ee0c9bb09d..59cca5ac3045 100644
> --- a/drivers/remoteproc/imx_rproc.c
> +++ b/drivers/remoteproc/imx_rproc.c
> @@ -374,7 +374,8 @@ static int imx_rproc_start(struct rproc *rproc)
> dcfg->src_start);
> break;
> case IMX_RPROC_SMC:
> - arm_smccc_smc(IMX_SIP_RPROC, IMX_SIP_RPROC_START, 0, 0, 0, 0, 0, 0, &res);
> + arm_smccc_smc(IMX_SIP_RPROC, IMX_SIP_RPROC_START, rproc->bootaddr,
> + 0, 0, 0, 0, 0, &res);
> ret = res.a0;
> break;
> case IMX_RPROC_SCU_API:
> @@ -664,6 +665,13 @@ static u64 imx_rproc_get_boot_addr(struct rproc *rproc, const struct firmware *f
> */
> writel(*(u32 *)(elf_data + offset), va);
> writel(*(u32 *)(elf_data + offset + 4), va + 4);
> + } else if (priv->dcfg->devtype == IMX_RPROC_IMX93) {
> + /* i.MX93 Cortex-M33 has ROM, it only needs the section address */
> + shdr = rproc_elf_find_shdr(rproc, fw, ".interrupts");
> + if (!shdr)
> + return bootaddr;
This contradicts what you wrote in the cover letter of the patchset about an
".interrupts" section always being present.
There is enough in this patchset to make me look for a second opinion. As such
I am CC'ing Iuliana and Daniel. Please respin this, adding both of them to the
recipient list. I will do another revision only when they have provided an RB
tag.
Thanks,
Mathieu
> +
> + return elf_shdr_get_sh_addr(class, shdr);
> }
>
> return bootaddr;
> --
> 2.37.1
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-02-02 22:06 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 9:22 [PATCH V2 0/6] remoteproc: imx_rproc: support firmware in DDR Peng Fan (OSS)
2023-01-27 9:22 ` Peng Fan (OSS)
2023-01-27 9:22 ` [PATCH V2 1/6] remoteproc: elf_loader: introduce rproc_elf_find_shdr Peng Fan (OSS)
2023-01-27 9:22 ` Peng Fan (OSS)
2023-01-27 9:22 ` [PATCH V2 2/6] remoteproc: imx_rproc: add devtype Peng Fan (OSS)
2023-01-27 9:22 ` Peng Fan (OSS)
2023-02-02 21:40 ` Mathieu Poirier
2023-02-02 21:40 ` Mathieu Poirier
2023-01-27 9:22 ` [PATCH V2 3/6] remoteproc: imx_rproc: correct i.MX8MQ DDR Code alias mapping Peng Fan (OSS)
2023-01-27 9:22 ` Peng Fan (OSS)
2023-01-27 9:22 ` [PATCH V2 4/6] remoteproc: imx_rproc: force pointer type Peng Fan (OSS)
2023-01-27 9:22 ` Peng Fan (OSS)
2023-01-27 9:22 ` [PATCH V2 5/6] remoteproc: imx_rproc: set Cortex-M stack/pc to TCML Peng Fan (OSS)
2023-01-27 9:22 ` Peng Fan (OSS)
2023-02-02 21:56 ` Mathieu Poirier
2023-02-02 21:56 ` Mathieu Poirier
2023-02-03 0:04 ` Peng Fan
2023-02-03 0:04 ` Peng Fan
2023-02-13 18:04 ` Mathieu Poirier
2023-02-13 18:04 ` Mathieu Poirier
2023-02-03 12:47 ` Daniel Baluta
2023-02-03 12:47 ` Daniel Baluta
2023-02-03 12:50 ` Peng Fan
2023-02-03 12:50 ` Peng Fan
2023-01-27 9:22 ` [PATCH V2 6/6] remoteproc: imx_rproc: set address of .interrupts section as bootaddr Peng Fan (OSS)
2023-01-27 9:22 ` Peng Fan (OSS)
2023-02-02 22:05 ` Mathieu Poirier [this message]
2023-02-02 22:05 ` Mathieu Poirier
2023-02-03 0:12 ` Peng Fan
2023-02-03 0:12 ` Peng Fan
2023-02-03 12:49 ` [PATCH V2 0/6] remoteproc: imx_rproc: support firmware in DDR Daniel Baluta
2023-02-03 12:49 ` Daniel Baluta
2023-02-03 12:55 ` Peng Fan
2023-02-03 12:55 ` Peng Fan
2023-02-03 13:03 ` Daniel Baluta
2023-02-03 13:03 ` 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=20230202220557.GD1147631@p14s \
--to=mathieu.poirier@linaro.org \
--cc=andersson@kernel.org \
--cc=arnaud.pouliquen@foss.st.com \
--cc=daniel.baluta@nxp.com \
--cc=festevam@gmail.com \
--cc=iuliana.prodan@nxp.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=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.