pw_chrono: Add clarification to is_nmi_safe
Change-Id: I3d5392bb0fd7038638643f778ae81385e05cb903
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/174573
Commit-Queue: Auto-Submit <auto-submit@pigweed-service-accounts.iam.gserviceaccount.com>
Pigweed-Auto-Submit: Armando Montanez <amontanez@google.com>
Reviewed-by: Ewout van Bekkum <ewout@google.com>
diff --git a/pw_chrono/public/pw_chrono/system_clock.h b/pw_chrono/public/pw_chrono/system_clock.h
index 72035fb..360241e 100644
--- a/pw_chrono/public/pw_chrono/system_clock.h
+++ b/pw_chrono/public/pw_chrono/system_clock.h
@@ -102,8 +102,9 @@
/// The now() function can be invoked at any time.
static constexpr bool is_always_enabled = true;
- /// The now() function may work in non-masking interrupts, depending on the
- /// backend. This must be provided by the backend.
+ /// The now() function may work in non-maskable interrupt contexts (e.g.
+ /// exception/fault handlers), depending on the backend. This must be provided
+ /// by the backend.
static constexpr bool is_nmi_safe = backend::kSystemClockNmiSafe;
/// This is thread and IRQ safe. This must be provided by the backend.
