summaryrefslogtreecommitdiff
path: root/post
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 /post
parent23e20aa6488e6c0622496549861bfdc74108debe (diff)
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 'post')
-rw-r--r--post/drivers/rtc.c15
1 files changed, 15 insertions, 0 deletions
diff --git a/post/drivers/rtc.c b/post/drivers/rtc.c
index 7d4f9b88ee6..e3da5e64ced 100644
--- a/post/drivers/rtc.c
+++ b/post/drivers/rtc.c
@@ -28,6 +28,8 @@
*
* The Real Time Clock (RTC) operation is verified by this test.
* The following features are verified:
+ * o) RTC Power Fault
+ * This is verified by analyzing the rtc_get() return status.
* o) Time uniformity
* This is verified by reading RTC in polling within
* a short period of time.
@@ -96,6 +98,10 @@ int rtc_post_test (int flags)
unsigned int ynl = 1999;
unsigned int yl = 2000;
unsigned int skipped = 0;
+ int reliable;
+
+ /* Time reliability */
+ reliable = rtc_get (&svtm);
/* Time uniformity */
if (rtc_post_skip (&diff) != 0) {
@@ -176,6 +182,15 @@ int rtc_post_test (int flags)
}
rtc_post_restore (&svtm, skipped);
+ /* If come here, then RTC operates correcty, check the correctness
+ * of the time it reports.
+ */
+ if (reliable < 0) {
+ post_log ("RTC Time is not reliable! Power fault? \n");
+
+ return -1;
+ }
+
return 0;
}