public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Daniel Baluta <daniel.baluta@oss.nxp.com>
To: Jiafei Pan <Jiafei.Pan@nxp.com>,
	andersson@kernel.org, mathieu.poirier@linaro.org,
	peng.fan@nxp.com, Frank.Li@nxp.com, s.hauer@pengutronix.de,
	kernel@pengutronix.de, festevam@gmail.com, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Cc: Zhiqiang.Hou@nxp.com, mingkai.hu@nxp.com
Subject: Re: [PATCH 5/5] remoteproc: imx: use device node name as processor name
Date: Tue, 28 Apr 2026 16:36:34 +0300	[thread overview]
Message-ID: <685ed732-fe54-4d2b-b2e9-6bfd10d67b82@oss.nxp.com> (raw)
In-Reply-To: <20260428090819.17761-6-Jiafei.Pan@nxp.com>

On 4/28/26 12:08, Jiafei Pan wrote:
> [You don't often get email from jiafei.pan@nxp.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
> 
> As currently there are maybe multiple remote processors, so change from
> using fixed name to using device node name as remote processor name in
> order to make them can be distinguished by through of name in sys
> filesystem.
> 
> Signed-off-by: Jiafei Pan <Jiafei.Pan@nxp.com>
> ---
>  drivers/remoteproc/imx_rproc.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/remoteproc/imx_rproc.c b/drivers/remoteproc/imx_rproc.c
> index e8d239bef5c9..17026e390e88 100644
> --- a/drivers/remoteproc/imx_rproc.c
> +++ b/drivers/remoteproc/imx_rproc.c
> @@ -1357,7 +1357,7 @@ static int imx_rproc_probe(struct platform_device *pdev)
>         int ret;
> 
>         /* set some other name then imx */

I think you can also remove the comment above.

> -       rproc = devm_rproc_alloc(dev, "imx-rproc", &imx_rproc_ops,
> +       rproc = devm_rproc_alloc(dev, np->name, &imx_rproc_ops,
>                                  NULL, sizeof(*priv));
>         if (!rproc)
>                 return -ENOMEM;
> --
> 2.43.0
> 
> 



  reply	other threads:[~2026-04-28 13:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-28  9:08 [PATCH 0/5] remoteproc: add Cortex-A Core remoteproc support on i.MX platforms Jiafei Pan
2026-04-28  9:08 ` [PATCH 1/5] dt-bindings: remoteproc: add imx-rproc-psci binding Jiafei Pan
2026-04-29  7:05   ` Krzysztof Kozlowski
2026-04-28  9:08 ` [PATCH 2/5] drivers: remoteproc: imx: add support for Cortex-A Core Jiafei Pan
2026-04-29  7:05   ` Krzysztof Kozlowski
2026-04-30  6:47     ` [EXT] " Jiafei Pan
2026-04-28  9:08 ` [PATCH 3/5] drivers: remoteproc: imx: add autoboot support for A-core remoteproc Jiafei Pan
2026-04-28 13:49   ` Daniel Baluta
2026-04-30  6:22     ` Jiafei Pan
2026-04-28  9:08 ` [PATCH 4/5] arm64: dts: imx93: Cortex-A Core remoteproc device node Jiafei Pan
2026-04-29  7:07   ` Krzysztof Kozlowski
2026-04-30  6:51     ` [EXT] " Jiafei Pan
2026-04-30  8:45       ` Daniel Baluta
2026-04-28  9:08 ` [PATCH 5/5] remoteproc: imx: use device node name as processor name Jiafei Pan
2026-04-28 13:36   ` Daniel Baluta [this message]
2026-04-30  6:21     ` Jiafei Pan

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=685ed732-fe54-4d2b-b2e9-6bfd10d67b82@oss.nxp.com \
    --to=daniel.baluta@oss.nxp.com \
    --cc=Frank.Li@nxp.com \
    --cc=Jiafei.Pan@nxp.com \
    --cc=Zhiqiang.Hou@nxp.com \
    --cc=andersson@kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=mingkai.hu@nxp.com \
    --cc=peng.fan@nxp.com \
    --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