On Thu, 17 Aug 2023 15:55:30 -0700, Guenter Roeck wrote:
> Some alarm timers are based on time offsets, not on absolute times.
> In some situations, the amount of time that can be scheduled in the
> future is limited. This may result in a refusal to suspend the system,
> causing substantial battery drain.
>
> This problem was previously observed on a Chromebook using the cros_ec
> rtc driver. EC variants on some older Chromebooks only support 24 hours
> of alarm time in the future. To work around the problem on affected
> Chromebooks, code to limit the maximum alarm time was added to the cros_ec
> rtc driver with commit f27efee66370 ("rtc: cros-ec: Limit RTC alarm range
> if needed"). The problem is now seen again on a system using the cmos
> RTC driver on hardware limited to 24 hours of alarm time, so a more
> generic solution is needed.
>
> [...]
Applied, thanks!
[1/7] rtc: Add support for limited alarm timer offsets
commit: 781589e40ac5f929f58824c15448e1ba49c3ac32
[3/7] rtc: cros-ec: Detect and report supported alarm window size
commit: 00c3092d881bc9d63dc36eecd140cdb38962c7ec
[4/7] rtc: cmos: Report supported alarm limit to rtc infrastructure
commit: 2546e7083f2ea96bdd6157961dc2748d65a9e487
[5/7] rtc: tps6586x: Report maximum alarm limit to rtc core
commit: 3637bbdc8a446b8edb369383d2abc816c96ee864
[6/7] rtc: ds1305: Report maximum alarm limit to rtc core
commit: 46b79ac0b463e155b098805ff66f1f22ff249b45
[7/7] rtc: rzn1: Report maximum alarm limit to rtc core
commit: 2b0386d578836b9cd5d2e63cff38b7229c319e4a
Best regards,
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
