From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Bjorn Andersson <andersson@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Andy Gross <agross@kernel.org>,
Patrice Chotard <patrice.chotard@foss.st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
linux-remoteproc@vger.kernel.org, kernel@pengutronix.de,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
linux-arm-kernel@lists.infradead.org,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-amlogic@lists.infradead.org,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
linux-mediatek@lists.infradead.org,
Konrad Dybcio <konrad.dybcio@linaro.org>,
linux-arm-msm@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH 00/18] remoteproc: Convert to platform remove callback returning void
Date: Tue, 9 May 2023 14:09:17 -0600 [thread overview]
Message-ID: <ZFqobZAfdlu+Rdtt@p14s> (raw)
In-Reply-To: <20230504194453.1150368-1-u.kleine-koenig@pengutronix.de>
On Thu, May 04, 2023 at 09:44:35PM +0200, Uwe Kleine-König wrote:
> Hello,
>
> this patch series adapts most platform drivers below drivers/remoteproc
> to use the .remove_new() callback. Compared to the traditional .remove()
> callback .remove_new() returns no value. This is a good thing because
> the driver core doesn't (and cannot) cope for errors during remove. The
> only effect of a non-zero return value in .remove() is that the driver
> core emits a warning. The device is removed anyhow and an early return
> from .remove() usually yields a resource leak. One driver suffering from
> this problem (s3c2410) is fixed by the first patch.
>
> By changing the remove callback to return void driver authors cannot
> reasonably (but wrongly) assume any more that there happens some kind of
> cleanup later.
>
> There is one driver (i.e. ti_k3_dsp_remoteproc.c) that might return an
> error code in .remove(). I didn't look in detail into this driver, but
> if that error happens, we have exactly the bad situation described
> above. (Note that kproc->mem and the register mapping goes away.)
>
> Best regards
> Uwe
>
> Uwe Kleine-König (18):
> remoteproc: da8xx: Convert to platform remove callback returning void
> remoteproc: imx_dsp: Convert to platform remove callback returning
> void
> remoteproc: imx: Convert to platform remove callback returning void
> remoteproc: keystone: Convert to platform remove callback returning
> void
> remoteproc: meson_mx_ao_arc: Convert to platform remove callback
> returning void
> remoteproc: mtk_scp: Convert to platform remove callback returning
> void
> remoteproc: omap: Convert to platform remove callback returning void
> remoteproc: pru: Convert to platform remove callback returning void
> remoteproc: qcom_q6v5_adsp: Convert to platform remove callback
> returning void
> remoteproc: qcom_q6v5_mss: Convert to platform remove callback
> returning void
> remoteproc: qcom_q6v5_pas: Convert to platform remove callback
> returning void
> remoteproc: qcom_q6v5_wcss: Convert to platform remove callback
> returning void
> remoteproc: qcom_wcnss: Convert to platform remove callback returning
> void
> remoteproc: rcar: Convert to platform remove callback returning void
> remoteproc: virtio: Convert to platform remove callback returning void
> remoteproc: st: Convert to platform remove callback returning void
> remoteproc: stm32: Convert to platform remove callback returning void
> remoteproc: wkup_m3: Convert to platform remove callback returning
> void
>
> drivers/remoteproc/da8xx_remoteproc.c | 6 ++----
> drivers/remoteproc/imx_dsp_rproc.c | 6 ++----
> drivers/remoteproc/imx_rproc.c | 6 ++----
> drivers/remoteproc/keystone_remoteproc.c | 6 ++----
> drivers/remoteproc/meson_mx_ao_arc.c | 6 ++----
> drivers/remoteproc/mtk_scp.c | 6 ++----
> drivers/remoteproc/omap_remoteproc.c | 6 ++----
> drivers/remoteproc/pru_rproc.c | 6 ++----
> drivers/remoteproc/qcom_q6v5_adsp.c | 6 ++----
> drivers/remoteproc/qcom_q6v5_mss.c | 6 ++----
> drivers/remoteproc/qcom_q6v5_pas.c | 6 ++----
> drivers/remoteproc/qcom_q6v5_wcss.c | 6 ++----
> drivers/remoteproc/qcom_wcnss.c | 6 ++----
> drivers/remoteproc/rcar_rproc.c | 6 ++----
> drivers/remoteproc/remoteproc_virtio.c | 6 ++----
> drivers/remoteproc/st_remoteproc.c | 6 ++----
> drivers/remoteproc/stm32_rproc.c | 6 ++----
> drivers/remoteproc/wkup_m3_rproc.c | 6 ++----
> 18 files changed, 36 insertions(+), 72 deletions(-)
>
I have applied this set.
Thanks,
Mathieu
>
> base-commit: 1a5304fecee523060f26e2778d9d8e33c0562df3
> --
> 2.39.2
>
prev parent reply other threads:[~2023-05-09 20:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 19:44 [PATCH 00/18] remoteproc: Convert to platform remove callback returning void Uwe Kleine-König
2023-05-04 19:44 ` [PATCH 06/18] remoteproc: mtk_scp: " Uwe Kleine-König
2023-05-05 8:58 ` AngeloGioacchino Del Regno
2023-05-05 17:13 ` Matthias Brugger
2023-05-09 20:09 ` Mathieu Poirier [this message]
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=ZFqobZAfdlu+Rdtt@p14s \
--to=mathieu.poirier@linaro.org \
--cc=agross@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andersson@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=festevam@gmail.com \
--cc=jbrunet@baylibre.com \
--cc=kernel@pengutronix.de \
--cc=khilman@baylibre.com \
--cc=konrad.dybcio@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=martin.blumenstingl@googlemail.com \
--cc=matthias.bgg@gmail.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=neil.armstrong@linaro.org \
--cc=patrice.chotard@foss.st.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=u.kleine-koenig@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