summaryrefslogtreecommitdiff
path: root/arch/mips/kernel/cevt-bcm1480.c
diff options
context:
space:
mode:
authorRalf Baechle <ralf@linux-mips.org>2007-11-11 20:24:46 +0300
committerRalf Baechle <ralf@linux-mips.org>2007-11-16 02:21:50 +0300
commit622477533d3dc24845c847f386533f3c0e6a1be6 (patch)
tree24503bc9ebe8496566991c5a7a689b4115065e7b /arch/mips/kernel/cevt-bcm1480.c
parent89becf5c0d9019f4f9300840f08a98ee33d57d37 (diff)
downloadlinux-622477533d3dc24845c847f386533f3c0e6a1be6.tar.xz
[MIPS] Sibyte: Increase minimum oneshot timer interval to two ticks.
For the old minimum of a single tick a value of zero would be programmed into the init value register which in the BCM1250/BCM1125/BCM1125H User Manual in the Timer Special Cases section is documented to have UNPREDICTABLE effect. Observable sympthoms of this bug were hangs of several seconds on the console during bootup and later if both dyntick and highres timer options were activated. In theory contiguous mode of the timers is also affected but in an act of hopeless lack of realism I'll assume nobody will ever configure a KERNEL for HZ > 500kHz but if so I leave that to evolution to sort out. Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
Diffstat (limited to 'arch/mips/kernel/cevt-bcm1480.c')
-rw-r--r--arch/mips/kernel/cevt-bcm1480.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/mips/kernel/cevt-bcm1480.c b/arch/mips/kernel/cevt-bcm1480.c
index f6fcc62ade3a..e54410e5a2cd 100644
--- a/arch/mips/kernel/cevt-bcm1480.c
+++ b/arch/mips/kernel/cevt-bcm1480.c
@@ -122,7 +122,7 @@ void __cpuinit sb1480_clockevent_init(void)
CLOCK_EVT_FEAT_ONESHOT;
clockevent_set_clock(cd, V_SCD_TIMER_FREQ);
cd->max_delta_ns = clockevent_delta2ns(0x7fffff, cd);
- cd->min_delta_ns = clockevent_delta2ns(1, cd);
+ cd->min_delta_ns = clockevent_delta2ns(2, cd);
cd->rating = 200;
cd->irq = irq;
cd->cpumask = cpumask_of_cpu(cpu);