From: Tanmay Shah <tanmay.shah@amd.com>
To: <jassisinghbrar@gmail.com>, <andersson@kernel.org>,
<mathieu.poirier@linaro.org>
Cc: <linux-kernel@vger.kernel.org>,
<linux-remoteproc@vger.kernel.org>,
Tanmay Shah <tanmay.shah@amd.com>
Subject: [PATCH v4 2/3] remoteproc: xlnx: assign mbox client per mbox channel
Date: Tue, 3 Feb 2026 14:58:21 -0800 [thread overview]
Message-ID: <20260203225821.3293475-3-tanmay.shah@amd.com> (raw)
In-Reply-To: <20260203225821.3293475-1-tanmay.shah@amd.com>
Sharing mbox client data structure between "tx" and "rx" channels
can lead to data corruption. Instead each channel should have its own
mbox client data structure.
Signed-off-by: Tanmay Shah <tanmay.shah@amd.com>
---
changes in v4:
- separate remoteproc driver patch in to two patches
drivers/remoteproc/xlnx_r5_remoteproc.c | 19 ++++++++++++++-----
1 file changed, 14 insertions(+), 5 deletions(-)
diff --git a/drivers/remoteproc/xlnx_r5_remoteproc.c b/drivers/remoteproc/xlnx_r5_remoteproc.c
index bd619a6c42aa..109831c5815c 100644
--- a/drivers/remoteproc/xlnx_r5_remoteproc.c
+++ b/drivers/remoteproc/xlnx_r5_remoteproc.c
@@ -74,7 +74,8 @@ struct zynqmp_sram_bank {
* @tx_mc_buf: to copy data to mailbox tx channel
* @r5_core: this mailbox's corresponding r5_core pointer
* @mbox_work: schedule work after receiving data from mailbox
- * @mbox_cl: mailbox client
+ * @mbox_tx_cl: tx channel mailbox client
+ * @mbox_rx_cl: rx channel mailbox client
* @tx_chan: mailbox tx channel
* @rx_chan: mailbox rx channel
*/
@@ -83,7 +84,8 @@ struct mbox_info {
unsigned char tx_mc_buf[MBOX_CLIENT_BUF_MAX];
struct zynqmp_r5_core *r5_core;
struct work_struct mbox_work;
- struct mbox_client mbox_cl;
+ struct mbox_client mbox_tx_cl;
+ struct mbox_client mbox_rx_cl;
struct mbox_chan *tx_chan;
struct mbox_chan *rx_chan;
};
@@ -230,7 +232,7 @@ static void zynqmp_r5_mb_rx_cb(struct mbox_client *cl, void *msg)
struct mbox_info *ipi;
size_t len;
- ipi = container_of(cl, struct mbox_info, mbox_cl);
+ ipi = container_of(cl, struct mbox_info, mbox_rx_cl);
/* copy data from ipi buffer to r5_core */
ipi_msg = (struct zynqmp_ipi_message *)msg;
@@ -269,8 +271,8 @@ static struct mbox_info *zynqmp_r5_setup_mbox(struct device *cdev)
if (!ipi)
return NULL;
- mbox_cl = &ipi->mbox_cl;
- mbox_cl->rx_callback = zynqmp_r5_mb_rx_cb;
+ mbox_cl = &ipi->mbox_tx_cl;
+ mbox_cl->rx_callback = NULL;
mbox_cl->tx_block = false;
mbox_cl->knows_txdone = false;
mbox_cl->tx_done = NULL;
@@ -285,6 +287,13 @@ static struct mbox_info *zynqmp_r5_setup_mbox(struct device *cdev)
return NULL;
}
+ mbox_cl = &ipi->mbox_rx_cl;
+ mbox_cl->rx_callback = zynqmp_r5_mb_rx_cb;
+ mbox_cl->tx_block = false;
+ mbox_cl->knows_txdone = false;
+ mbox_cl->tx_done = NULL;
+ mbox_cl->dev = cdev;
+
ipi->rx_chan = mbox_request_channel_byname(mbox_cl, "rx");
if (IS_ERR(ipi->rx_chan)) {
mbox_free_channel(ipi->tx_chan);
--
2.34.1
next prev parent reply other threads:[~2026-02-03 22:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 22:58 [PATCH v4 0/3] mailbox queue length check Tanmay Shah
2026-02-03 22:58 ` [PATCH v4 1/3] mailbox: check mailbox queue is full or not Tanmay Shah
2026-02-03 22:58 ` Tanmay Shah [this message]
2026-02-09 23:27 ` [PATCH v4 2/3] remoteproc: xlnx: assign mbox client per mbox channel Jassi Brar
2026-02-10 17:12 ` Shah, Tanmay
2026-02-03 22:58 ` [PATCH v4 3/3] remoteproc: xlnx: do not send new mbox notification Tanmay Shah
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=20260203225821.3293475-3-tanmay.shah@amd.com \
--to=tanmay.shah@amd.com \
--cc=andersson@kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.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
all inboxes | Powered by JetHome®