20a0130
From a97ad0c4b447a132a322cedc3a5f7fa4cab4b304 Mon Sep 17 00:00:00 2001
20a0130
From: Miroslav Lichvar <mlichvar@redhat.com>
20a0130
Date: Thu, 1 Aug 2013 19:31:35 +0200
20a0130
Subject: [PATCH] ntp: Make periodic RTC update more reliable
20a0130
20a0130
The current code requires that the scheduled update of the RTC happens
20a0130
in the closest tick to the half of the second. This seems to be
20a0130
difficult to achieve reliably. The scheduled work may be missing the
20a0130
target time by a tick or two and be constantly rescheduled every second.
20a0130
20a0130
Relax the limit to 10 ticks. As a typical RTC drifts in the 11-minute
20a0130
update interval by several milliseconds, this shouldn't affect the
20a0130
overall accuracy of the RTC much.
20a0130
20a0130
Signed-off-by: Miroslav Lichvar <mlichvar@redhat.com>
20a0130
Signed-off-by: John Stultz <john.stultz@linaro.org>
20a0130
---
20a0130
 kernel/time/ntp.c |    3 ++-
20a0130
 1 file changed, 2 insertions(+), 1 deletion(-)
20a0130
20a0130
diff --git a/kernel/time/ntp.c b/kernel/time/ntp.c
20a0130
index 8f5b3b9..ab1fa7c 100644
20a0130
--- a/kernel/time/ntp.c
20a0130
+++ b/kernel/time/ntp.c
20a0130
@@ -475,6 +475,7 @@ static void sync_cmos_clock(struct work_struct *work)
20a0130
 	 * called as close as possible to 500 ms before the new second starts.
20a0130
 	 * This code is run on a timer.  If the clock is set, that timer
20a0130
 	 * may not expire at the correct time.  Thus, we adjust...
20a0130
+	 * We want the clock to be within a couple of ticks from the target.
20a0130
 	 */
20a0130
 	if (!ntp_synced()) {
20a0130
 		/*
20a0130
@@ -485,7 +486,7 @@ static void sync_cmos_clock(struct work_struct *work)
20a0130
 	}
20a0130
 
20a0130
 	getnstimeofday(&now;;
20a0130
-	if (abs(now.tv_nsec - (NSEC_PER_SEC / 2)) <= tick_nsec / 2) {
20a0130
+	if (abs(now.tv_nsec - (NSEC_PER_SEC / 2)) <= tick_nsec * 5) {
20a0130
 		struct timespec adjust = now;
20a0130
 
20a0130
 		fail = -ENODEV;
20a0130
-- 
20a0130
1.7.9.5
20a0130