[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20191029074603.499a3940@kemnade.info>
Date: Tue, 29 Oct 2019 07:46:03 +0100
From: Andreas Kemnade <andreas@...nade.info>
To: Alexandre Belloni <alexandre.belloni@...tlin.com>
Cc: lee.jones@...aro.org, a.zummo@...ertech.it,
linux-kernel@...r.kernel.org, linux-rtc@...r.kernel.org,
phh@....me, b.galvani@...il.com, stefan@...er.ch,
letux-kernel@...nphoenux.org
Subject: Re: [PATCH 5/5] rtc: rtc-rc5t583: add ricoh rc5t619 RTC driver
On Thu, 24 Oct 2019 01:17:17 +0200
Alexandre Belloni <alexandre.belloni@...tlin.com> wrote:
[...]
> > > Is the RTC 1900-2099 or 2000-2199? Please include the ouput of rtc-range
> > > in the commit log:
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/abelloni/rtc-tools.git/tree/rtc-range.c
> > >
> > # ./rtc-range
> >
> > Testing 2000-02-28 23:59:59.
> > OK
> >
> > Testing 2038-01-19 03:14:07.
> > OK
> >
> > Testing 2069-12-31 23:59:59.
> > OK
> >
> > Testing 2099-12-31 23:59:59.
> > KO RTC_RD_TIME returned 22 (line 138)
> >
> > Testing 2100-02-28 23:59:59.
> > KO RTC_RD_TIME returned 22 (line 138)
> >
> > Testing 2106-02-07 06:28:15.
> > OK
> >
> > Testing 2262-04-11 23:47:16.
> > KO Read back 2102-04-11 23:47:16.
> >
> > I think it is 1900 to 2099.
> >
>
> It is, I'm very curious to know why it doesn't roll over properly from
> 2099-12-31 23:59:59 to 1900-01-01 00:00:00.
>
It rolls over correcly, but rtc_valid_tm() bails out if
year < 70.
I am preparing a v2 of this series.
Regards,
Andreas
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists