summaryrefslogtreecommitdiff
path: root/drivers/rtc/m41t60.c
diff options
context:
space:
mode:
authorYuri Tikhonov <yur@emcraft.com>2008-03-20 17:56:04 +0300
committerWolfgang Denk <wd@denx.de>2008-03-20 21:48:46 +0100
commitb73a19e1609d0f705cbab8014ca17aefe89e4c76 (patch)
tree4f6752b24fe118da445233479396497d516a1e50 /drivers/rtc/m41t60.c
parent23e20aa6488e6c0622496549861bfdc74108debe (diff)
downloadu-boot-imx-b73a19e1609d0f705cbab8014ca17aefe89e4c76.zip
u-boot-imx-b73a19e1609d0f705cbab8014ca17aefe89e4c76.tar.gz
u-boot-imx-b73a19e1609d0f705cbab8014ca17aefe89e4c76.tar.bz2
LWMON5: POST RTC fix
Modify the RTC API to provide one a status for the time reported by the rtc_get() function: 0 - a reliable time is guaranteed, < 0 - a reliable time isn't guaranteed (power fault, clock issues, and so on). The RTC chip drivers are responsible for providing this info if the corresponding chip supports such functionality. If not - always report that the time is reliable. The POST RTC test was modified to detect the RTC faults utilizing this new rtc_get() feature. Signed-off-by: Yuri Tikhonov <yur@emcraft.com>
Diffstat (limited to 'drivers/rtc/m41t60.c')
-rw-r--r--drivers/rtc/m41t60.c6
1 files changed, 4 insertions, 2 deletions
diff --git a/drivers/rtc/m41t60.c b/drivers/rtc/m41t60.c
index 7c80143..8a32ea0 100644
--- a/drivers/rtc/m41t60.c
+++ b/drivers/rtc/m41t60.c
@@ -170,12 +170,12 @@ static uchar *rtc_validate(void)
return data;
}
-void rtc_get(struct rtc_time *tmp)
+int rtc_get(struct rtc_time *tmp)
{
uchar const *const data = rtc_validate();
if (!data)
- return;
+ return -1;
tmp->tm_sec = bcd2bin(data[RTC_SEC] & 0x7F);
tmp->tm_min = bcd2bin(data[RTC_MIN] & 0x7F);
@@ -190,6 +190,8 @@ void rtc_get(struct rtc_time *tmp)
debug("Get DATE: %4d-%02d-%02d (wday=%d) TIME: %2d:%02d:%02d\n",
tmp->tm_year, tmp->tm_mon, tmp->tm_mday, tmp->tm_wday,
tmp->tm_hour, tmp->tm_min, tmp->tm_sec);
+
+ return 0;
}
void rtc_set(struct rtc_time *tmp)