From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Peng Fan <peng.fan@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
linux-remoteproc@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [bug report] remoteproc: imx_rproc: Introduce prepare ops for imx_rproc_dcfg
Date: Fri, 6 Feb 2026 09:29:53 -0700 [thread overview]
Message-ID: <aYYXAa2Fj36XG4yQ@p14s> (raw)
In-Reply-To: <aYXveV_Y1gT73JoK@stanley.mountain>
On Fri, Feb 06, 2026 at 04:41:13PM +0300, Dan Carpenter wrote:
> [ Smatch checking is paused while we raise funding. #SadFace
> https://lore.kernel.org/all/aTaiGSbWZ9DJaGo7@stanley.mountain/ -dan ]
>
> Hello Peng Fan,
>
> Commit edd2a9956055 ("remoteproc: imx_rproc: Introduce prepare ops
> for imx_rproc_dcfg") from Jan 9, 2026 (linux-next), leads to the
> following Smatch static checker warning:
>
> drivers/remoteproc/imx_rproc.c:648 imx_rproc_prepare()
> warn: ignoring unreachable code.
>
> drivers/remoteproc/imx_rproc.c
> 605 static int imx_rproc_prepare(struct rproc *rproc)
> 606 {
> 607 struct imx_rproc *priv = rproc->priv;
> 608 struct device_node *np = priv->dev->of_node;
> 609 struct rproc_mem_entry *mem;
> 610 int i = 0;
> 611 u32 da;
> 612
> 613 /* Register associated reserved memory regions */
> 614 while (1) {
> 615 int err;
> 616 struct resource res;
> 617
> 618 err = of_reserved_mem_region_to_resource(np, i++, &res);
> 619 if (err)
> 620 return 0;
> 621
> 622 /*
> 623 * Ignore the first memory region which will be used vdev buffer.
> 624 * No need to do extra handlings, rproc_add_virtio_dev will handle it.
> 625 */
> 626 if (strstarts(res.name, "vdev0buffer"))
> 627 continue;
> 628
> 629 if (strstarts(res.name, "rsc-table"))
> 630 continue;
> 631
> 632 /* No need to translate pa to da, i.MX use same map */
> 633 da = res.start;
> 634
> 635 /* Register memory region */
> 636 mem = rproc_mem_entry_init(priv->dev, NULL, (dma_addr_t)res.start,
> 637 resource_size(&res), da,
> 638 imx_rproc_mem_alloc, imx_rproc_mem_release,
> 639 "%.*s", strchrnul(res.name, '@') - res.name,
> 640 res.name);
> 641 if (!mem)
> 642 return -ENOMEM;
> 643
> 644 rproc_coredump_add_segment(rproc, da, resource_size(&res));
> 645 rproc_add_carveout(rproc, mem);
> 646 }
> 647
> --> 648 if (priv->ops && priv->ops->prepare)
> 649 return priv->ops->prepare(rproc);
>
> This is unreachable code.
It looks like Dan (and Smatch) has a point.
>
> 650
> 651 return 0;
> 652 }
>
> regards,
> dan carpenter
>
next prev parent reply other threads:[~2026-02-06 16:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <caa37f28-a2e8-4e0a-a9ce-a365ce805e4b@stanley.mountain>
2026-02-06 13:40 ` [bug report] phy: apple: Add Apple Type-C PHY Dan Carpenter
2026-02-06 21:47 ` Janne Grunau
2026-02-06 21:48 ` Sven Peter
2026-02-06 13:40 ` [bug report] spi: stm32: properly fail on dma_request_chan error Dan Carpenter
2026-02-06 13:41 ` [bug report] remoteproc: imx_rproc: Introduce prepare ops for imx_rproc_dcfg Dan Carpenter
2026-02-06 16:29 ` Mathieu Poirier [this message]
2026-02-08 11:45 ` Peng Fan
2026-02-06 13:41 ` [bug report] soc: rockchip: grf: Support multiple grf to be handled Dan Carpenter
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=aYYXAa2Fj36XG4yQ@p14s \
--to=mathieu.poirier@linaro.org \
--cc=dan.carpenter@linaro.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=linux-remoteproc@vger.kernel.org \
--cc=peng.fan@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