linux-toradex.git/drivers/clocksource/sun4i_timer.c, branch v4.4-rc6

clockevents/drivers/sun4i: Migrate to new 'set-state' interface

2015-08-10T09:40:40+00:00

Migrate sun4i driver to the new 'set-state' interface provided by
clockevents core, the earlier 'set-mode' interface is marked obsolete
now.

This also enables us to implement callbacks for new states of clockevent
devices, for example: ONESHOT_STOPPED.

Cc: Maxime Ripard 
Signed-off-by: Viresh Kumar 
Signed-off-by: Daniel Lezcano 
Acked-by: Maxime Ripard

clocksource/drivers/sun4i-timer: Only register a sched_clock on sun4i and sun5i

2015-03-31T07:15:58+00:00

sun6i and newer have an arm arch timer which is a better
sched_clock source then the sun4i-timer, and sched_clock does
not have priorities, so do not register the sun4i-timer
sched_clock at all on sun6i and newer.

Signed-off-by: Hans de Goede 
Signed-off-by: Daniel Lezcano 
Acked-by: Maxime Ripard 
Cc: ben.dooks@codethink.co.uk
Cc: digetx@gmail.com
Cc: laurent.pinchart+renesas@ideasonboard.com
Cc: linux-arm-kernel@lists.infradead.org
Cc: viresh.kumar@linaro.org
Link: http://lkml.kernel.org/r/1427746633-9137-8-git-send-email-daniel.lezcano@linaro.org
Signed-off-by: Ingo Molnar

clockevent: sun4i: Fix race condition in the probe code

2014-11-19T09:43:51+00:00

The interrupts were activated and the handler registered before the clockevent
was registered in the probe function.

The interrupt handler, however, was making the assumption that the clockevent
device was registered.

That could cause a null pointer dereference if the timer interrupt was firing
during this narrow window.

Fix that by moving the clockevent registration before the interrupt is enabled.

Reported-by: Roman Byshko 
Signed-off-by: Maxime Ripard 
Cc: stable@vger.kernel.org
Signed-off-by: Daniel Lezcano

clocksource: sunxi: Add new compatibles

2014-03-11T22:04:46+00:00

The Allwinner A10 compatibles were following a slightly different compatible
patterns than the rest of the SoCs for historical reasons. Add compatibles
matching the other pattern to the timer driver for consistency, and keep the
older one for backward compatibility.

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

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