summaryrefslogtreecommitdiff
path: root/drivers/rtc/ds1302.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/ds1302.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/ds1302.c')
-rw-r--r--drivers/rtc/ds1302.c6
1 files changed, 5 insertions, 1 deletions
diff --git a/drivers/rtc/ds1302.c b/drivers/rtc/ds1302.c
index 55af130..3a856c8 100644
--- a/drivers/rtc/ds1302.c
+++ b/drivers/rtc/ds1302.c
@@ -253,9 +253,10 @@ rtc_reset(void)
/* TODO */
}
-void
+int
rtc_get(struct rtc_time *tmp)
{
+ int rel = 0;
struct ds1302_st bbclk;
if(!ds1302_initted) rtc_init();
@@ -265,6 +266,7 @@ rtc_get(struct rtc_time *tmp)
if (bbclk.CH) {
printf("ds1302: rtc_get: Clock was halted, clock probably "
"corrupt\n");
+ rel = -1;
}
tmp->tm_sec=10*bbclk.sec10+bbclk.sec;
@@ -281,6 +283,8 @@ rtc_get(struct rtc_time *tmp)
DPRINTF("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 rel;
}
void