Searched full:alarms (Results 1 – 25 of 113) sorted by relevance
12345
| /Zephyr-latest/dts/bindings/rtc/ |
| D | rtc-device.yaml | 9 alarms-count:
13 Number of alarms supported by RTC device. The number of
14 alarms defaults to 0, which indicates that the RTC has
15 no alarms.
|
| D | st,stm32-rtc.yaml | 25 alarms-count:
27 Number of alarms supported by STM32 RTC device.
28 Most of STM32 MCU series have 2 RTC alarms, A & B.
|
| /Zephyr-latest/drivers/rtc/ |
| D | rtc_emul.c | 40 struct rtc_emul_alarm *alarms; member
151 alarm = &data->alarms[i]; in rtc_emul_test_alarms()
321 data->alarms[id].mask = mask; in rtc_emul_alarm_set_time()
324 data->alarms[id].datetime = *timeptr; in rtc_emul_alarm_set_time()
342 *timeptr = data->alarms[id].datetime; in rtc_emul_alarm_get_time()
343 *mask = data->alarms[id].mask; in rtc_emul_alarm_get_time()
360 ret = (data->alarms[id].pending == true) ? 1 : 0; in rtc_emul_alarm_is_pending()
362 data->alarms[id].pending = false; in rtc_emul_alarm_is_pending()
379 data->alarms[id].callback = callback; in rtc_emul_alarm_set_callback()
380 data->alarms[id].user_data = user_data; in rtc_emul_alarm_set_callback()
[all …]
|
| D | rtc_ll_stm32.h | 12 /* STM32 RTC alarms, A & B, LL masks are equal */
|
| D | Kconfig | 24 This is an option which enables driver support for RTC alarms.
|
| D | rtc_pcf8563.c | 28 /* The user may need only alarms but not interrupts so we will only
337 * There are several kinds of alarms, but here we only need to know that anything but 0 in pcf8563_alarm_is_pending()
360 LOG_ERR("Error when clearing alarms: %d", err); in pcf8563_alarm_is_pending()
366 /* No alarms */ in pcf8563_alarm_is_pending()
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | rtc.rst | 29 RTCs usually contain one or more alarms which can be configured to
30 trigger at a given time. These alarms are commonly used to wake up the
74 * Alarms if supported by hardware, with and without callback enabled
82 for testing. To test the optional alarms, update event callback
139 * RTC alarms are not persistent across application initialization.
142 Every time an application is initialized, the RTC's time and alarms are reset. Reading
|
| /Zephyr-latest/tests/drivers/rtc/rtc_api/ |
| D | Kconfig | 14 RTC alarms during testing.
|
| /Zephyr-latest/include/zephyr/drivers/rtc/ |
| D | maxim_ds3231.h | 14 * crystal oscillator and support for configurable alarms.
24 * channel 0 supports alarms at 1 s resolution, while channel 1
25 * supports alarms at 1 minute resolution.
106 * indicating which alarms are ready.
114 * indicating which alarms are ready.
152 * If set the alarm minutes field is ignored and alarms will be
166 * If set the alarm hours field is ignored and alarms will be
253 * DS3231 alarms can be set to fire at specific times or at the
260 * is present, alarms can be read using maxim_ds3231_check_alarms().
277 /** @brief Handler to be invoked when alarms are signalled.
[all …]
|
| /Zephyr-latest/samples/drivers/counter/maxim_ds3231/ |
| D | README.rst | 12 and supports alarms. The `Chronodot`_ breakout board can be used to
78 We're now 2.131 ms into the run, at which point the alarms are read back
79 and displayed. Alarms do not include date but can include day-of-week
82 2131 ms in: get alarms: 0 0
|
| /Zephyr-latest/boards/shields/adafruit_adalogger_featherwing/ |
| D | adafruit_adalogger_featherwing.overlay | 37 alarms-count = <1>;
|
| /Zephyr-latest/boards/shields/adafruit_data_logger/ |
| D | adafruit_data_logger.overlay | 58 alarms-count = <1>;
|
| /Zephyr-latest/tests/drivers/build_all/rtc/ |
| D | i2c_devices.overlay | 38 alarms-count = <1>;
|
| /Zephyr-latest/dts/x86/intel/ |
| D | atom.dtsi | 86 alarms-count = <1>;
|
| /Zephyr-latest/tests/drivers/rtc/rtc_api/src/ |
| D | test_alarm.c | 109 /* Validate alarms supported fields */ in ZTEST()
207 /* Disable and clear alarms */ in ZTEST()
|
| D | test_alarm_callback.c | 149 /* Disable and clear alarms */ in ZTEST()
|
| /Zephyr-latest/include/zephyr/drivers/timer/ |
| D | nrf_rtc_timer.h | 206 * performed when there are no active alarms set. It should be used for testing
210 * @retval -EBUSY if there are active alarms.
|
| /Zephyr-latest/boards/raspberrypi/rpi_pico2/doc/ |
| D | index.rst | 23 - 2 Timer with 4 alarms, 1 AON Timer
|
| /Zephyr-latest/drivers/counter/ |
| D | counter_mchp_xec.c | 20 * compare values for interrupts. When setting single shot alarms,
122 * So only relative alarms are supported. in counter_xec_set_alarm()
|
| D | counter_nxp_mrt.c | 188 LOG_ERR("MRT does not support alarms"); in nxp_mrt_set_alarm()
197 LOG_ERR("MRT does not support alarms"); in nxp_mrt_cancel_alarm()
|
| /Zephyr-latest/tests/drivers/counter/maxim_ds3231_api/src/ |
| D | test_counter.c | 359 * Two alarms set. First alarm is absolute, second relative. Because
360 * setting of both alarms is delayed it is expected that second alarm
391 /* Counter does not support two alarms */ in test_multiple_alarms_instance()
467 * rollover so both alarms can be tested. in test_all_channels_instance()
|
| /Zephyr-latest/tests/cmake/hwm/board_extend/oot_root/boards/native/native_sim_extend/ |
| D | native_sim_native_one.dts | 207 alarms-count = <2>;
|
| /Zephyr-latest/boards/native/native_sim/ |
| D | native_sim.dts | 218 alarms-count = <2>;
|
| /Zephyr-latest/dts/arm/atmel/ |
| D | sam3x.dtsi | 263 alarms-count = <1>;
|
| D | sam4s.dtsi | 256 alarms-count = <1>;
|
12345
