[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.10.1406112012460.5170@nanos>
Date: Wed, 11 Jun 2014 20:14:02 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Matthias Brugger <matthias.bgg@...il.com>
cc: linux-kernel@...r.kernel.org, robh+dt@...nel.org,
pawel.moll@....com, mark.rutland@....com,
ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
rdunlap@...radead.org, linux@....linux.org.uk,
daniel.lezcano@...aro.org, grant.likely@...aro.org,
thierry.reding@...il.com, florian.vaussard@...l.ch,
jic23@...nel.org, jason@...edaemon.net, andrew@...n.ch,
silvio.fricke@...il.com, heiko.stuebner@...com, olof@...om.net,
sebastian.hesselbarth@...il.com, sboyd@...eaurora.org,
gregory.clement@...e-electrons.com, arnd@...db.de,
robherring2@...il.com, marc.zyngier@....com,
maxime.ripard@...e-electrons.com, soren.brinkmann@...inx.com,
shawn.guo@...escale.com, anders.berg@....com,
linus.walleij@...aro.org, devicetree@...r.kernel.org,
linux-doc@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v8 2/7] clocksource: Add support for the Mediatek SoCs
On Wed, 11 Jun 2014, Matthias Brugger wrote:
> +static void mtk_clkevt_mode(enum clock_event_mode mode,
> + struct clock_event_device *clk)
> +{
> + struct mtk_clock_event_device *evt = to_mtk_clk(clk);
> +
> + mtk_clkevt_time_stop(evt, GPT_CLK_EVT);
> +
> + switch (mode) {
> + case CLOCK_EVT_MODE_PERIODIC:
> + mtk_clkevt_time_setup(evt, evt->ticks_per_jiffy, GPT_CLK_EVT);
> + mtk_clkevt_time_start(evt, true, GPT_CLK_EVT);
> + break;
> + case CLOCK_EVT_MODE_ONESHOT:
> + mtk_clkevt_time_start(evt, false, GPT_CLK_EVT);
Why start the timer here? The code will call set next event right away.
> + break;
> + case CLOCK_EVT_MODE_UNUSED:
> + case CLOCK_EVT_MODE_SHUTDOWN:
> + default:
> + /* No more interrupts will occur as source is disabled */
> + break;
> + }
> +}
Looks good otherwise.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists