From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752422AbbLSAbf (ORCPT ); Fri, 18 Dec 2015 19:31:35 -0500 Received: from mail-wm0-f54.google.com ([74.125.82.54]:35170 "EHLO mail-wm0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751674AbbLSAbe (ORCPT ); Fri, 18 Dec 2015 19:31:34 -0500 MIME-Version: 1.0 In-Reply-To: References: <1450220569-10670-1-git-send-email-jwerner@chromium.org> Date: Fri, 18 Dec 2015 16:31:32 -0800 X-Google-Sender-Auth: 6NoICYbZlwtxQr8OFr0i1rC0aUw Message-ID: Subject: Re: [PATCHv3] RTC: RK808: Compensate for Rockchip calendar deviation on November 31st From: Julius Werner To: Doug Anderson Cc: Julius Werner , Alexandre Belloni , Andrew Morton , Alessandro Zummo , Sonny Rao , Chris Zhong , Heiko Stuebner , LKML , rtc-linux@googlegroups.com Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > There's actually a real world case that's pretty common where we want > to work with dates before 2016. When I power cycle my device and it > totally loses battery, I notice that the firmware seems to start as: > > 2013-01-21 00:50:02 > > It's possible we could need to run for a while in this state and we > possibly could even need alarms to fire. ...but that's nowhere near > the problematic dates and presumably someone wouldn't have a system in > the "clock set totally wrong" state for a really long time. Yeah... I don't think it really makes much sense to worry about that. At that point it's much more likely that you will loose an alarm because the user finally fixes the clock at some point (either manually or by connecting to a network and having some automated sync service jump in), and we never worry about something like that either. I mean, fixing it wouldn't be a big deal (another 5 lines or so maybe), but I just don't think it's worth adding any complexity. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com. [2a00:1450:400c:c09::229]) by gmr-mx.google.com with ESMTPS id b62si285395wmc.0.2015.12.18.16.31.33 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 Dec 2015 16:31:33 -0800 (PST) Received: by mail-wm0-x229.google.com with SMTP id p187so4904440wmp.0 for ; Fri, 18 Dec 2015 16:31:33 -0800 (PST) MIME-Version: 1.0 Sender: rtc-linux@googlegroups.com In-Reply-To: References: <1450220569-10670-1-git-send-email-jwerner@chromium.org> Date: Fri, 18 Dec 2015 16:31:32 -0800 Message-ID: Subject: [rtc-linux] Re: [PATCHv3] RTC: RK808: Compensate for Rockchip calendar deviation on November 31st From: Julius Werner To: Doug Anderson Cc: Julius Werner , Alexandre Belloni , Andrew Morton , Alessandro Zummo , Sonny Rao , Chris Zhong , Heiko Stuebner , LKML , rtc-linux@googlegroups.com Content-Type: text/plain; charset=UTF-8 Reply-To: rtc-linux@googlegroups.com List-ID: List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , > There's actually a real world case that's pretty common where we want > to work with dates before 2016. When I power cycle my device and it > totally loses battery, I notice that the firmware seems to start as: > > 2013-01-21 00:50:02 > > It's possible we could need to run for a while in this state and we > possibly could even need alarms to fire. ...but that's nowhere near > the problematic dates and presumably someone wouldn't have a system in > the "clock set totally wrong" state for a really long time. Yeah... I don't think it really makes much sense to worry about that. At that point it's much more likely that you will loose an alarm because the user finally fixes the clock at some point (either manually or by connecting to a network and having some automated sync service jump in), and we never worry about something like that either. I mean, fixing it wouldn't be a big deal (another 5 lines or so maybe), but I just don't think it's worth adding any complexity. -- -- You received this message because you are subscribed to "rtc-linux". Membership options at http://groups.google.com/group/rtc-linux . Please read http://groups.google.com/group/rtc-linux/web/checklist before submitting a driver. --- You received this message because you are subscribed to the Google Groups "rtc-linux" group. To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com. For more options, visit https://groups.google.com/d/optout.