[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DB7PR10MB2348BE83A0907337835A1FCBFE430@DB7PR10MB2348.EURPRD10.PROD.OUTLOOK.COM>
Date: Fri, 22 Mar 2019 15:16:54 +0000
From: Steve Twiss <stwiss.opensource@...semi.com>
To: Alexandre Belloni <alexandre.belloni@...tlin.com>,
"linux-rtc@...r.kernel.org" <linux-rtc@...r.kernel.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
Support Opensource <Support.Opensource@...semi.com>,
"linux-renesas-soc@...r.kernel.org"
<linux-renesas-soc@...r.kernel.org>
Subject: RE: [PATCH 1/2] rtc: da9063: set range
Hi Alexandre,
Thanks.
Sorry, I didn't see this immediately because of our e-mail filtering algorithm,
On 21 March 2019 10:16, Alexandre Belloni wrote,
> Subject: [PATCH 1/2] rtc: da9063: set range
> The DA9062 and DA9063 have a year register that can go up to 0x3F.
Yep.
[...]
> index 588120ba372c..09fb4af5edab 100644
> --- a/include/linux/rtc.h
> +++ b/include/linux/rtc.h
> @@ -164,6 +164,7 @@ struct rtc_device {
> /* useful timestamps */
> #define RTC_TIMESTAMP_BEGIN_1900 -2208989361LL /* 1900-01-01 00:00:00 */
> #define RTC_TIMESTAMP_BEGIN_2000 946684800LL /* 2000-01-01 00:00:00 */
> +#define RTC_TIMESTAMP_END_2063 2966371199LL /* 2063-12-31 23:59:59 */
Thanks.
Yes.
Register min and max values are:
2000-01-01 00:00:00
2063-12-31 23:59:59
Acked-by: Steve Twiss <stwiss.opensource@...semi.com>
Regards,
Steve
Powered by blists - more mailing lists