rtc kconfig: point out need for static linkage

55ff1aba · David Brownell <[email protected]> · 2007-07-21 04:37:56 -07:00

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 <[email protected]>
Acked-by: Alessandro Zummo <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>

Commit: 55ff1aba940ff46d4f6d4fd790ea3e1a47aaa84f
Parents: ef154ec6

Changes

1 files changed · +3 −0

File	Status	Add	Del	Content
drivers/rtc/Kconfig	modified	+3	−0	View file

drivers/rtc/Kconfig

View file

diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig
index 35f3466..505f512 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).