From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-remoteproc@vger.kernel.org, linux-rt-devel@lists.linux.dev
Cc: Bjorn Andersson <andersson@kernel.org>,
Clark Williams <clrkwllms@kernel.org>,
Fabio Estevam <festevam@gmail.com>, Frank Li <Frank.Li@nxp.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Sascha Hauer <s.hauer@pengutronix.de>,
Steven Rostedt <rostedt@goodmis.org>, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH v4] remoteproc: imx_rproc: Invoke the callback directly
Date: Tue, 14 Jul 2026 10:31:30 +0200 [thread overview]
Message-ID: <20260714083130.ZsK0SgpX@linutronix.de> (raw)
In-Reply-To: <20260703-imx_mbox_rproc-v4-1-67b10560a861@linutronix.de>
On 2026-07-03 10:24:18 [+0200], To imx@lists.linux.dev wrote:
> The imx-mailbox driver moved the callback invocation into the threaded
> IRQ handler. This means the callback is invoked in preemptible context
> and there is no need to schedule the kworker for the
> imx_rproc_notified_idr_cb() invocation.
>
> This was tested with the rpmsg-tty driver on imx93.
>
> Remove the workqueue handling and invoke the imx_rproc_notified_idr_cb()
> callback directly.
>
> Reviewed-by: Peng Fan <peng.fan@nxp.com>
> Reviewed-by: Mathieu Poirier <mathieu.poirier@linaro.org>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
A friendly ping.
> ---
> v3…v4: https://lore.kernel.org/r/20260617-imx_mbox_rproc-v3-0-77948112defc@linutronix.de
> - The mailbox bits are part of v7.2-rc1. This is just a repost of the
> imx_rproc driver which is left.
>
> v2…v3: https://lore.kernel.org/r/20260603-imx_mbox_rproc-v2-0-a0059dc3b69a@linutronix.de
> - Forward the error in imx_mu_generic_tx() to the caller (new patch
> #1)
> - Extend the patch description a bit for for "Start splitting the IRQ
> handler" to briefly explain why callbacks are moved to the threaded
> handler.
> - Drop imx_mu_con_priv::pending. The primary handler wakes its
> threaded handler. Once the handler is woken, the pending flag must
> be set and there is no need to set/ clear it.
> - Avoid the double clk_disable_unprepare() if
> devm_mbox_controller_register() fails.
>
> v1…v2: https://lore.kernel.org/r/20260529-imx_mbox_rproc-v1-0-b8ffc36e11e5@linutronix.de
> - Using correct register to enable RXDB event.
> - Update commit description for the "threaded interrupt", "unmasks the
> interrupt" => "masks the interrupt event".
> - Add a shutdown field so that the interrupt does not unmask the
> interrupt if it has been already disabled because the channel is
> about to be shutdown. A possible race mentioned by sashiko.
> - Use devm_pm_runtime_enable(). This should avoid a possible race
> sashiko mentioned.
> - Use devm_of_platform_populate().
Sebastian
prev parent reply other threads:[~2026-07-14 8:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 8:24 [PATCH v4] remoteproc: imx_rproc: Invoke the callback directly Sebastian Andrzej Siewior
2026-07-14 8:31 ` Sebastian Andrzej Siewior [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=20260714083130.ZsK0SgpX@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=Frank.Li@nxp.com \
--cc=andersson@kernel.org \
--cc=clrkwllms@kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=mathieu.poirier@linaro.org \
--cc=peng.fan@nxp.com \
--cc=rostedt@goodmis.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