On Fri, 30 Oct 2020 16:25:23 -0700, Stephen Boyd wrote:
> The EC sends an RTC host event when the RTC fires, but we don't need to
> treat that as a wakeup event here. The RTC class already properly
> handles activating and deactivating a wakeup source in rtc_update_irq()
> by calling pm_stay_awake() at the start of processing and pm_relax()
> once all expired RTC timers have been processed. This reduces one wakeup
> increment but not much else. I noticed this while debugging RTC wakeups
> and how they always incremented the wakeup count by two instead of one
> because this is duplicated.
Applied, thanks!
[1/1] platform/chrome: Don't treat RTC events as wakeup sources
commit: 853c1a789f5fe8e783586a5c2dcc2ad1b57ac20f
Best regards,
--
Enric Balletbo i Serra <enric.balletbo@xxxxxxxxxxxxx>
