Lines Matching full:alarm
76 * @name Alarm configuration flags
78 * @brief Used in alarm configuration structure (@ref counter_alarm_cfg).
82 * @brief Counter alarm absolute value flag.
90 * @brief Alarm flag enabling immediate expiration when driver detects that
91 * absolute alarm was set too late.
93 * Alarm callback must be called from the same context as if it was set on time.
109 * absolute alarm (see @ref counter_set_channel_alarm).
115 /** @brief Alarm callback
119 * @param ticks Counter value that triggered the alarm.
126 /** @brief Alarm callback structure.
130 * Callback called on alarm (cannot be NULL).
134 * Number of ticks that triggers the alarm.
137 * COUNTER_ALARM_CFG_ABSOLUTE). Both, relative and absolute, alarm
139 * @ref counter_get_top_value). When setting an absolute alarm value
142 * manages to activate the alarm. Therefore a guard period can be
155 * Alarm flags (see @ref COUNTER_ALARM_FLAGS).
205 * Number of channels that can be used for setting alarm.
268 * @brief Function to get number of alarm channels.
272 * @return Number of alarm channels.
435 * @brief Set a single shot alarm on a channel.
437 * After expiration alarm can be set again, disabling is not needed. When alarm
445 * @param alarm_cfg Alarm configuration.
450 * @retval -EINVAL if alarm settings are invalid.
451 * @retval -ETIME if absolute alarm was set too late.
452 * @retval -EBUSY if alarm is already active.
473 * @brief Cancel an alarm on a channel.
506 * there is no active channel alarm.
520 * @retval -EBUSY if any alarm is active.
584 * When setting an absolute alarm value close to the current counter value there
586 * before the driver manages to activate the alarm. If this would go unnoticed
587 * then the alarm would only expire after the timer has wrapped and reached the
593 * most to actually activate the alarm after the driver API has been called. If
598 * either ignore the alarm or expire it immediately in such a case.
619 * If you need only short alarm periods, you can set the guard period very high