Commit 754d5c2b authored by Jonas Bonn's avatar Jonas Bonn
Browse files

openrisc: Set shortest clock event to 100 ticks

It takes a couple of instructions to actually configure a clock event
so setting an alarm just 1 clock cycle in the future isn't going to work;
doing so results in setting an alarm in the "past" in which case the event
won't fire until the timer overflows and rolls back around to the "current

Not quite sure how many clock cycles it actually takes to get through to
actually writing the register, but 100 seems to work reliably.

Use generic helper to set up the clock event while we're at it.

Reported-by: default avatarJan Schulte <>
Signed-off-by: default avatarJonas Bonn <>
parent 17425275
......@@ -125,16 +125,13 @@ irqreturn_t __irq_entry timer_interrupt(struct pt_regs *regs)
static __init void openrisc_clockevent_init(void)
cpuinfo.clock_frequency, 4);
clockevent_openrisc_timer.cpumask = cpumask_of(0);
/* We only have 28 bits */
clockevent_openrisc_timer.max_delta_ns =
clockevent_delta2ns((u32) 0x0fffffff, &clockevent_openrisc_timer);
clockevent_openrisc_timer.min_delta_ns =
clockevent_delta2ns(1, &clockevent_openrisc_timer);
clockevent_openrisc_timer.cpumask = cpumask_of(0);
100, 0x0fffffff);
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment