Repository navigation
Implement RTC driver with generic dmdrvi contract and STM32F4/F7 ports - #1
Merged
Merged
Conversation
This was referenced Oct 15, 2026
JaxCalder
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implement dmrtc with a dmdrvi device interface, portable calendar core and STM32F4/F7 ports sharing stm32_common. Board/MCU INI configuration selects LSE/LSI and startup deadline. RCC IRQ plus an ISR-safe semaphore handles oscillator startup; register waits sleep with bounded deadlines. Device initialization requires the scheduler and the accompanying boot worker change.
Public RTC ioctl commands and calendar/capability/status structures come from dmdrvi. The generic rtc CLI opens a configurable VFS device and has no dmrtc API dependency. Supported precision/range, unset state, permissions and optional loss detection have defined behavior; STM32 does not claim detected continuity or trusted UTC. No private ioctl aliases or manually pinned dependencies remain.
Validation: native ctest 3/3 targets (driver 12/12, actual STM32 wait source, generic client against an independent subsecond/read-only RTC); STM32F4/F7 builds; STM32F746G-DISCO RTC 11/11, dmdrvi 6/6, RNG 6/6. Warm-reset retention and actual LSE IRQ wake were checked separately. The latest console transcript and package hashes are in docs/testing.md and docs/validation/rtc-device-contract-2026-10-16.txt. VBAT is tied to VDD, so power-loss retention is not claimed.
Merge/release dependencies first:
Validation used local unreleased packages, without changing production dependency resolution. Registration: choco-technologies/dmod-registry#16; ecosystem: choco-technologies/dmod-ecosystem#30.
Current remote CI fails on missing dmdrvi_rtc_* types/commands because the public registry still supplies the interface before this contract. After the dmdrvi release, rerun the consumer workflow; local native and board validation used the new interface.