OpenDevicePartnership / OpenDevicePartnership/embassy-imxrt
Enable multiple RTC time alarms to addresses set_alarm unsound potential
@jerrysxie is already working on this.
Since Mar 15, 2026.
- Dominant language
- Rust
- Stars
- 23
- Forks
- 38
- PR merge metrics
- No merged PRs in 30d
Description
Setting an RTC time alarm as it stands in https://github.com/OpenDevicePartnership/embassy-imxrt/pull/542 has no inherent guards about setting an alarm while another one is active. This could cause unwanted behavior depending on the user implementation, either where some futures will never complete, or an alarm goes off while trying to set a different one.
Allowing for multiple alarms could resolve these issues and expand to allow users multiple locations to await an RTC alarm, just as they can with a time alarm via the Timer.
https://github.com/OpenDevicePartnership/embassy-imxrt/pull/542#discussion_r2694746937
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.