summaryrefslogtreecommitdiff
path: root/docs/core_runtime.md
diff options
context:
space:
mode:
authorMary Ruthven <mruthven@chromium.org>2021-01-11 11:27:12 -0800
committerCommit Bot <commit-bot@chromium.org>2021-01-11 21:55:20 +0000
commitec643f0d99397eafa09ab39b2d7dd6b968bd70d8 (patch)
tree76109b01c5760134d13384678b5ce126e29fba8c /docs/core_runtime.md
parent17baff2bd51e5b14fa9992f4cddca96742a7dea8 (diff)
downloadchrome-ec-ec643f0d99397eafa09ab39b2d7dd6b968bd70d8.tar.gz
coil: cleanup commentsstabilize-rust-13720.B-cr50_stab
BUG=b:175244613 TEST=make buildall -j Change-Id: Icbd143b072fdd5df3b67d7e5a09ee6c01a77f6b9 Signed-off-by: Mary Ruthven <mruthven@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2622889 Reviewed-by: Namyoon Woo <namyoon@chromium.org>
Diffstat (limited to 'docs/core_runtime.md')
-rw-r--r--docs/core_runtime.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/core_runtime.md b/docs/core_runtime.md
index 9d81b807be..680e5e4928 100644
--- a/docs/core_runtime.md
+++ b/docs/core_runtime.md
@@ -52,7 +52,7 @@ where you need to avoid it.
The hardware interrupt requests are connected to the interruption handling
*C* routines declared by the `DECLARE_IRQ` macros, through some chip/core
specific mechanisms (e.g. depending whether we have a vectored interrupt
-controller, slave interrupt controllers...)
+controller, peripheral interrupt controllers...)
The interrupts can be nested (ie interrupted by a higher priority interrupt).
All the interrupt vectors are assigned a priority as defined in their