[PATCH] omap3: beagle: Use GPTIMERi 1 for clockevents
From: paul@pwsan.com (Paul Walmsley)
Date: 2011-06-25 22:47:00
Also in:
linux-omap
From: paul@pwsan.com (Paul Walmsley)
Date: 2011-06-25 22:47:00
Also in:
linux-omap
On Sun, 26 Jun 2011, Premi, Sanjeev wrote:
[sp] I didn't include a reason - because the problem may not
be reproducible on the public trees.
During tests performed in internal development trees, the
BogoMIPS calculations @ 1GHz wouldn't go beyond "830-850"
range. While there was no such inconsistency on OMAP3EVM.There are some other reasons to avoid GPTIMER12 when possible, which you should probably put in the patch description. The most important, in my view, is that the clock source for GPTIMER12 is much less frequency-stable than the clock sources for GPTIMER1. So using GPTIMER12 can result in major time skew over a fairly short interval. I've been meaning to send a patch like this for some time, so I'm happy to see this fixed. - Paul