machine: compute rp2 clock dividers from crystal and target frequency #4747
+15
−3
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.
Follow-up to #4728 which implemented the algorithm for finding the dividers.
The calculation is computed at compile time by interp, as verified by the unchanging size for example/blinky1 for -target pico.
@soypat you mentioned that you couldn't get TinyGo to compute the dividers at compile time. However, this PR doesn't change the size of the blinky1 example for
-target pico1
. What did I miss?