From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752621AbbI3OuC (ORCPT ); Wed, 30 Sep 2015 10:50:02 -0400 Received: from mout.kundenserver.de ([212.227.126.187]:64504 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751317AbbI3Ot7 (ORCPT ); Wed, 30 Sep 2015 10:49:59 -0400 From: Arnd Bergmann To: linux-arm-kernel@lists.infradead.org Cc: balbi@ti.com, Alexandre Courbot , Stephen Warren , Tony Lindgren , daniel.lezcano@linaro.org, Linux Kernel Mailing List , Thierry Reding , linux-tegra@vger.kernel.org, tglx@linutronix.de, Linux OMAP Mailing List Subject: Re: [RFC/PATCH 00/11] arm: omap: counter32k rework Date: Wed, 30 Sep 2015 16:49:53 +0200 Message-ID: <6944324.e1oo8C9xbx@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <3705422.OMk7ysE7Jn@wuerfel> References: <1443559446-26969-1-git-send-email-balbi@ti.com> <20150930141338.GC31865@saruman.tx.rr.com> <3705422.OMk7ysE7Jn@wuerfel> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:tk/mY6Gy8H+nAmdABfzJTv89mRvlyACWT+Q8p3bZ6l4zud8Re7k Rl2JFj7INzb10jGUamLarRvuZajAR5qPL9KilMQwK+hhGt8+SCGlVKODoUnVnik09ndpWp3 kFGqdJj+p2kpTCPOWqmSKTMnXpwIVQjsnemYvHehJLRD+LTYD/uaVc1iNxStt+RrkrY4FB2 RrTY2MS3vVHprMt2ixMNw== X-UI-Out-Filterresults: notjunk:1;V01:K0:glkrPpuiO3g=:Zqp8nYLcSNzCnq9DL6uJpR 6/ZEmugbMowGSFKatmZtvF5CD/1G1ZydTKZZpL5DH6PdjkL1y4jFdGzqeJpFWMZA3bBYEmRvO P4SPjlStiofZg5MMNt/ktHQ4QDdZOU/4KVm0dkqbALWhXeWAhy3XiVbZTwro/nvK7H6qr8Ucv UvBOtXBD0FgwOqq2LAgqw8UJd3e93mfgu6MuXwpVzchzqZ7EpEdgWFdcN0mNdYj89q5UDNbHg lja1gViX02tyTIvr1bpenxtk23Je2DZ3li5FEqda7H5zvrVZysvK0euML+/pWpahTSINUhl9n H5jLgMaq2VfHl7P8xk5G+oYU9U9YQHPr16HW1ZeoTFjHtVhcfk2RyvaDAvsxeOL3oIStpKKmN hP129Do96itWWlywcIt0AIPcCazVL9AdPAhex7NGEDeh92qOG3zj9Mfz+on7F3nKUc5MkZwOX 9o5/dLrtY1IXuj5eesU9CIPwS02PCqW6Tvb+f6EZmnTE63SNH6peKz5zshU77tr3eneRETZfY BIrrFl6F8c/46m31SrN9iNEczce1RJ/yuEflDk6cV17NxbbZYNQXjp6ojC0eEV4qkblLFagQR Ke1Bo8E5KQSJaKoDvKXq+Fz0l6RBJt6wmSXPSV+p+F+Tbf0pzs0+P3kBVOTMXpj6M9hTE/YQ1 1i3h2c5PzyXB7Qn9hVNGHwLub3TnTzzR3FXraBY/AVaxVEN8/Gp35OYG/H3L5NsRLrYbO+XJK jvvaDlW6abGh8Woj Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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