| Message ID | 3fac202ead48b50c0967c62eae92fe9786fd24a1.1425015704.git.viresh.kumar@linaro.org |
|---|---|
| State | New |
| Headers | show |
On 03/27/2015 06:16 PM, Viresh Kumar wrote: > On 27 February 2015 at 13:16, Uwe Kleine-König > <u.kleine-koenig@pengutronix.de> wrote: >> Hello Viresh, >> >> On Fri, Feb 27, 2015 at 11:12:33AM +0530, Viresh Kumar wrote: >>> We have used CLOCK_EVT_MODE_PERIODIC instead of CLOCK_EVT_FEAT_PERIODIC while >>> defining features. Fix it. >>> >>> Cc: Uwe Kleine-Koenig <u.kleine-koenig@pengutronix.de> >>> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> >> Makes sense, thanks for catching. >> >> Acked-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> > > @Daniel: Have you applied this one ? Nope, I missed it. Applied in my tree. Thanks for the heads up. -- Daniel
diff --git a/drivers/clocksource/time-efm32.c b/drivers/clocksource/time-efm32.c index bba62f9deefb..9edeab37a14b 100644 --- a/drivers/clocksource/time-efm32.c +++ b/drivers/clocksource/time-efm32.c @@ -111,7 +111,7 @@ static irqreturn_t efm32_clock_event_handler(int irq, void *dev_id) static struct efm32_clock_event_ddata clock_event_ddata = { .evtdev = { .name = "efm32 clockevent", - .features = CLOCK_EVT_FEAT_ONESHOT | CLOCK_EVT_MODE_PERIODIC, + .features = CLOCK_EVT_FEAT_ONESHOT | CLOCK_EVT_FEAT_PERIODIC, .set_mode = efm32_clock_event_set_mode, .set_next_event = efm32_clock_event_set_next_event, .rating = 200,
We have used CLOCK_EVT_MODE_PERIODIC instead of CLOCK_EVT_FEAT_PERIODIC while defining features. Fix it. Cc: Uwe Kleine-Koenig <u.kleine-koenig@pengutronix.de> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> --- drivers/clocksource/time-efm32.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)