rtc: pcf8523: set range

Set the th RTC range, it is a classic BCD RTC, considering 00 as a leap
year. Let the core handle range checking.

Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Link: https://lore.kernel.org/r/20201118002747.1346504-2-alexandre.belloni@bootlin.com

diff --git a/drivers/rtc/rtc-pcf8523.c b/drivers/rtc/rtc-pcf8523.c
index b525998cd70e8a99ff42724b951bc9f9fdbd885d..d5f913cb2ec9f9b1236ed03d349a587030689e7b 100644 (file)
--- a/drivers/rtc/rtc-pcf8523.c
+++ b/drivers/rtc/rtc-pcf8523.c
@@ -226,17 +226,6 @@ static int pcf8523_rtc_set_time(struct device *dev, struct rtc_time *tm)
        u8 regs[8];
        int err;
 
-       /*
-        * The hardware can only store values between 0 and 99 in it's YEAR
-        * register (with 99 overflowing to 0 on increment).
-        * After 2100-02-28 we could start interpreting the year to be in the
-        * interval [2100, 2199], but there is no path to switch in a smooth way
-        * because the chip handles YEAR=0x00 (and the out-of-spec
-        * YEAR=0xa0) as a leap year, but 2100 isn't.
-        */
-       if (tm->tm_year < 100 || tm->tm_year >= 200)
-               return -EINVAL;
-
        err = pcf8523_stop_rtc(client);
        if (err < 0)
                return err;
@@ -361,6 +350,8 @@ static int pcf8523_probe(struct i2c_client *client,
                return PTR_ERR(rtc);
 
        rtc->ops = &pcf8523_rtc_ops;
+       rtc->range_min = RTC_TIMESTAMP_BEGIN_2000;
+       rtc->range_max = RTC_TIMESTAMP_END_2099;
 
        return devm_rtc_register_device(rtc);
 }