From 2a90e913f4c8e0d08aa652ebfa86a41a32da0070 Mon Sep 17 00:00:00 2001 From: David Brownell Date: Sat, 21 Jul 2007 04:37:56 -0700 Subject: [PATCH] --- yaml --- r: 62342 b: refs/heads/master c: 55ff1aba940ff46d4f6d4fd790ea3e1a47aaa84f h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/drivers/rtc/Kconfig | 3 +++ 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/[refs] b/[refs] index f607c6f6ba73..d00a01d98c78 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: ef154ec69c45aa052b1fa71ee5eeaca7e7f920a3 +refs/heads/master: 55ff1aba940ff46d4f6d4fd790ea3e1a47aaa84f diff --git a/trunk/drivers/rtc/Kconfig b/trunk/drivers/rtc/Kconfig index 35f34665e3c4..505f512ac254 100644 --- a/trunk/drivers/rtc/Kconfig +++ b/trunk/drivers/rtc/Kconfig @@ -38,6 +38,9 @@ config RTC_HCTOSYS_DEVICE clock, usually rtc0. Initialization is done when the system starts up, and when it resumes from a low power state. + The driver for this RTC device must be loaded before late_initcall + functions run, so it must usually be statically linked. + This clock should be battery-backed, so that it reads the correct time when the system boots from a power-off state. Otherwise, your system will need an external clock source (like an NTP server).