Hi Kukjin,
Just trying to learn what other people are doing in their platforms, so
apologies if my comments aren't applicable! Looks good to me though.
On Wed, Dec 22, 2010 at 08:27:01PM +0900, Kukjin Kim wrote:
> From: Changhwan Youn <chaos.youn@xxxxxxxxxxx>
>
> The Multi-Core Timer(MCT) of S5PV310 is designed for implementing
> clock source timer and clock event timers. This patch implements
> 1 clock source timer with 64 bit free running counter of MCT and
> 2 clock event timers with two of 31-bit tick counters.
>
> Signed-off-by: Changhwan Youn <chaos.youn@xxxxxxxxxxx>
> Cc: Ben Dooks <ben-linux@xxxxxxxxx>
> Cc: Russell King <rmk+kernel@xxxxxxxxxxxxxxxx>
> Signed-off-by: Kukjin Kim <kgene.kim@xxxxxxxxxxx>
> ---
> arch/arm/mach-s5pv310/Kconfig | 7 +
> arch/arm/mach-s5pv310/Makefile | 8 +-
> arch/arm/mach-s5pv310/include/mach/regs-mct.h | 47 ++++
> arch/arm/mach-s5pv310/mct.c | 365 +++++++++++++++++++++++++
> 4 files changed, 426 insertions(+), 1 deletions(-)
> create mode 100644 arch/arm/mach-s5pv310/include/mach/regs-mct.h
> create mode 100644 arch/arm/mach-s5pv310/mct.c
[...]
> diff --git a/arch/arm/mach-s5pv310/mct.c b/arch/arm/mach-s5pv310/mct.c
> new file mode 100644
> index 0000000..2fe189c
> --- /dev/null
> +++ b/arch/arm/mach-s5pv310/mct.c
[...]
> +static struct clock_event_device mct_tick0_device = {
> + .name = "mct-tick0",
> + .features = CLOCK_EVT_FEAT_PERIODIC | CLOCK_EVT_FEAT_ONESHOT,
> + .rating = 450,
> + .shift = 20,
> + .set_next_event = s5pv310_tick0_set_next_event,
> + .set_mode = s5pv310_tick0_set_mode,
> +};
> +
> +static struct clock_event_device mct_tick1_device = {
> + .name = "mct-tick1",
> + .features = CLOCK_EVT_FEAT_PERIODIC | CLOCK_EVT_FEAT_ONESHOT,
> + .rating = 450,
> + .shift = 20,
> + .set_next_event = s5pv310_tick1_set_next_event,
> + .set_mode = s5pv310_tick1_set_mode,
> +};
Do you need to specify .shift here? Could you use
clockevents_calc_mult_shift() to calculate mult and shift for you?
> +irqreturn_t s5pv310_mct0_event_isr(int irq, void *dev_id)
> +{
> + struct clock_event_device *evt;
> +
> + /* Clear the MCT tick interrupt */
> +
> + evt = &mct_tick0_device;
> + if (evt->mode != CLOCK_EVT_MODE_PERIODIC)
> + s5pv310_mct_tick_stop(MCT_TICK0);
I don't think you need to stop the timer here, the clockevents layer
will handle this for you.
[...]
> +static void s5pv310_mct_clockevent_init(struct clock_event_device *dev)
> +{
> + dev->mult = div_sc(clk_rate / 2, NSEC_PER_SEC, dev->shift);
> +
> + dev->max_delta_ns = clockevent_delta2ns(0xfffffff, dev);
Is there a reason that the delta is only using 28 bits here?
Jamie
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
