From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755227Ab3DYHLh (ORCPT ); Thu, 25 Apr 2013 03:11:37 -0400 Received: from h1446028.stratoserver.net ([85.214.92.142]:45339 "EHLO mail.ahsoftware.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753812Ab3DYHLg (ORCPT ); Thu, 25 Apr 2013 03:11:36 -0400 Message-ID: <5178D719.2060405@ahsoftware.de> Date: Thu, 25 Apr 2013 09:11:21 +0200 From: Alexander Holler User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130402 Thunderbird/17.0.5 MIME-Version: 1.0 To: John Stultz CC: Kay Sievers , LKML , Feng Tang , Jason Gunthorpe Subject: Re: CONFIG_RTC_HCTOSYS lost on x86 with ALWAYS_USE_PERSISTENT_CLOCK changes? References: <517746E4.908@linaro.org> <51774F44.2060704@linaro.org> <517769A9.5060308@ahsoftware.de> <51780348.6090202@linaro.org> In-Reply-To: <51780348.6090202@linaro.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am 24.04.2013 18:07, schrieb John Stultz: >> And why is RTC_SYSTOHC now gone on x86? > > So summarizing the above, because as much as I'm aware, its always been > redundant and unnecessary on x86. Thus being able at build time to mark > it as unnecessary was attractive, since it reduced the code paths > running at suspend/resume. Hmm, I thought RTC_SYSTOHC was there to update the used RTC clock with the time from NTP (and liked that). Therefor I don't understand why it is redundant and unnecessary on x86. Of course, most systems do have something in userspace to set the RTC on shutdown, so it isn't really needed. Anyway, thanks a lot for the great overview. I was totally unaware about the persistent_clock framework on x86. Regards, Alexander