Repository navigation
ec-acpi: Time and Alarm ACPI and Notification code #149
Description
Implement and check in ASL code for time and alarm features defined by ACPI and in the EC minimum requirements document.
Metadata
Metadata
Assignees
Labels
No labels
Activity
dymk commentedon Sep 30, 2026
Landed scope and remaining work (2026-09-30)
The platform RTC ASL is shipped and exercised through the actual Windows ACPI -> FF-A -> SP -> EC path. OpenDevicePartnership/odp-platform-qemu-arm-virt#180 landed timestamp set/readback, AC/DC nonzero expired-status clearing, policy 0/45 readback, checked NEVER setter acceptance/peer isolation, and normalized setter failures (_SRT: 0xFFFFFFFF; _CWS/_STV/_STP: 1). The final Windows fixture passed 40 assertions. A focused regression separately exercised actual-ASL rejection of nonzero SP status.
Supporting work landed in OpenDevicePartnership/odp-secure-services#101, OpenDevicePartnership/odp-platform-common#219, OpenDevicePartnership/odp-platform-common#220, and OpenDevicePartnership/odp-embedded-controller#47. Documentation examples and the shipped platform ASL are distinct; the Windows result qualifies the latter.
Not implemented or qualified by this work: real sleep-to-wake transitions, active AC/DC power-source integration, and asynchronous ACPI/FF-A notification delivery. Related remaining trackers are #689, #733, and #160. The EC triggered-wake bit alone is not physical-wake evidence.
This records the completed synchronous-method portion without closing the broader ACPI/notification issue. Maintainers can reconcile its remaining notification obligations with those trackers before deciding closure.