From 28894b35e41a4ef2bdb831a9c98e28197f355a0e Mon Sep 17 00:00:00 2001 From: Rodrigo Peixoto Date: Fri, 20 Oct 2023 10:53:00 -0300 Subject: [PATCH] doc: zbus: fix VDED notification sequence figure The figure and table related to the VDED notification sequence were wrong. It fixes that by changing the image and adjusting the table content. Signed-off-by: Rodrigo Peixoto (cherry picked from commit 32bdb24a92b5c6bb65185bbe3e6d4b88e647cf17) --- .../zbus_publishing_process_example.svg | 107 +++++++++--------- doc/services/zbus/index.rst | 21 ++-- 2 files changed, 67 insertions(+), 61 deletions(-) diff --git a/doc/services/zbus/images/zbus_publishing_process_example.svg b/doc/services/zbus/images/zbus_publishing_process_example.svg index 72d7430a1637..84fbbdd6b1fa 100644 --- a/doc/services/zbus/images/zbus_publishing_process_example.svg +++ b/doc/services/zbus/images/zbus_publishing_process_example.svg @@ -1,70 +1,71 @@ + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - + + + + - + - - - - - - - - + + + + + + + + - - - - + + + + diff --git a/doc/services/zbus/index.rst b/doc/services/zbus/index.rst index 45e9e0ea69a8..ca8ab6142a8f 100644 --- a/doc/services/zbus/index.rst +++ b/doc/services/zbus/index.rst @@ -235,17 +235,22 @@ priority. it cannot access the channel since it is still locked. * - i - - VDED finishes the publishing by unlocking channel A. + - VDED finishes the publishing by unlocking channel A. The MS1 leaves the pending state and + starts executing. - * - j, k, l + * - j + - MS1 finishes execution. The MS2 leaves the pending state and starts executing. + + * - k + - MS2 finishes execution. The S1 leaves the pending state and starts executing. + + * - l, m, n - The S1 leaves the pending state since channel A is not locked. It gets in the CPU again and - starts executing. As it did receive a notification from channel A, it performs a channel read - (as simple as lock, memory copy, unlock), continues its execution, and goes out the CPU. - * - m - - S1 goes out of the MCU. + starts executing. As it did receive a notification from channel A, it performed a channel read + (as simple as lock, memory copy, unlock), continues its execution and goes out of the CPU. - * - n, o - - MS2 and MS1 execute and finish their workload. + * - o + - S1 finishes its workload. The figure below illustrates the actions performed during the VDED execution when T1 publishes to