zephyr/drivers/clock_control
Thiago Silveira 1d8c8ac3af clock_control: nrf5_power: Let the LF clock be configured at least once
If the LF clock was already started, but wasn't initialized with
_k32src_start yet, allow it to run once. This is needed because if a
soft reset is triggered while watchdog is active, the LF clock will
already be running, but won't be configured yet (watchdog forces LF
clock to be running).

If the LF clock isn't configured with _k32src_start, the nRF5 RTC
won't count and the whole system will malfunction, as the kernel
depends on the clock source being working properly.

Signed-off-by: Thiago Silveira <thiago@exati.com.br>
2017-10-08 23:05:34 -04:00
..
beetle_clock_control.c
Kconfig Kconfig: make all syslog variables depend on SYS_LOG 2017-08-04 14:34:54 -05:00
Kconfig.beetle
Kconfig.nrf5 clock_control: nRF5x: Select 251-500ppm as default for 32kHz RCOSC 2017-07-11 10:29:46 -05:00
Kconfig.quark_se
Kconfig.stm32
Makefile
nrf5_power_clock.c clock_control: nrf5_power: Let the LF clock be configured at least once 2017-10-08 23:05:34 -04:00
quark_se_clock_control.c
stm32_ll_clock.c
stm32_ll_clock.h
stm32f1x_ll_clock.c
stm32f3x_ll_clock.c
stm32f4x_ll_clock.c
stm32l4x_ll_clock.c