samd51 adc: init defines generic clock so adc0 and adc1 can be used at the same time #113
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.
samd51 adc was hardcoding a single clock and crashing when both adc0 and adc1 were initialized at same time.
Moves clock selection to the adc init function instead. But this isnt very typestatey or safe and just moves the problem upstream. Perhaps we need a clock tree function call to replace configure_gclk_divider_and_source to hand out generic clocks so users or subsystems cant reuse.