Home
last modified time | relevance | path

Searched refs:MSG_RELEASE_BOUND (Results 1 – 3 of 3) sorted by relevance

/Zephyr-latest/doc/services/ipc/ipc_service/backends/
Dipc_service_icbmsg.rst190 #. The receiver sends ``MSG_RELEASE_DATA`` or ``MSG_RELEASE_BOUND`` control message over ICMsg cont…
271 MSG_RELEASE_BOUND subsubsection
280 * - MSG_RELEASE_BOUND
287 The ``MSG_RELEASE_BOUND`` control message is sent in response to ``MSG_BOUND``.
346 …ent using the ``MSG_BOUND`` control message and released with the ``MSG_RELEASE_BOUND`` control me…
353 Usually, it will be ``MSG_RELEASE_BOUND``, but ``MSG_DATA`` is also allowed.
360 It should not send the ``MSG_RELEASE_BOUND`` yet.
367 #. The follower sends the ``MSG_RELEASE_BOUND`` control message.
Dicbmsg_flows.svg191 MSG_RELEASE_BOUND,
310 MSG_RELEASE_BOUND,
/Zephyr-latest/subsys/ipc/ipc_service/backends/
Dipc_icbmsg.c130 MSG_RELEASE_BOUND, /* Release endpoint bound message. enumerator
680 r = send_release(dev_data, buffer, MSG_RELEASE_BOUND, ept_addr); in match_bound_msg()
972 case MSG_RELEASE_BOUND: in control_received()