platform: scheduler: zephyr: fix issue while reconfiguring timer period #110
Conversation
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
1 participant
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.
The purpose of this Pull-Request is to fix an issue while changing timer period on Zephyr targets.
The
k_timer_startfunction allows to change theperiodof the timer even if it is already running. However, this is not possible if thedurationis K_FOREVER (not mentioned in Zephyr doc, only in the code).As a consequence the updates were checked with period
CONFIG_MENDER_CLIENT_AUTHENTICATION_POLL_INTERVALinstead ofCONFIG_MENDER_CLIENT_UPDATE_POLL_INTERVAL.