include/hw/ptimer.h

17  * using ptimer_run(), the value will count downwards at the frequency
19  * When it reaches zero it will trigger a callback function, and
26  * When ptimer_transaction_commit() is called it will evaluate the state
32  * bug in the QEMU device and will cause warning messages to be printed
89  * ptimer_set_count() or ptimer_set_limit() will not trigger the timer
90  * (though it will cause a reload). Only a counter decrement to "0"
91  * will cause a trigger. Not compatible with NO_IMMEDIATE_TRIGGER;
92  * ptimer_init() will assert() that you don't set both.
108  * If a ptimer is created using this API then will use the
119  * is called it will evaluate the state of the timer after all the
126  * the callback will be called a second time after the first call returns.
148  * attempting to do this will trigger an assert.
158  * callback, it will be called directly.
171  * This function will assert if it is called outside a
192  * This function will assert if it is called outside a
209  * This function will assert if it is called outside a
219  * of the down-counter; that is, the value which it will be
239  * This function will assert if it is called outside a
248  * Return the current value of the down-counter. This will
260  * enabled this will arrange for a timer callback at the appropriate
263  * This function will assert if it is called outside a
274  * passed to ptimer_init() will be invoked.
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
295  * This function will assert if it is called outside a