Searched refs:alarms (Results 1 – 25 of 83) sorted by relevance
1234
40 struct rtc_emul_alarm *alarms; member151 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 …]
24 This is an option which enables driver support for RTC alarms.
14 RTC alarms during testing.
37 alarms-count = <1>;
29 RTCs usually contain one or more alarms which can be configured to30 trigger at a given time. These alarms are commonly used to wake up the82 for testing. To test the optional alarms, update event callback139 * RTC alarms are not persistent across application initialization.142 Every time an application is initialized, the RTC's time and alarms are reset. Reading
38 alarms-count = <1>;
58 alarms-count = <1>;
86 alarms-count = <1>;
412 alarms-count = <1>;
12 and supports alarms. The `Chronodot`_ breakout board can be used to78 We're now 2.131 ms into the run, at which point the alarms are read back82 2131 ms in: get alarms: 0 0
23 - 2 Timer with 4 alarms, 1 AON Timer
207 alarms-count = <2>;
218 alarms-count = <2>;
263 alarms-count = <1>;
256 alarms-count = <1>;
321 alarms-count = <1>;
244 alarms-count = <1>;
160 alarms-count = <2>;
39 - RTC with HW calendar, alarms and calibration
38 - RTC with HW calendar, alarms and calibration
338 alarms-count = <1>;
356 alarms-count = <1>;
51 - RTC with HW calendar, alarms and calibration
100 alarms-count = <2>;
214 alarms-count = <1>;
