From 270504d87da42ff8bbad2afb1b905dd14df3dc4c Mon Sep 17 00:00:00 2001 From: Tshepang Mbambo <tshepang@gmail.com> Date: Fri, 1 Dec 2023 08:45:20 +0200 Subject: [PATCH] runtime.adoc: typo --- docs/modules/ROOT/pages/runtime.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/modules/ROOT/pages/runtime.adoc b/docs/modules/ROOT/pages/runtime.adoc index 8f4921f67..f2812dd7c 100644 --- a/docs/modules/ROOT/pages/runtime.adoc +++ b/docs/modules/ROOT/pages/runtime.adoc @@ -27,7 +27,7 @@ If you use the `#[embassy_executor::main]` macro in your application, it creates Interrupts are a common way for peripherals to signal completion of some operation and fits well with the async execution model. The following diagram describes a typical application flow where (1) a task is polled and is attempting to make progress. The task then (2) instructs the peripheral to perform some operation, and awaits. After some time has passed, (3) an interrupt is raised, marking the completion of the operation. -The peripheral HAL then (4) ensures that interrupt signals are routed to to the peripheral and updating the peripheral state with the results of the operation. The executor is then (5) notified that the task should be polled, which it will do. +The peripheral HAL then (4) ensures that interrupt signals are routed to the peripheral and updating the peripheral state with the results of the operation. The executor is then (5) notified that the task should be polled, which it will do. image::embassy_irq.png[Interrupt handling]