PWM: Set TOP to 0xfffe by default and fix get_max_duty #744
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
A TOP value of 0xffff is incompatible with true 100% duty cycle. Therefore, the default TOP value is reduced to 0xfffe, and a warning regarding the 0xffff value is added the documentation of `set_top`. The value returned by get_max_duty is corrected to be TOP + 1, if possible.
thejpster
approved these changes
Dec 27, 2023
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.
A TOP value of 0xffff is incompatible with true 100% duty cycle. Therefore, the default TOP value is reduced to 0xfffe, and a warning regarding the 0xffff value is added the documentation of
set_top.The value returned by get_max_duty is corrected to be TOP + 1, if possible.
Closes #735