[ARM] 4066/1: correct a comment about PXA's sched_clock range
Signed-off-by: Nicolas Pitre <nico@cam.org> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
This commit is contained in:
parent
ae2aa9073a
commit
0c48d314b1
|
@ -76,7 +76,9 @@ unsigned long long sched_clock(void)
|
||||||
/*
|
/*
|
||||||
* 96-bit math to perform tick * NSEC_PER_SEC / CLOCK_TICK_RATE for
|
* 96-bit math to perform tick * NSEC_PER_SEC / CLOCK_TICK_RATE for
|
||||||
* any value of CLOCK_TICK_RATE. Max value is in the 80 thousand
|
* any value of CLOCK_TICK_RATE. Max value is in the 80 thousand
|
||||||
* years range which is nice, but with higher computation cost.
|
* years range and truncation to unsigned long long limits it to
|
||||||
|
* sched_clock's max range of ~584 years. This is nice but with
|
||||||
|
* higher computation cost.
|
||||||
*/
|
*/
|
||||||
{
|
{
|
||||||
union {
|
union {
|
||||||
|
|
Loading…
Reference in a new issue