RtcBuilder for Rtc easy initialization and access #362
Conversation
This file contains 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
…er functions and one fixed
|
Not sure if I can do anything to fix this checks |
|
@Sh3Rm4n Hi, why do we use chrono 0.4.34, it is for rustc 1.61 we should use chrono 0.4.31. Do you want me to fix it by this PR? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added a builder that facilitates the initialization of RTC with various clock sources (LSE or LSI, HSE in future). The intent of the update is to easy access to other clock sources without the need for detailed knowledge of this modules configuration while still offering the ability to modify default settings. The solution does not affect the existing setup so as not to force current users to update their existing code. Easy to expand.