archives/pebble
2
0
Fork 0
mirror of https://github.com/google/pebble.git synced 2025-04-30 15:21:41 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

spelling: separate

Browse source 
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
This commit is contained in:
Josh Soref 2025-01-28 15:40:53 -05:00
parent 394c11d071
commit 586db5b942
4 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
src/fw/apps/prf_apps/recovery_first_use_app/getting_started_button_combo.h
View file

@ -32,7 +32,7 @@
//! The reason it's not just a boring set of long click handlers is because we don't support
//! registering a long click handler for a combination of buttons like up+down.
//!
//! I tried to split this out from a seperate file from the recovery_first_use.c file so I could
//! I tried to split this out from a separate file from the recovery_first_use.c file so I could
//! test this behaviour in a unit test independent in the UI. I think it turned out /okay/. The
//! callback specification is a little odd (only for select but not for the other ones, should we
//! be blowing memory on static behaviour like this?) but it was worth a shot.

4
src/fw/console/dbgserial_input.c
View file

@ -36,7 +36,7 @@ static void dbgserial_interrupt_handler(bool *should_context_switch);
static DbgSerialCharacterCallback s_character_callback;
static TimerID s_stop_mode_timeout_timer;
//! Use a seperate variable so it's safe to check from the ISR.
//! Use a separate variable so it's safe to check from the ISR.
static bool s_stop_mode_inhibited = false;
//! We DMA into this buffer as a circular buffer
@ -64,7 +64,7 @@ static bool prv_uart_irq_handler(UARTDevice *dev, uint8_t data, const UARTRXErro
void dbgserial_input_init(void) {
exti_configure_pin(BOARD_CONFIG.dbgserial_int, ExtiTrigger_Falling, dbgserial_interrupt_handler);
// some platforms have a seperate pin for the EXTI int and the USART
// some platforms have a separate pin for the EXTI int and the USART
if (BOARD_CONFIG.dbgserial_int_gpio.gpio != NULL) {
gpio_input_init(&BOARD_CONFIG.dbgserial_int_gpio);
}

4
src/fw/drivers/rtc.h
View file

@ -30,11 +30,11 @@ typedef uint64_t RtcTicks;
void rtc_init(void);
//! Calibrate the RTC driver using the given crystal frequency (in mHz).
//! This is a seperate step because rtc_init needs to run incredibly early in the startup process
//! This is a separate step because rtc_init needs to run incredibly early in the startup process
//! and the manufacturing registry won't be initialized yet.
void rtc_calibrate_frequency(uint32_t frequency);
//! Initialize any timers the RTC driver may need. This is a seperate step than rtc_init because
//! Initialize any timers the RTC driver may need. This is a separate step than rtc_init because
//! rtc_init needs to run incredibly early in the startup process and at that time the timer
//! system won't be initialized yet.
void rtc_init_timers(void);

2
src/fw/services/normal/data_logging/dls_list.h
View file

@ -40,7 +40,7 @@ void dls_list_insert_session(DataLoggingSession *logging_session);
//! Creates a new DataLoggingSession object that is only initialized with the parameters given. The
//! session will only be initialized with the given parameters. The .storage and .comm members must
//! be seperately initialized. Also, the resulting object will need to be added to the list of
//! be separately initialized. Also, the resulting object will need to be added to the list of
//! sessions using one of dls_list_add_new_session and dls_list_insert_session. May return NULL if
//! we've created too many sessions.
DataLoggingSession *dls_list_create_session(uint32_t tag, DataLoggingItemType type, uint16_t size,