Lines Matching refs:S1
162 ascending priority ``S1``, ``MS2``, ``MS1``, and ``T1`` (the highest priority); two listeners,
163 ``L1`` and ``L2``; and channel A. Supposing ``L1``, ``L2``, ``MS1``, ``MS2``, and ``S1`` observer
182 ZBUS_OBSERVERS(L1, L2, MS1, MS2, S1), /* observers */
197 ZBus VDED execution detail for priority T1 > MS1 > MS2 > S1.
203 execution. The scenario considers the following priorities: T1 > MS1 > MS2 > S1. T1 has the highest
207 .. list-table:: VDED execution steps in detail for priority T1 > MS1 > MS2 > S1.
230 - The VDED pushes the notification message to the queue of S1. Notice the thread gets ready to
242 - MS2 finishes execution. The S1 leaves the pending state and starts executing.
245 - The S1 leaves the pending state since channel A is not locked. It gets in the CPU again and
250 - S1 finishes its workload.
254 channel A. The scenario considers the following priorities: T1 < MS1 < MS2 < S1.
260 ZBus VDED execution detail for priority T1 < MS1 < MS2 < S1.
264 .. list-table:: VDED execution steps in detail for priority T1 < MS1 < MS2 < S1.
291 - The VDED pushes the notification message to the queue of S1.
297 - The S1 leaves the pending state since channel A is not locked. It gets in the CPU again and
319 < MS2 < S1.
325 ZBus VDED execution detail with priority boost enabled and for priority T1 < MS1 < MS2 < S1.
365 * No other threads (that are not involved in the communication) with priority between T1 and S1 can
604 ``S1`` read attempts would definitely fail with K_NO_WAIT. For more details, check