From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
rtc-linux@googlegroups.com,
Alessandro Zummo <a.zummo@towertech.it>, Willy Tarreau <w@1wt.eu>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rtc: Add an option to invalidate dates in 2038
Date: Sun, 21 Feb 2016 00:42:51 +0100 [thread overview]
Message-ID: <20160220234251.GL2222@piout.net> (raw)
In-Reply-To: <20160220231702.GK2222@piout.net>
On 21/02/2016 at 00:17:02 +0100, Alexandre Belloni wrote :
> All the failures seem quite random to me but the reports I get are not
> that precise.
>
> I know it happens with PCF8523 and that can be true because the
> datasheet says the date is undefined at reset. The handling of the OS
> bit (that bit indicates the date is probably wrong) has to be fixed and
> I will take care of that.
>
> If that is the only RTC with that particular issue, we clearly don't
> need my workaround. But As I say, I can ask but I don't have a clear
> list of the affected system and their RTC.
>
I add that it also seem to affect the Allwinner A20 RTC. I'm not sure
how much we can trust the datasheet but it claims the reset value is 0
and I don't think there is a way to know whether the date is correct or
not.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-20 23:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 19:10 [PATCH] rtc: Add an option to invalidate dates in 2038 Alexandre Belloni
2016-02-20 19:43 ` One Thousand Gnomes
2016-02-20 20:47 ` Alexandre Belloni
2016-02-20 22:16 ` Arnd Bergmann
2016-02-20 23:17 ` Alexandre Belloni
2016-02-20 23:42 ` Alexandre Belloni [this message]
2016-02-21 12:40 ` One Thousand Gnomes
2016-02-22 13:00 ` Alexandre Belloni
2016-02-22 13:43 ` One Thousand Gnomes
2016-02-22 15:44 ` Arnd Bergmann
2016-02-22 15:56 ` Alexandre Belloni
2016-02-22 16:18 ` Arnd Bergmann
2016-02-22 16:40 ` Alexandre Belloni
2016-02-22 16:41 ` Austin S. Hemmelgarn
2016-02-22 16:58 ` Alexandre Belloni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160220234251.GL2222@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=arnd@arndb.de \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=w@1wt.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox