Lines Matching refs:observer

28 published channel's observers. Based on the observer's type, it can access the message directly,
72 * Subscriber, a thread-based observer that relies internally on a message queue where the event
74   notified. Note this kind of observer does not receive the message itself. It should read the
76 * Message subscribers, a thread-based observer that relies internally on a FIFO where the event
80 every observation, a pair channel/observer. Developers can statically allocate observation using the
82 enabling developers to create runtime observations. It is possible to disable an observer entirely
93 allocated (runtime observation). (a) shows that the observer and all observations are enabled. (b)
94 shows the observer is disabled, so the event dispatcher will ignore it. (c) shows the observer
163 ``L1`` and ``L2``; and channel A. Supposing ``L1``, ``L2``, ``MS1``, ``MS2``, and ``S1`` observer
306 Priority (HOP); even if the observer is not waiting for a message on the channel, it is considered
327 To properly use the priority boost, attaching the observer to a thread is necessary. When the
329 consider the observer's priority. The following code illustrates the thread-attaching function.
355 On the above code, the :c:func:`zbus_obs_attach_to_thread` will set the ``s1`` observer with
357 observer using the :c:func:`zbus_obs_detach_from_thread`. Only enabled observers and observations
439 observer can be a subscriber (asynchronous), a message subscriber (asynchronous), or a listener
516 that a post-definition static observer. The command enables us to indicate an initialization
630 channel or observer on the same call. The following code builds on the examples above and displays
820 Runtime observer registration
837             /* Adding the observer to channel chan1 */
839             /* Removing the observer from channel chan1 */
863   observer registration feature;
872 synchronously or asynchronously. Choosing the proper observer type is crucial. Use subscribers for
897 * :kconfig:option:`CONFIG_ZBUS_MSG_SUBSCRIBER` enables the message subscriber observer type;
908 * :kconfig:option:`CONFIG_ZBUS_RUNTIME_OBSERVERS` enables the runtime observer registration.