Home
last modified time | relevance | path

Searched refs:subscribers (Results 1 – 15 of 15) sorted by relevance

/Zephyr-latest/samples/subsys/llext/edk/app/src/
Dpubsub.c36 } subscribers[MAX_SUBSCRIBERS]; member
52 if (sus->subscribers[i].thread == thread) { in remove_subscriber()
53 sus->subscribers[i].thread = NULL; in remove_subscriber()
54 sus->subscribers[i].evt = NULL; in remove_subscriber()
64 memmove(&sus->subscribers[i], &sus->subscribers[i + 1], in remove_subscriber()
66 sizeof(sus->subscribers[0])); in remove_subscriber()
79 sus->subscribers[sus->subscribers_count].thread = thread; in add_subscriber()
80 sus->subscribers[sus->subscribers_count].evt = evt; in add_subscriber()
93 k_event_post(subs->subscribers[i].evt, channel); in notify_subscribers()
/Zephyr-latest/samples/subsys/zbus/benchmark/
DKconfig19 bool "Asynchronous using subscribers"
22 bool "Asynchronous using message subscribers"
30 Forces a message copy on the listeners and subscribers to behave equivalent to
31 message subscribers.
DREADME.rst25 * **CONFIG_BM_SUBSCRIBERS** Use y to perform the benchmark subscribers;
26 * **CONFIG_BM_MSG_SUBSCRIBERS** Use y to perform the benchmark message subscribers.
/Zephyr-latest/samples/subsys/zbus/confirmed_channel/
DREADME.rst5 Use confirmed zbus channels to ensure all subscribers consume a message.
10 The confirmed channel can only be published when all the subscribers consume the message.
/Zephyr-latest/subsys/zbus/
DKconfig30 bool "Message subscribers will receive all messages in sequence."
/Zephyr-latest/doc/services/input/
Dindex.rst32 used to indicate which device reported the event and can be used by subscribers
35 subscribers with no device filter will receive the event.
/Zephyr-latest/doc/services/zbus/
Dindex.rst49 * Threads (subscribers and message subscribers) and callbacks (listeners) publishing, reading, and
76 * Message subscribers, a thread-based observer that relies internally on a FIFO where the event
154 subscribers, and pushes the channel's reference to the subscribers' notification message queue in
367 * Message subscribers will wait for the VDED to finish the message delivery process. So the VDED
389 ZBus always delivers the messages to the listeners and message subscribers. However, there are no
390 message delivery guarantees for subscribers because zbus only sends the notification, but the
402 subscribers. Thus, choose carefully the configurations
405 (delivery guarantee) considering message subscribers. If you want to keep an isolated pool for a
853 * :zephyr:code-sample:`zbus-msg-subscriber` illustrates how to use message subscribers;
865 with subscribers;
[all …]
/Zephyr-latest/samples/subsys/zbus/priority_boost/
DREADME.rst12 developer's application. Those who want to avoid priority inversions between message subscribers and
13 plain subscribers should use the priority boost strategy.
/Zephyr-latest/samples/subsys/zbus/msg_subscriber/
DREADME.rst5 Use zbus message subscribers to listen to messages published to channels.
/Zephyr-latest/samples/subsys/llext/edk/
DREADME.rst18 subscribers. There are four extensions, which are loaded by the application and
/Zephyr-latest/doc/releases/
Drelease-notes-3.5.rst2329 channel using subscribers.
2331 * Created the zbus message subscriber sample to demonstrate how to use message subscribers.
Drelease-notes-3.6.rst1204 * Refactored the benchmark sample, adding message subscribers. (:github:`64524`)
Drelease-notes-3.7.rst1881 * Added a way of isolating a channel message subscribers pool. Some channels can now share an
Drelease-notes-3.2.rst1485 * Allow multiple subscribers to latency changes in the policy manager.
Drelease-notes-3.3.rst2492 * Observers can be listeners (synchronous) and subscribers (asynchronous).