aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/rtc/rtc-rs5c348.c
diff options
context:
space:
mode:
authorAlexandre Belloni <alexandre.belloni@bootlin.com>2018-02-21 00:20:43 +0100
committerAlexandre Belloni <alexandre.belloni@bootlin.com>2018-03-01 10:49:40 +0100
commitbff11e3aa9ccfce1a66ef05871d01c1da533f896 (patch)
tree0b63ea90eeb19143e52a910f06026c8214d9f5a6 /drivers/rtc/rtc-rs5c348.c
parent812318a094d0715194d9f686b22ee67e7dc59d93 (diff)
downloadlinux-bff11e3aa9ccfce1a66ef05871d01c1da533f896.tar.gz
rtc: rs5c348: let the core handle invalid time
Returning a valid time when the time is invalid is a bad practice, because then userspace is not able to react on the information. Also, it doesn't make sense to return epoch because it is already the default time. Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Diffstat (limited to 'drivers/rtc/rtc-rs5c348.c')
-rw-r--r--drivers/rtc/rtc-rs5c348.c5
1 files changed, 0 insertions, 5 deletions
diff --git a/drivers/rtc/rtc-rs5c348.c b/drivers/rtc/rtc-rs5c348.c
index 9a306983aabae..f2de8b17e7e36 100644
--- a/drivers/rtc/rtc-rs5c348.c
+++ b/drivers/rtc/rtc-rs5c348.c
@@ -135,11 +135,6 @@ rs5c348_rtc_read_time(struct device *dev, struct rtc_time *tm)
tm->tm_year = bcd2bin(rxbuf[RS5C348_REG_YEAR]) +
((rxbuf[RS5C348_REG_MONTH] & RS5C348_BIT_Y2K) ? 100 : 0);
- if (rtc_valid_tm(tm) < 0) {
- dev_err(&spi->dev, "retrieved date/time is not valid.\n");
- rtc_time_to_tm(0, tm);
- }
-
return 0;
}