You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Handle Time and Alarm commands defined in the EC minimum requirements and map them to eSPI peripheral memory map. Add notification event handling for required notification events.
The synchronous TimeAlarm command path is implemented upstream. The EC already supported all nine commands; the missing secure-world SetRealTime (3), ClearWakeStatus (5), and SetExpiredTimerPolicy (8) relay handlers landed in OpenDevicePartnership/odp-secure-services#101.
The original peripheral-memory wording is superseded by the existing relay transport; the deprecated eSPI memory map was removed in #707 and must not be rebuilt.
Remaining concerns are separate: power-source integration and actual timer-triggered wake (#689), asynchronous relay notifications (#733), and any required ALERT/SCI/VWire handling (#160). Status-bit tests do not demonstrate physical wake. NEVER policy coverage proves setter acceptance and peer isolation, not independently distinguishable readback.
This comment reconciles delivered scope without closing this broader issue. Maintainers should confirm that the remaining notification/wake obligations are fully owned by the separate trackers before closing it.
Activity
dymk commentedon Sep 30, 2026
Landed scope and remaining work (2026-09-30)
The synchronous TimeAlarm command path is implemented upstream. The EC already supported all nine commands; the missing secure-world SetRealTime (3), ClearWakeStatus (5), and SetExpiredTimerPolicy (8) relay handlers landed in OpenDevicePartnership/odp-secure-services#101.
Qualification and contract work also landed:
The original peripheral-memory wording is superseded by the existing relay transport; the deprecated eSPI memory map was removed in #707 and must not be rebuilt.
Remaining concerns are separate: power-source integration and actual timer-triggered wake (#689), asynchronous relay notifications (#733), and any required ALERT/SCI/VWire handling (#160). Status-bit tests do not demonstrate physical wake. NEVER policy coverage proves setter acceptance and peer isolation, not independently distinguishable readback.
This comment reconciles delivered scope without closing this broader issue. Maintainers should confirm that the remaining notification/wake obligations are fully owned by the separate trackers before closing it.