mirror of
https://github.com/Motorhead1991/qemu.git
synced 2025-12-11 16:00:50 -07:00
hw/ptimer: Add "no immediate trigger" policy
Performing trigger on setting (or starting to run with) counter = 0 could be a wrong behaviour for some of the timers, provide "no immediate trigger" policy to maintain correct behaviour for such timers. Signed-off-by: Dmitry Osipenko <digetx@gmail.com> Message-id: 72c0319cf2ec599f22397b7da280c06c34dc40dd.1475421224.git.digetx@gmail.com Reviewed-by: Peter Maydell <peter.maydell@linaro.org> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
This commit is contained in:
parent
2e74583b29
commit
22471b8a0f
2 changed files with 20 additions and 4 deletions
|
|
@ -43,6 +43,10 @@
|
|||
* re-trigger every period. */
|
||||
#define PTIMER_POLICY_CONTINUOUS_TRIGGER (1 << 1)
|
||||
|
||||
/* Starting to run with/setting counter to "0" won't trigger immediately,
|
||||
* but after a one period for both oneshot and periodic modes. */
|
||||
#define PTIMER_POLICY_NO_IMMEDIATE_TRIGGER (1 << 2)
|
||||
|
||||
/* ptimer.c */
|
||||
typedef struct ptimer_state ptimer_state;
|
||||
typedef void (*ptimer_cb)(void *opaque);
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue