aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNathan Vander Wilt <[email protected]>2025-05-27 11:38:11 -0700
committerGitHub <[email protected]>2025-05-27 11:38:11 -0700
commit035040e53cba24d7a15a055b605d50c568eb9e57 (patch)
tree3d180a3ae1880dd2d40c60a0d2c8e21805e4be82
parent645883d8748995beb8b07f5cee93ac960f6d6a9f (diff)
Update layer_by_layer.adoc to clarify PAC limitations
proposed fix for #4226, re. https://github.com/embassy-rs/embassy/issues/4226#issuecomment-2908772500
-rw-r--r--docs/pages/layer_by_layer.adoc2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/pages/layer_by_layer.adoc b/docs/pages/layer_by_layer.adoc
index 7dba11b5e..0692ee4fa 100644
--- a/docs/pages/layer_by_layer.adoc
+++ b/docs/pages/layer_by_layer.adoc
@@ -8,7 +8,7 @@ The application we'll write is a simple 'push button, blink led' application, wh
8 8
9== PAC version 9== PAC version
10 10
11The PAC is the lowest API for accessing peripherals and registers, if you don't count reading/writing directly to memory addresses. It provides distinct types to make accessing peripheral registers easier, but it does not prevent you from writing unsafe code. 11The PAC is the lowest API for accessing peripherals and registers, if you don't count reading/writing directly to memory addresses. It provides distinct types to make accessing peripheral registers easier, but it does little to prevent you from configuring or coordinating those registers incorrectly.
12 12
13Writing an application using the PAC directly is therefore not recommended, but if the functionality you want to use is not exposed in the upper layers, that's what you need to use. 13Writing an application using the PAC directly is therefore not recommended, but if the functionality you want to use is not exposed in the upper layers, that's what you need to use.
14 14