| commit | 5580ea4576b60a4fa615c85e254fab1401149b45 | |
| author | Dmitry Osipenko <digetx@gmail.com> | |
| Mon, 24 Oct 2016 15:26:52 +0000 (24 16:26 +0100) | ||
| committer | Peter Maydell <peter.maydell@linaro.org> | |
| Mon, 24 Oct 2016 15:26:52 +0000 (24 16:26 +0100) | ||
| tree | 3d7d4dbe2ed49179b0b6a3ea352925ade49ec480 | treesnapshot (tar.gz zip) |
| parent | 56700e1aa6959c082a839285022fa4e48d5cf512 | commitdiff |
hw/ptimer: Add "no counter round down" policy
For most of the timers counter starts to decrement after first period
expires. Due to rounding down performed by the ptimer_get_count, it returns
counter - 1 for the running timer, so that for the ptimer user it looks
like counter gets decremented immediately after running the timer. Add "no
counter round down" policy that provides correct behaviour for those timers.
Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
Message-id: ef39622d0ebfdc32a0877e59ffdf6910dc3db688.1475421224.git.digetx@gmail.com
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
For most of the timers counter starts to decrement after first period
expires. Due to rounding down performed by the ptimer_get_count, it returns
counter - 1 for the running timer, so that for the ptimer user it looks
like counter gets decremented immediately after running the timer. Add "no
counter round down" policy that provides correct behaviour for those timers.
Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
Message-id: ef39622d0ebfdc32a0877e59ffdf6910dc3db688.1475421224.git.digetx@gmail.com
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
| hw/core/ptimer.c | diffblobblamehistory | |
| include/hw/ptimer.h | diffblobblamehistory |