Comments

The purpose of this option is to allow ARM/etc systems that rely on the
class RTC subsystem to have the same kind of automatic NTP based
synchronization that we have on PC platforms. Today ARM does not
implement update_persistent_clock and makes extensive use of the class
RTC system.
When enabled CONFIG_RTC_SYSTOHC will provide a generic
rtc_update_persistent_clock that stores the current time in the RTC and
is intended complement the existing CONFIG_RTC_HCTOSYS option that loads
the RTC at boot.
Like with RTC_HCTOSYS the platform's update_persistent_clock is used
first, if it works. Platforms with mixed class RTC and non-RTC drivers
need to return ENODEV when class RTC should be used. Such an update for
PPC is included in this patch.
Long term, implementations of update_persistent_clock should migrate to
proper class RTC drivers and use CONFIG_RTC_SYSTOHC instead.
Tested on ARM kirkwood and PPC405
Signed-off-by: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
---
arch/powerpc/kernel/time.c | 2 +-
drivers/rtc/Kconfig | 9 +++++++++
drivers/rtc/Makefile | 1 +
drivers/rtc/systohc.c | 44 ++++++++++++++++++++++++++++++++++++++++++++
include/linux/time.h | 1 +
kernel/time/ntp.c | 15 +++++++++++----
6 files changed, 67 insertions(+), 5 deletions(-)
create mode 100644 drivers/rtc/systohc.c
v2 updates:
- Be very careful to return ENODEV from rtc_update_persistent_clock,
we don't want to loop on the fast retry path of sync_cmos_clock
if there is no RTC set support available
- Call the platform update_persistent_clock first. Only try
the RTC version if it is compiled out, or explicitly returns ENODEV
- Added 'depends on RTC_SYSTOHC = y' to KConfig
- Don't fast rety in sync_cmos_clock if ENODEV is returned
- Update PPC to return ENODEV if there is no mach specific function
available in ppc_md. This will give rtc_update_persistent_clock
a chance.
- Use rtc_set_time not mms since rtc_hctosys assumes UTC.