clockevents/drivers/dw_apb_timer: Implement ->set_state_oneshot_stopped()
authorJisheng Zhang <jszhang@marvell.com>
Fri, 26 Feb 2016 09:45:57 +0000 (17:45 +0800)
committerDaniel Lezcano <daniel.lezcano@linaro.org>
Thu, 28 Apr 2016 13:09:03 +0000 (15:09 +0200)
commit457353260d9ff4b89bcf21c9142b2f54ed75699e
treee6077b064485d548ce59ac071e520eeebed28ce2
parent86d3473224b004f920c107206d181d37db735145
clockevents/drivers/dw_apb_timer: Implement ->set_state_oneshot_stopped()

The dw_apb_timer only "supports PERIODIC mode and their drivers emulate
ONESHOT over that" as described in commit 8fff52fd5093 ("clockevents:
Introduce CLOCK_EVT_STATE_ONESHOT_STOPPED state").

Inspired by Viresh, I think the dw_apb_timer also needs to implement
the set_state_oneshot_stopped() which is called by the clkevt core,
when the next event is required at an expiry time of 'KTIME_MAX'. This
normally happens with NO_HZ_{IDLE|FULL} in both LOWRES/HIGHRES modes.

This patch makes the clockevent device to stop on such an event, to
avoid spurious interrupts, as explained by the above commit.

Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Reviewed-by: Viresh Kumar <viresh.kumar@linaro.org>
drivers/clocksource/dw_apb_timer.c