diff options
| author | Russell King <rmk+kernel@armlinux.org.uk> | 2017-09-23 19:27:37 +0100 |
|---|---|---|
| committer | Russell King (Oracle) <rmk+kernel@armlinux.org.uk> | 2025-04-04 15:20:01 +0100 |
| commit | 91d826c70dfde25201eed873f9748dccdeac9a92 (patch) | |
| tree | e6564db48af78def44a7025b1a12d1cb967e58dc | |
| parent | cd8d54831870500bbbfe8436e59cee5ec4765a8b (diff) | |
rtc: armada38x: provide set_offset_nsecrtc
Armada 388 resets the prescaler when the time register is written, so
it requires the current second as close to the start of that second as
possible. The data sheet is a bit unclear, so this has been confirmed
on real hardware.
Verified on Armada 388 based Clearfog.
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
| -rw-r--r-- | drivers/rtc/rtc-armada38x.c | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/drivers/rtc/rtc-armada38x.c b/drivers/rtc/rtc-armada38x.c index 713fa0d077cd..1e9fb2876677 100644 --- a/drivers/rtc/rtc-armada38x.c +++ b/drivers/rtc/rtc-armada38x.c @@ -447,6 +447,15 @@ static int armada38x_rtc_set_offset(struct device *dev, long offset) return 0; } +static void armada38x_rtc_pre_register(struct rtc_device *rtc) +{ + /* + * The Armada 388 resets the prescaler when we write the time. + * Validated on clearfog. + */ + rtc->set_offset_nsec = 0; +} + static const struct rtc_class_ops armada38x_rtc_ops = { .read_time = armada38x_rtc_read_time, .set_time = armada38x_rtc_set_time, @@ -455,6 +464,7 @@ static const struct rtc_class_ops armada38x_rtc_ops = { .alarm_irq_enable = armada38x_rtc_alarm_irq_enable, .read_offset = armada38x_rtc_read_offset, .set_offset = armada38x_rtc_set_offset, + .pre_register = armada38x_rtc_pre_register, }; static const struct armada38x_rtc_data armada38x_data = { |