Commit 55ff1aba authored Jul 21, 2007 by David Brownell Committed by Linus Torvalds Jul 21, 2007

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>

parent ef154ec6

drivers/rtc/Kconfig

+3 −0

Original line number	Diff line number	Diff line
		@@ -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).