aboutsummaryrefslogtreecommitdiff
path: root/book/en/src/internals/timer-queue.md
diff options
context:
space:
mode:
authorbors[bot] <26634292+bors[bot]@users.noreply.github.com>2023-05-23 06:26:28 +0000
committerGitHub <noreply@github.com>2023-05-23 06:26:28 +0000
commit62162241d4c7d82dfbb310113f7525d134cfde9b (patch)
tree4346cbe248835eba381003d8592248102028dac5 /book/en/src/internals/timer-queue.md
parent21b0d97e17922c023a3b5d8148a414d4277f7b87 (diff)
parent9fa073f7936782bddf5d02b7b1949032e84de1bd (diff)
Merge #741
741: Docs 2 r=korken89 a=datdenkikniet Working on the migration guide and other docs TODO: - [x] Migration guide - [x] Hardcoded examples should link to example code that is tested (this was already done, AFAICT) - [x] Address #699 - [x] Discuss: should we remove references to non-v2, apart from the migration guide and link to the book for v1? (Off-github conclusion: yes) - [x] RTIC {vs,and} Embassy (important: distinction between embassy runtime & HALs) - [x] More descriptive docs on how to implement & PR implementations of `Monotonic` to `rtic-monotonics` Co-authored-by: datdenkikniet <jcdra1@gmail.com>
Diffstat (limited to 'book/en/src/internals/timer-queue.md')
-rw-r--r--book/en/src/internals/timer-queue.md12
1 files changed, 6 insertions, 6 deletions
diff --git a/book/en/src/internals/timer-queue.md b/book/en/src/internals/timer-queue.md
index fcd345c..06056e2 100644
--- a/book/en/src/internals/timer-queue.md
+++ b/book/en/src/internals/timer-queue.md
@@ -10,7 +10,7 @@ appropriate ready queue.
Let's see how this in implemented in code. Consider the following program:
-``` rust
+``` rust,noplayground
#[rtic::app(device = ..)]
mod app {
// ..
@@ -31,7 +31,7 @@ mod app {
Let's first look at the `schedule` API.
-``` rust
+``` rust,noplayground
mod foo {
pub struct Schedule<'a> {
priority: &'a Cell<u8>,
@@ -122,7 +122,7 @@ is up.
Let's see the associated code.
-``` rust
+``` rust,noplayground
mod app {
#[no_mangle]
fn SysTick() {
@@ -220,7 +220,7 @@ analysis.
To illustrate, consider the following example:
-``` rust
+``` rust,noplayground
#[rtic::app(device = ..)]
mod app {
#[task(priority = 3, spawn = [baz])]
@@ -269,7 +269,7 @@ an `INSTANTS` buffers used to store the time at which a task was scheduled to
run; this `Instant` is read in the task dispatcher and passed to the user code
as part of the task context.
-``` rust
+``` rust,noplayground
mod app {
// ..
@@ -311,7 +311,7 @@ buffer. The value to be written is stored in the `Spawn` struct and its either
the `start` time of the hardware task or the `scheduled` time of the software
task.
-``` rust
+``` rust,noplayground
mod foo {
// ..