Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@nxp.com>
To: Peng Fan <peng.fan@nxp.com>
Cc: 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>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	Daniel Baluta <daniel.baluta@nxp.com>,
	linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
	imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/5] remoteproc: imx_rproc: Introduce prepare ops for imx_rproc_dcfg
Date: Fri, 31 Oct 2025 15:20:18 -0400	[thread overview]
Message-ID: <aQUL8v7nqiQaP5Sq@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20251031-imx95-rproc-2025-10-31-v2-3-758b2e547a55@nxp.com>

On Fri, Oct 31, 2025 at 10:24:54AM +0800, Peng Fan wrote:
> Allow each platform to provide its own prepare operations, preparing
> for i.MX95 LMM and CPU ops support.
>
> No functional changes.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---

Reviewed-by: Frank Li <Frank.Li@nxp.com>

>  drivers/remoteproc/imx_rproc.c | 5 ++++-
>  drivers/remoteproc/imx_rproc.h | 1 +
>  2 files changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/remoteproc/imx_rproc.c b/drivers/remoteproc/imx_rproc.c
> index 82cb8c7866ccb79061c46068d2039f38feebbb3c..232eb91e0b5dc2432131b1c140d6688b073fea1d 100644
> --- a/drivers/remoteproc/imx_rproc.c
> +++ b/drivers/remoteproc/imx_rproc.c
> @@ -532,7 +532,10 @@ static int imx_rproc_prepare(struct rproc *rproc)
>  		rproc_add_carveout(rproc, mem);
>  	}
>
> -	return  0;
> +	if (priv->ops && priv->ops->prepare)
> +		return priv->ops->prepare(rproc);
> +
> +	return 0;
>  }
>
>  static int imx_rproc_parse_fw(struct rproc *rproc, const struct firmware *fw)
> diff --git a/drivers/remoteproc/imx_rproc.h b/drivers/remoteproc/imx_rproc.h
> index aeed08bdfb5619c7afd7201589f417cfd6745818..e4b9ede656506142b260aa7515823f489a168ba4 100644
> --- a/drivers/remoteproc/imx_rproc.h
> +++ b/drivers/remoteproc/imx_rproc.h
> @@ -37,6 +37,7 @@ struct imx_rproc_plat_ops {
>  	int (*stop)(struct rproc *rproc);
>  	int (*detach)(struct rproc *rproc);
>  	int (*detect_mode)(struct rproc *rproc);
> +	int (*prepare)(struct rproc *rproc);
>  };
>
>  struct imx_rproc_dcfg {
>
> --
> 2.37.1
>


  reply	other threads:[~2025-10-31 19:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-31  2:24 [PATCH v2 0/5] remoteproc: imx_rproc: Support i.MX95 Peng Fan
2025-10-31  2:24 ` [PATCH v2 1/5] dt-bindings: remoteproc: fsl,imx-rproc: Add support for i.MX95 Peng Fan
2025-10-31  2:24 ` [PATCH v2 2/5] remoteproc: imx_rproc: Add runtime ops copy to support dynamic behavior Peng Fan
2025-11-04  9:43   ` Iuliana Prodan
2025-11-05  8:47     ` Peng Fan
2025-11-07  7:54   ` Daniel Baluta
2025-10-31  2:24 ` [PATCH v2 3/5] remoteproc: imx_rproc: Introduce prepare ops for imx_rproc_dcfg Peng Fan
2025-10-31 19:20   ` Frank Li [this message]
2025-11-07  7:56   ` Daniel Baluta
2025-10-31  2:24 ` [PATCH v2 4/5] remoteproc: imx_rproc: Add support for System Manager API Peng Fan
2025-10-31 19:28   ` Frank Li
2025-11-04  4:28     ` Peng Fan
2025-11-04  9:50   ` Iuliana Prodan
2025-11-05  8:51     ` Peng Fan
2025-11-07  9:10   ` Daniel Baluta
2025-11-07 13:49     ` Peng Fan
2025-10-31  2:24 ` [PATCH v2 5/5] remoteproc: imx_rproc: Add support for i.MX95 Peng Fan
2025-10-31 19:28   ` Frank Li
2025-11-07  9:13   ` 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=aQUL8v7nqiQaP5Sq@lizhi-Precision-Tower-5810 \
    --to=frank.li@nxp.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=daniel.baluta@nxp.com \
    --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=robh@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox