* Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx> [130121 13:07]:This is right. It was only because of the drift associated when clocked
As for Samsung and the rest I can't comment. The original reason OMAP
used this though was because the 32768Hz counter can't produce 100Hz
without a .1% error - too much error under pre-clocksource
implementations for timekeeping. Whether that's changed with the
clocksource/clockevent support needs to be checked.
Yes that's why HZ was originally set to 128. That value (or some multiple)
still makes sense when the 32 KiHZ clock source is being used. Of course
we should rely on the local timer when running for the SoCs that have
them.