Lines Matching full:of
2 * General purpose implementation of a simple periodic countdown timer.
27 * of the timer after all the changes in the transaction, and call the
29 * list of state-modifying functions and detailed semantics of the callback.)
42 * that you need and specify the right set of policy flags to get that.
48 * The rough edges of the default policy:
52 * - Setting period to 0 of the running timer emits error message and
59 * - Counter value of the running timer is one less than the actual value.
61 * - Changing period/frequency of the running timer loses time elapsed
63 * counter = counter value at the moment of change (.i.e. one less).
83 /* Make counter value of the running timer represent the actual value and
119 * is called it will evaluate the state of the timer after all the
145 * for a list of these), and must always have a matched call to
156 * the ptimer's state, and completes the update of the ptimer. If the
165 * @period: period of the counter in nanoseconds
185 * representation of the Clock period was converted to either a period
204 * need to call one of them. If the counter behaviour is specified
207 * precise to fractions of a nanosecond, avoiding rounding errors.
215 * ptimer_get_limit - Get the configured limit of the ptimer
219 * of the down-counter; that is, the value which it will be
230 * ptimer_set_limit - Set the limit of the ptimer
235 * Set the limit value of the down-counter. The @reload flag can
236 * be used to emulate the behaviour of timers which immediately
245 * ptimer_get_count - Get the current value of the ptimer
248 * Return the current value of the down-counter. This will
255 * ptimer_set_count - Set the current value of the ptimer
259 * Set the value of the down-counter. If the counter is currently