| commit | a399e3fa795afa058e4485b25c498e0c5a860428 | |
| author | Nicolas Pitre <nico@cam.org> | |
| Fri, 15 May 2009 04:42:36 +0000 (15 00:42 -0400) | ||
| committer | Nicolas Pitre <nico@cam.org> | |
| Mon, 8 Jun 2009 17:04:54 +0000 (8 13:04 -0400) | ||
| tree | ce58f69f27ff8dc3b188f7e66dff9c19910d3646 | treesnapshot (tar.gz zip) |
| parent | 8a3269fc21cc4405d80b362139c078cf655a505a | commitdiff |
[ARM] orion: make sure sched_clock() usage of cnt32_to_63() is safe
With a TCLK = 200MHz, the half period of the hardware timer is roughly
10 seconds. Because cnt32_to_63() must be called at least once per
half period of the base hardware counter, it is a bit risky to rely
solely on scheduling to generate frequent enough calls. Let's use a
kernel timer to ensure this.
Signed-off-by: Nicolas Pitre <nico@marvell.com>
With a TCLK = 200MHz, the half period of the hardware timer is roughly
10 seconds. Because cnt32_to_63() must be called at least once per
half period of the base hardware counter, it is a bit risky to rely
solely on scheduling to generate frequent enough calls. Let's use a
kernel timer to ensure this.
Signed-off-by: Nicolas Pitre <nico@marvell.com>
| arch/arm/plat-orion/time.c | diffblobblamehistory |