include/hw/ptimer.h

16  * ptimer_get_count() and ptimer_set_count()). When it is enabled
19  * When it reaches zero it will trigger a callback function, and
26  * When ptimer_transaction_commit() is called it will evaluate the state
31  * Forgetting to set the period/frequency (or setting it to zero) is a
39  * It has several weird behaviours which don't match typical hardware
46  * consider updating it to specify the right policy flags.
55  *  - Starting to run with counter = 0 or setting it to "0" while timer
90  * (though it will cause a reload). Only a counter decrement to "0"
119  * is called it will evaluate the state of the timer after all the
147  * It is an error to call this function for a BH-based ptimer;
158  * callback, it will be called directly.
171  * This function will assert if it is called outside a
183  * way to tell the ptimer about the period, because it avoids any
192  * This function will assert if it is called outside a
206  * because it allows specifying an effective period which is
209  * This function will assert if it is called outside a
219  * of the down-counter; that is, the value which it will be
220  * reset to when it hits zero.
224  * and set limit functions rather than needing to also track it
239  * This function will assert if it is called outside a
263  * This function will assert if it is called outside a
273  * Start a ptimer counting down; when it reaches zero the callback function
276  * the counter value will then be reloaded from the limit and it will
278  * will disable itself when it reaches zero.
280  * This function will assert if it is called outside a
290  * is called to start it counting again).
292  * Note that this can cause it to "lose" time, even if it is immediately
295  * This function will assert if it is called outside a