Re: [PATCH 1/3] time: Don't bother to run rtc_resume() for nonstop clocksource

On Tue, 20 Jan 2015, Xunlei Pang wrote: > --- > drivers/rtc/class.c | 2 +- > include/linux/timekeeping.h | 11 +++ > kernel/time/timekeeping.c | 3 ++- > 3 files changed, 14 insertions(+), 2 deletions(-) > > diff --git a/drivers/rtc/class.c b/drivers/rtc/class.c > index

Re: [PATCH 1/3] time: Don't bother to run rtc_resume() for nonstop clocksource

On Tue, 20 Jan 2015, Xunlei Pang wrote: --- drivers/rtc/class.c | 2 +- include/linux/timekeeping.h | 11 +++ kernel/time/timekeeping.c | 3 ++- 3 files changed, 14 insertions(+), 2 deletions(-) diff --git a/drivers/rtc/class.c b/drivers/rtc/class.c index

[PATCH 1/3] time: Don't bother to run rtc_resume() for nonstop clocksource

If a system does not provide a persistent_clock(), the time will be updated on resume by rtc_resume(). With the addition of the non-stop clocksources for suspend timing, those systems set the time on resume in timekeeping_resume(), but may not provide a valid persistent_clock(). This results in

[PATCH 1/3] time: Don't bother to run rtc_resume() for nonstop clocksource

If a system does not provide a persistent_clock(), the time will be updated on resume by rtc_resume(). With the addition of the non-stop clocksources for suspend timing, those systems set the time on resume in timekeeping_resume(), but may not provide a valid persistent_clock(). This results in