user/sven/linux.git/include/linux/rtc.h, branch v4.19.14

rtc: remove struct rtc_task

2018-08-02T15:16:05Z

Include rtc_task members directly in rtc_timer member. Signed-off-by: Alexandre Belloni

rtc: simplify rtc_irq_set_state/rtc_irq_set_freq

2018-07-26T13:08:53Z

The PIE doesn't handle tasks anymore, remove the pointer from the interface. Signed-off-by: Alexandre Belloni

rtc: remove irq_task and irq_task_lock

2018-07-26T13:08:53Z

There is no way to set a periodic task anymore, remove task pointer and lock. Signed-off-by: Alexandre Belloni

rtc: remove rtc_irq_register/rtc_irq_unregister

2018-07-26T13:08:50Z

The rtc_irq_* interface is not used from outside the RTC subsytem since 2016. Signed-off-by: Alexandre Belloni

rtc: nvmem: don't return an error when not enabled

2018-05-16T19:08:42Z

Avoid reporting an error when RTC_NVMEM is not selected. Reported-by: kernel test robot Signed-off-by: Alexandre Belloni

rtc: Add useful timestamp definitions

2018-03-17T13:20:55Z

Add commonly used timestamps for range definition. Signed-off-by: Alexandre Belloni

rtc: Add one offset seconds to expand RTC range

2018-03-17T13:20:55Z

From our investigation for all RTC drivers, 1 driver will be expired before year 2017, 7 drivers will be expired before year 2038, 23 drivers will be expired before year 2069, 72 drivers will be expired before 2100 and 104 drivers will be expired before 2106. Especially for these early expired drivers, we need to expand the RTC range to make the RTC can still work after the expired year. So we can expand the RTC range by adding one offset to the time when reading from hardware, and subtracting it when writing back. For example, if you have an RTC that can do 100 years, and currently is configured to be based in Jan 1 1970, so it can represents times from 1970 to 2069. Then if you change the start year from 1970 to 2000, which means it can represents times from 2000 to 2099. By adding or subtracting the offset produced by moving the wrap point, all times between 1970 and 1999 from RTC hardware could get interpreted as times from 2070 to 2099, but the interpretation of dates between 2000 and 2069 would not change. Signed-off-by: Baolin Wang Signed-off-by: Alexandre Belloni

rtc: Add RTC range

2018-03-17T13:20:54Z

Add a way for drivers to inform the core of the supported date/time range. The core can then check whether the date/time or alarm is in the range before calling ->set_time, ->set_mmss or ->set_alarm. It returns -ERANGE when the time is out of range. Signed-off-by: Alexandre Belloni

char: rtc: remove unused rtc_control() API

2018-03-01T09:49:37Z

Since commit 34ce71a96dcb ("ALSA: timer: remove legacy rtctimer"), the rtc_register/rtc_control/rtc_unregister API is unused. As it is highly unlikely to be needed again, remove it. Acked-by: Greg Kroah-Hartman Acked-by: Arnd Bergmann Signed-off-by: Alexandre Belloni

rtc: remove nvmem_config

2018-03-01T09:49:23Z

Because nvmem_config is only used and copied at nvmem registration, remove it from struct rtc_device. All the rtc drivers using nvmem are now calling rtc_nvmem_register directly. Signed-off-by: Alexandre Belloni