diff options
author | Sascha Hauer <[email protected]> | 2022-11-23 10:55:27 +0100 |
---|---|---|
committer | Alexandre Belloni <[email protected]> | 2023-02-09 23:01:49 +0100 |
commit | e5c594233fcf1a55a439dec103aa815cdbf392a7 (patch) | |
tree | 7050bb9d95aafa01a1bc374fa12efcacab588237 /tools/perf/scripts/python/failed-syscalls-by-pid.py | |
parent | 19409796578c879a41e88ddbdbce50c19457658d (diff) |
rtc: rv8803: invalidate date/time if alarm time is invalid
RTC core never calls rv8803_set_alarm with an invalid alarm time,
so if an invalid alarm time > 0 is set, external factors must have
corrupted the RTC's alarm time and possibly other registers.
Play it safe by marking the date/time invalid, so all registers are
reinitialized on a ->set_time.
This may cause existing setups to lose time if they so far set only
date/time, but ignored that the alarm registers had an invalid date
value, e.g.:
rtc rtc0: invalid alarm value: 2020-3-27 7:82:0
These systems will have their ->get_time return -EINVAL till
->set_time initializes the alarm value (and sets a new time).
Signed-off-by: Ahmad Fatoum <[email protected]>
Signed-off-by: Sascha Hauer <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Alexandre Belloni <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/failed-syscalls-by-pid.py')
0 files changed, 0 insertions, 0 deletions