[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6944324.e1oo8C9xbx@wuerfel>
Date: Wed, 30 Sep 2015 16:49:53 +0200
From: Arnd Bergmann <arnd@...db.de>
To: linux-arm-kernel@...ts.infradead.org
Cc: balbi@...com, Alexandre Courbot <gnurou@...il.com>,
Stephen Warren <swarren@...dotorg.org>,
Tony Lindgren <tony@...mide.com>, daniel.lezcano@...aro.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Thierry Reding <thierry.reding@...il.com>,
linux-tegra@...r.kernel.org, tglx@...utronix.de,
Linux OMAP Mailing List <linux-omap@...r.kernel.org>
Subject: Re: [RFC/PATCH 00/11] arm: omap: counter32k rework
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.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists