lkml.org 
[lkml]   [2015]   [Mar]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 11/11] clocksource: efm32: Use CLOCK_EVT_FEAT_PERIODIC for defining features
    Date
    From: Viresh Kumar <viresh.kumar@linaro.org>

    We have used CLOCK_EVT_MODE_PERIODIC instead of CLOCK_EVT_FEAT_PERIODIC while
    defining features. Fix it.

    Acked-by: Uwe Kleine-Koenig <u.kleine-koenig@pengutronix.de>
    Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
    Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
    ---
    drivers/clocksource/time-efm32.c | 2 +-
    1 file changed, 1 insertion(+), 1 deletion(-)

    diff --git a/drivers/clocksource/time-efm32.c b/drivers/clocksource/time-efm32.c
    index ec57ba2..5b6e3d5 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,
    --
    1.9.1


    \
     
     \ /
      Last update: 2015-03-30 23:01    [W:2.893 / U:0.540 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site