On Wed, Sep 30, 2015 at 04:49:53PM +0200, Arnd Bergmann wrote: > 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. cool, I'll try to have a look at that after this series gets accepted. -- balbi
Attachment:
signature.asc
Description: PGP signature
