mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Baluta <daniel.baluta@oss.nxp.com>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Frank Li <Frank.Li@nxp.com>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>
Cc: linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
	imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH 0/4] Add i.MX94 remoteproc support and reset vector handling improvements
Date: Fri, 20 Mar 2026 11:19:06 +0200	[thread overview]
Message-ID: <b5e05fe6-97c4-40cd-b7cc-b417d8717aec@oss.nxp.com> (raw)
In-Reply-To: <20260312-imx943-rproc-v1-0-3e66596592a8@nxp.com>

On 3/12/26 14:36, Peng Fan (OSS) wrote:
> This series adds remoteproc support for the i.MX94 family, including the
> CM70, CM71, and CM33S cores, and introduces a new device‑tree property to
> correctly derive the hardware reset vector for Cortex‑M processors whose
> ELF entry point does not directly correspond to the actual reset address.
>
> Background:
> Cortex‑M processors fetch their initial SP and PC from a fixed reset vector
> table. While ELF images embed the entry point (e_entry), this value is
> not always aligned to the hardware reset address. On platforms such as
> i.MX94 CM33S, masking is required to compute the correct reset vector
> address before programming the SoC reset registers.

What happens if the reset vector is at 0 and the e_entry point is at 0x800...?

In this case masking will no longer work! Can we implement a generic approach?


>
> Similarly, on i.MX95, the existing implementation always programs a reset
> vector of 0x0, which only works when executing entirely from TCM. When
> firmware is loaded into DDR, the driver must pass the correct reset vector
> to the SM CPU/LMM interfaces.
>
> This series addresses these issues and provides the necessary DT bindings
> and driver support.
>
> Summary of patches:
> [1]dt-bindings: remoteproc: imx-rproc: Introduce fsl,reset-vector-mask
> Adds a new DT property allowing SoCs to specify a mask for deriving the
> hardware reset vector from the ELF entry point.
>
> [2]dt-bindings: remoteproc: imx-rproc: Support i.MX9[4,52]
> Adds compatible strings for i.MX94 CM70, CM71, and CM33S processors.
>
> [3]remoteproc: imx_rproc: Pass bootaddr to SM CPU/LMM reset vector
> Ensures the correct reset vector is passed to SM APIs by introducing a
> driver‑level helper (imx_rproc_get_boot_addr()) that applies the
> reset‑vector mask.
>
> [4]remoteproc: imx_rproc: Add support for i.MX94 remoteproc
> Adds address translation tables and configuration data for CM70, CM71,
> and CM33S, enabling full remoteproc operation on i.MX94.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> Peng Fan (4):
>       dt-bindings: remoteproc: imx-rproc: Introduce fsl,reset-vector-mask
>       dt-bindings: remoteproc: imx-rproc: Support i.MX94
>       remoteproc: imx_rproc: Pass bootaddr to SM CPU/LMM reset vector
>       remoteproc: imx_rproc: Add support for i.MX94
>
>  .../bindings/remoteproc/fsl,imx-rproc.yaml         |  9 +++
>  drivers/remoteproc/imx_rproc.c                     | 85 +++++++++++++++++++++-
>  2 files changed, 91 insertions(+), 3 deletions(-)
> ---
> base-commit: 7109a2155340cc7b21f27e832ece6df03592f2e8
> change-id: 20260311-imx943-rproc-2050e00b65f7
>
> Best regards,



  parent reply	other threads:[~2026-03-20  9:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-12 12:36 Peng Fan (OSS)
2026-03-12 12:36 ` [PATCH 1/4] dt-bindings: remoteproc: imx-rproc: Introduce fsl,reset-vector-mask Peng Fan (OSS)
2026-03-20  9:46   ` Daniel Baluta
2026-03-20 13:02     ` Peng Fan
2026-03-23 15:15       ` Daniel Baluta
2026-03-23 19:15   ` Rob Herring
2026-03-23 20:20     ` Daniel Baluta
2026-03-12 12:36 ` [PATCH 2/4] dt-bindings: remoteproc: imx-rproc: Support i.MX94 Peng Fan (OSS)
2026-03-12 14:48   ` Frank Li
2026-03-23 15:16   ` Daniel Baluta
2026-03-23 19:16   ` Rob Herring (Arm)
2026-03-12 12:36 ` [PATCH 3/4] remoteproc: imx_rproc: Pass bootaddr to SM CPU/LMM reset vector Peng Fan (OSS)
2026-03-12 12:36 ` [PATCH 4/4] remoteproc: imx_rproc: Add support for i.MX94 Peng Fan (OSS)
2026-03-12 19:24   ` Frank Li
2026-03-23 15:24   ` Daniel Baluta
2026-03-20  9:19 ` Daniel Baluta [this message]
2026-03-23 14:32   ` [PATCH 0/4] Add i.MX94 remoteproc support and reset vector handling improvements Mathieu Poirier
2026-03-25  8:41     ` Daniel Baluta
2026-03-26 12:20       ` Peng Fan

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=b5e05fe6-97c4-40cd-b7cc-b417d8717aec@oss.nxp.com \
    --to=daniel.baluta@oss.nxp.com \
    --cc=Frank.Li@nxp.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=peng.fan@nxp.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    /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®