Repository navigation
Define a generic RTC device ioctl contract - #29
Merged
Merged
Conversation
This was referenced Oct 16, 2026
Merged
JohnAmadis
approved these changes
Oct 16, 2026
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.
RTC clients need a shared device contract to work with MCU calendars, external RTC chips and virtual clocks. Add
DMDRVI_IOCTL_RTC_{GET_TIME,SET_TIME,GET_STATUS,GET_INFO,INVALIDATE}in the 0x600 category, fixed-width calendar/status/info structures, optional write/invalidate/loss-detection capabilities, and precise error/access semantics. The calendar carries no implicit timezone or authenticated UTC policy; that belongs to dmutc.GET_INFO exposes supported years and granularity. Unsupported precision is rejected without truncation, unset/lost calendars return ENODATA, and loss continuity is only meaningful when advertised. ABI layout/category assertions and collision coverage include the new commands. The DMR packages the public headers, generated definitions and itself; the diagnostic has its own resource manifest.
Validation: native diagnostic 6/6; Cortex-M4/M7 builds with the architecture tools-cfg.cmake supplied as CMAKE_TOOLCHAIN_FILE; STM32F746G-DISCO diagnostic 6/6, RTC integration 11/11 and RNG regression 6/6. Hardware evidence: https://github.com/choco-technologies/dmrtc/blob/feat/stm32-rtc/docs/validation/rtc-device-contract-2026-10-16.txt
Consumer: choco-technologies/dmrtc#1. Merge and release this interface before rebuilding that consumer against the public registry. Validation used local unreleased headers, with no dependency pins added to consumer source.