summaryrefslogtreecommitdiffstats
path: root/drivers/rtc
diff options
context:
space:
mode:
authorDavid Brownell <david-b@pacbell.net>2007-07-21 04:37:56 -0700
committerLinus Torvalds <torvalds@woody.linux-foundation.org>2007-07-21 17:49:17 -0700
commit55ff1aba940ff46d4f6d4fd790ea3e1a47aaa84f (patch)
treeb4e62791cd1cfa99349485e3fce9b514009e29f0 /drivers/rtc
parentef154ec69c45aa052b1fa71ee5eeaca7e7f920a3 (diff)
downloadlinux-55ff1aba940ff46d4f6d4fd790ea3e1a47aaa84f.tar.gz
linux-55ff1aba940ff46d4f6d4fd790ea3e1a47aaa84f.tar.bz2
linux-55ff1aba940ff46d4f6d4fd790ea3e1a47aaa84f.zip
rtc kconfig: point out need for static linkage
Various people have expressed surprise that their modular RTC drivers don't seem to work for initializing the system time at boot. To help avoid such unpleasantness, make the Kconfig text point out that the driver probably needs to be statically linked. Signed-off-by: David Brownell <dbrownell@users.sourceforge.net> Acked-by: Alessandro Zummo <a.zummo@towertech.it> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/rtc')
-rw-r--r--drivers/rtc/Kconfig3
1 files changed, 3 insertions, 0 deletions
diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig
index 35f34665e3c4..505f512ac254 100644
--- a/drivers/rtc/Kconfig
+++ b/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).