update new mode to post-sensor mode (#431)

* update new mode to post-sensor mode * that's embarrassing * update timing_manager.c * timing_manager.c update
Severson-Group · Jan 2, 2025 · 691f32e · 691f32e
1 parent 18321d8
commit 691f32e
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/sdk/app_cpu1/common/drv/timing_manager.c b/sdk/app_cpu1/common/drv/timing_manager.c
@@ -172,10 +172,10 @@ uint32_t timing_manager_get_trigger_count(void)
 /*
  * Specify the interrupt source of the scheduler ISR:
  *
- * Mode 0 uses the timing manager's 'trigger' signal, i.e. the control
+ * Mode 0: legacy mode - uses the timing manager's 'trigger' signal, i.e. the control
  * frequency is based on the PWM carrier frequency and the user-specified PWM sub-ratio.
  *
- * Mode 1 uses the timing manager's 'all_done' signal, calling the scheduler
+ * Mode 1: post-sensor mode - uses the timing manager's 'all_done' signal, calling the scheduler
  * when all the sensors are done with acquisition. When no sensors are enabled,
  * the scheduler is called as in mode 0 (based on the trigger). This mode
  * supports reporting of the timing for each sensor

diff --git a/sdk/app_cpu1/user/usr/user_config.h b/sdk/app_cpu1/user/usr/user_config.h
@@ -12,7 +12,7 @@
 // Specify the source of the scheduler ISR
 // Mode 0: legacy mode - scheduler is triggered based on the PWM carrier events and ratio
 //         of carrier frequency to desired control frequency
-// Mode 1: new mode - scheduler is triggered when all the enabled sensors are done
+// Mode 1: post-sensor mode - scheduler is triggered when all the enabled sensors are done
 //         acquiring their data
 #define USER_CONFIG_ISR_SOURCE (0)