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: bidirectional

Browse source 
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
This commit is contained in:
Josh Soref 2025-01-28 12:51:10 -05:00
parent dc157413ef
commit 0ab43a028e
2 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
src/fw/drivers/stm32f2/spi.c
View file

@ -291,7 +291,7 @@ static void prv_spi_slave_deinit(const SPISlavePort *slave) {
//! The assertion and deassertion of the SCS line is automatic
//
static bool prv_is_bidrectional(const SPISlavePort *slave) {
static bool prv_is_bidirectional(const SPISlavePort *slave) {
bool is_bidirectional = (slave->spi_direction == SpiDirection_2LinesFullDuplex) ||
(slave->spi_direction == SpiDirection_2LinesRxOnly);
@ -304,7 +304,7 @@ void spi_slave_port_deinit(const SPISlavePort *slave) {
return;
}
prv_spi_slave_deinit(slave);
prv_spi_bus_deinit(slave->spi_bus, prv_is_bidrectional(slave));
prv_spi_bus_deinit(slave->spi_bus, prv_is_bidirectional(slave));
slave->slave_state->initialized = false;
}
@ -316,7 +316,7 @@ void spi_slave_port_init(const SPISlavePort *slave) {
slave->slave_state->initialized = true;
slave->slave_state->acquired = false;
slave->slave_state->scs_selected = false;
prv_spi_bus_init(slave->spi_bus, prv_is_bidrectional(slave));
prv_spi_bus_init(slave->spi_bus, prv_is_bidirectional(slave));
// SCS
gpio_output_init(&slave->spi_scs, GPIO_OType_PP, slave->spi_bus->spi_sclk_speed);

2
src/fw/services/normal/settings/settings_file.h
View file

@ -32,7 +32,7 @@
//! operations are atomic, so a reboot in the middle of changing the value for a
//! key will always either complete, returning the new value upon reboot, or
//! will just return the old value.
//! It also supports bidirection syncronization between the phone & watch,
//! It also supports bidirectional syncronization between the phone & watch,
//! using timestamps to resolve conflicts.
//! Note that although all operations are atomic, they are not thread-safe. If
//! you will be accessing a SettingsFile from multiple threads, make sure you