From: Arnd Bergmann Date: Wed, 11 Jul 2018 12:47:12 +0000 (+0200) Subject: rtc: use ktime_get_real_ts64() instead of getnstimeofday64() X-Git-Tag: v4.19~347^2~20 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=5089ea15baa9e7b0cb49f36881f2cb27bf281789;p=platform%2Fkernel%2Flinux-rpi.git rtc: use ktime_get_real_ts64() instead of getnstimeofday64() getnstimeofday64() is just a wrapper around the ktime accessor, so we should use that directly. I considered using ktime_get_boottime_ts64() (to avoid leap second problems) or ktime_get_real_seconds() (to simplify the calculation, but in the end concluded that the existing interface is probably the most appropriate in this case. Signed-off-by: Arnd Bergmann Signed-off-by: Alexandre Belloni --- diff --git a/drivers/rtc/class.c b/drivers/rtc/class.c index d37588f..7fa32c9 100644 --- a/drivers/rtc/class.c +++ b/drivers/rtc/class.c @@ -68,7 +68,7 @@ static int rtc_suspend(struct device *dev) return 0; } - getnstimeofday64(&old_system); + ktime_get_real_ts64(&old_system); old_rtc.tv_sec = rtc_tm_to_time64(&tm); @@ -110,7 +110,7 @@ static int rtc_resume(struct device *dev) return 0; /* snapshot the current rtc and system time at resume */ - getnstimeofday64(&new_system); + ktime_get_real_ts64(&new_system); err = rtc_read_time(rtc, &tm); if (err < 0) { pr_debug("%s: fail to read rtc time\n", dev_name(&rtc->dev));