summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoonwon Kang <joonwonkang@google.com>2026-04-21 13:46:51 +0300
committerJassi Brar <jassisinghbrar@gmail.com>2026-05-18 21:34:45 +0300
commitc96c8a7404ef8ce434ffd0f07b00e1a493fff42d (patch)
tree11d9320da9838411e54068c06fa207f3749aeb87
parentb57d1a40bc43258372fa1f4d39305e093947a262 (diff)
downloadlinux-c96c8a7404ef8ce434ffd0f07b00e1a493fff42d.tar.xz
mailbox: Clarify multi-thread is not supported in blocking mode
Unlike in non-blocking mode, multi-thread has not been supported in blocking mode. This commit is to prevent clients from having wrong assumption by explicitly specifying this fact to the API doc. Signed-off-by: Joonwon Kang <joonwonkang@google.com> Signed-off-by: Jassi Brar <jassisinghbrar@gmail.com>
-rw-r--r--drivers/mailbox/mailbox.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/drivers/mailbox/mailbox.c b/drivers/mailbox/mailbox.c
index bbc9fd75a95f..b00f7a32e866 100644
--- a/drivers/mailbox/mailbox.c
+++ b/drivers/mailbox/mailbox.c
@@ -258,6 +258,10 @@ EXPORT_SYMBOL_GPL(mbox_chan_tx_slots_available);
* over the chan, i.e, tx_done() is made.
* This function could be called from atomic context as it simply
* queues the data and returns a token against the request.
+ * In blocking mode, it is caller's responsibility to serialize threads'
+ * access to a channel if multi-threads are to send messages through the
+ * same channel, i.e. caller should not call this function until any
+ * previous call returns.
*
* Return: Non-negative integer for successful submission (non-blocking mode)
* or transmission over chan (blocking mode).