Hi John,
On 5/30/2018 7:50 AM, John Stultz wrote:
On Tue, May 29, 2018 at 2:49 AM, Mukesh Ojha wrote:
Currently, for both non-stop clocksource and persistent clock
there is a corner case, when a driver failed to go suspend mode
rtc_resume() injects the sleeptime as timekeeping_rtc_skipresume(
On Tue, May 29, 2018 at 2:49 AM, Mukesh Ojha wrote:
> Currently, for both non-stop clocksource and persistent clock
> there is a corner case, when a driver failed to go suspend mode
> rtc_resume() injects the sleeptime as timekeeping_rtc_skipresume()
> returned 'false' due to which we can see mism
Currently, for both non-stop clocksource and persistent clock
there is a corner case, when a driver failed to go suspend mode
rtc_resume() injects the sleeptime as timekeeping_rtc_skipresume()
returned 'false' due to which we can see mismatch in time between
system clock and other timers.
Success
3 matches
Mail list logo
