Skip to content

Conversation

rnd-ash
Copy link
Contributor

@rnd-ash rnd-ash commented Jul 28, 2025

Summary

Reverts the changes done in #919, whilst also ensuring that the provided GCLK is EnabledGclk0, rather than potentially any GCLK source like it was prior. The way GCLK0 is provided is the same as in the QSPI rework PR (#926), since both peripherals require proof of GCLK0, so both peripherals should have a consistent way of doing this.

@glaeqen would I be able to ask for your input on this?

@glaeqen
Copy link
Contributor

glaeqen commented Jul 28, 2025

Looks fine to me. One could bikeshed that the order of elements in the tuple does not match the one from before the revert but types have changed anyway so probably it is not the big deal.

@ianrrees
Copy link
Contributor

@rnd-ash - gentle reminder that we need to use conventional commits. I believe we'll also need to manually mark this as a breaking change, since it doesn't seem to detect those in feature-gated APIs.

@ianrrees ianrrees merged commit 9719649 into atsamd-rs:master Jul 28, 2025
109 checks passed
@github-actions github-actions bot mentioned this pull request Jul 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants