rtc: mv: reset date if after year 2038
authorThomas Petazzoni <thomas.petazzoni@free-electrons.com>
Tue, 18 Feb 2014 13:26:06 +0000 (14:26 +0100)
committerJason Cooper <jason@lakedaemon.net>
Fri, 21 Feb 2014 23:29:05 +0000 (23:29 +0000)
commite102dc7a5498439bf72ae9f6457f2e7fe09a4ae0
tree3b93a9f8c33eeb947a1be61b18c2e2dfe9b044e2
parent00b28184b1f148a60a08ddc2efd220ec4da32726
rtc: mv: reset date if after year 2038

Dates after January, 19th 2038 are badly handled by userspace due to
the time being stored on 32 bits. This causes issues on some Marvell
platform on which the RTC is initialized by default to a date that's
beyond 2038, causing a really weird behavior of the RTC.

In order to avoid that, reset the date to a sane value if the RTC is
beyond 2038.

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Jason Cooper <jason@lakedaemon.net>
drivers/rtc/rtc-mv.c