diff options
| author | Santosh Shilimkar <santosh.shilimkar@ti.com> | 2013-01-31 19:32:00 +0400 |
|---|---|---|
| committer | Tony Lindgren <tony@atomide.com> | 2013-02-02 02:51:22 +0400 |
| commit | 8f0de0d62f29e47f5142737dad7561f108f69e92 (patch) | |
| tree | 69a7627eab131309d5e4654fd1bbbce330f15f43 /arch/arm/mach-omap2/id.c | |
| parent | 14e067c1a5280fe6fe5d3348a0bae87bc4da16db (diff) | |
| download | linux-8f0de0d62f29e47f5142737dad7561f108f69e92.tar.xz | |
ARM: OMAP2+: Get rid of custom OMAP_32K_TIMER_HZ
The timekeeping doesn't depend on HZ value in presence of fine grained
clocksource and hence there should not be any time drift because of HZ
value which was chosen to be divisor of 32768.
OMAP has been using HZ = 128 value to avoid any time drift issues
because of 32768 HZ clock. But with various measurements performed
with HZ = 100, no time drift is observed and it also proves the
point about HZ not having impact on time keeping on OMAP.
Very informative thread on this topic is here:
https://lkml.org/lkml/2013/1/29/435
Special thanks to John Stulz, Arnd Bergmann and Russell King for their
valuable suggestions.
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Russell King <linux@arm.linux.org.uk>
Cc: John Stultz <john.stultz@linaro.org>
Cc: Tony Lindgren <tony@atomide.com>
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Tested-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'arch/arm/mach-omap2/id.c')
0 files changed, 0 insertions, 0 deletions