linux-toradex.git/drivers/clocksource/sun4i_timer.c, branch v3.14.3

Merge branch 'clockevents/3.14' of git://git.linaro.org/people/daniel.lezcano/linux into timers/core

2014-01-14T13:33:29+00:00

Pull clocksource/clockevent updates from Daniel Lezcano:

  * Axel Lin removed an unused structure defining the ids for the
    bcm kona driver.

  * Ezequiel Garcia enabled the timer divider only when the 25MHz
    timer is not used for the armada 370 XP.

  * Jingoo Han removed a pointless platform data initialization for
    the sh_mtu and sh_mtu2.

  * Laurent Pinchart added the clk_prepare/clk_unprepare for sh_cmt.

  * Linus Walleij added a useful warning in clk_of when no clocks
    are found while the old behavior was to silently hang at boot time.

  * Maxime Ripard added the high speed timer drivers for the
    Allwinner SoCs (A10, A13, A20). He increased the rating, shared the
    irq across all available cpus and fixed the clockevent's irq
    initialization for the sun4i.

  * Michael Opdenacker removed the usage of the IRQF_DISABLED for the
    all the timers driver located in drivers/clocksource.

  * Stephen Boyd switched to sched_clock_register for the
    arm_global_timer, cadence_ttc, sun4i and orion timers.

Conflicts:
	drivers/clocksource/clksrc-of.c

Signed-off-by: Ingo Molnar

clocksource: sun4i: Switch to sched_clock_register()

2013-12-11T10:40:24+00:00

The 32 bit sched_clock interface now supports 64 bits. Upgrade to
the 64 bit function to allow us to remove the 32 bit registration
interface. While we're here, mark the sched_clock function as
notrace to prevent ftrace recursion crashes.

Cc: Maxime Ripard 
Acked-by: Maxime Ripard 
Signed-off-by: Stephen Boyd 
Signed-off-by: Daniel Lezcano

clocksource: sun4i: Increase a bit the clock event and sources rating

2013-12-11T10:07:31+00:00

We want to keep this driver as the default provider of the clock events
and source, yet some other driver might fit in the "desired" category of
ratings. Hence, we need to increase a bit the rating so that we can have
more flexibility in the ratings we choose.

Signed-off-by: Maxime Ripard 
Tested-by: Emilio López 
Signed-off-by: Daniel Lezcano

clocksource: sun4i: Change CPU mask to cpu_possible_mask

2013-12-11T10:07:30+00:00

The interrupt for the timer is a shared processor interrupt, so any CPU
found in the system can handle it. Switch to our cpumask to
cpu_possible_mask instead of cpumask_of(0).

Signed-off-by: Maxime Ripard 
Signed-off-by: Daniel Lezcano 
Reviewed-by: Stephen Boyd

clockevent: sun4i: Fill the irq field in the clockevent structure

2013-12-11T10:07:29+00:00

The clock event structure irq field was not filled previously to the
interrupt we're using.

This was resulting in the timer not being used at all when using a
configuration with SMP enabled on a system with several CPUs, and with
the cpumask set to the cpu_possible_mask.

Signed-off-by: Maxime Ripard 
Signed-off-by: Daniel Lezcano 
Reviewed-by: Stephen Boyd

clocksource: sunxi: Stop timer from ticking before enabling interrupts

2013-12-10T18:41:28+00:00

The sun4i timer can still be ticking when we enable the interrupt.
If another timer is actually used (A7 architected timer, for example),
odds are that the interrupt will eventually fire with the event_handler
pointer being NULL.

The obvious fix it to stop the timer before registering the interrupt.

Observed and tested on sun7i (cubietruck).

Cc: Daniel Lezcano 
Acked-by: Maxime Ripard 
Signed-off-by: Marc Zyngier 
Signed-off-by: Daniel Lezcano

clocksource: sun4i: remove IRQF_DISABLED

2013-10-22T20:36:50+00:00

IRQF_DISABLED is a no-op nowadays, so we can safely remove it.

Signed-off-by: Maxime Ripard 
Signed-off-by: Daniel Lezcano

clocksource: sun4i: Report the minimum tick that we can program

2013-10-22T20:36:43+00:00

We need to wait for at least 2 clock cycles whenever we reprogram our
clockevent timer. Report that the minimum number of ticks we can handle
is 3 ticks, and remove 3 ticks to the interval programmed to reflect
this.

Signed-off-by: Maxime Ripard 
Signed-off-by: Daniel Lezcano

clocksource: sun4i: Fix bug when switching from periodic to oneshot modes

2013-07-18T13:27:21+00:00

The interval was firing at was set up at probe time, and only changed in
the set_next_event, and never changed back, which is not really what is
expected.

When enabling the periodic mode, now set an interval to tick every
jiffy.

Signed-off-by: Maxime Ripard 
Signed-off-by: Daniel Lezcano

clocksource: sun4i: Cleanup parent clock setup

2013-07-18T13:27:20+00:00

The current bring-up code for the timer was overly complicated. The only
thing we need is actually which clock we want to use as source and
that's pretty much all. Let's keep it that way.

Signed-off-by: Maxime Ripard 
Signed-off-by: Daniel Lezcano