Re: [RFC/PATCH 00/11] arm: omap: counter32k rework
From: Arnd Bergmann
Date: Wed Sep 30 2015 - 10:50:04 EST
On Wednesday 30 September 2015 16:42:21 Arnd Bergmann wrote:
> TEGRA folks: the tegra_read_persistent_clock() implementation apparently
> predates the Tegra RTC driver and I wonder if they actually do the
> right thing in combination. Could it be that the wall time forwards
> twice as fast as it should during resume when the RTC driver is loaded?
> Could it be that we can simply remove tegra_read_persistent_clock()
> and the register_persistent_clock() infrastructure?
I found the 'sleeptime_injected' variable now, which takes care of
forwarding the clock by the correct amount.
I also found the CLOCK_SOURCE_SUSPEND_NONSTOP flag next to it, which
should let us use the counter32k driver to provide the correct
time during suspend without the omap_read_persistent_clock() function.
We should be able to just delete that code.
If we decide to also delete the tegra_read_persistent_clock()
function, we can remove the registration too.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/