Messages in this thread | | | Date | Mon, 23 Jan 2023 11:21:28 -0800 | Subject | Re: [PATCH 3/6] rtc: brcmstb-waketimer: compensate for lack of wktmr disable | From | Florian Fainelli <> |
| |
On 1/20/23 11:01, Doug Berger wrote: > Since the WKTMR hardware block cannot be disabled it is necessary > for the driver to accommodate for associated timing hazards. This > commit targets the following possibilities: > > A possible race between clearing a wktmr event and the alarm expiring > is made one-sided by setting the alarm to its maximum value before > clearing the event. > > Programming alarm values close to the current time may not trigger > events if the counter advances while the alarm is being programmed. > After programming an alarm, a check is made to ensure that it is > either in the future or an expiration event is pending. > > Signed-off-by: Doug Berger <opendmb@gmail.com>
Acked-by: Florian Fainelli <f.fainelli@gmail.com> -- Florian
| |