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.
Summary
Prior pull request #9084 and issue #8858 added basic adjtime() support for the SAMv7 platform.
This pull request adds support for STM32 platform.
In addition I have made a few changes to the adjtime() configuration options:
Impact
Users who have used
CLOCK_ADJTIME_PERIOD
andCLOCK_ADJTIME_SLEWLIMIT
settings should update their configuration. NewCLOCK_ADJTIME_PERIOD_MS
is 10x the old period value, and newCLOCK_ADJTIME_SLEWLIMIT_PPM
is 10000 times the old slewlimit.Testing
Tested on custom STM32 board with the
adjtime
example program.Questions
@michallenc I couldn't find the significance of the
Should be between 0.95 and 0.99.
comment that was previously in help text forCLOCK_ADJTIME_PERIOD
. To me it appears that the desirable value for this setting will depend entirely on what code will be callingadjtime()
and how often.