Skip to content

clarify clock_configure and make it return the correct value achieved for bad clock inputs #2225

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 4, 2025

Conversation

kilograham
Copy link
Contributor

fixes #2189

@kilograham kilograham added this to the 2.1.1 milestone Feb 2, 2025
@kilograham kilograham merged commit 0d90992 into develop Feb 4, 2025
8 checks passed
@kilograham kilograham deleted the clock_divider branch February 4, 2025 17:17
@@ -287,7 +294,7 @@ bool clock_configure(clock_handle_t clock, uint32_t src, uint32_t auxsrc, uint32
*/
void clock_configure_undivided(clock_handle_t clock, uint32_t src, uint32_t auxsrc, uint32_t src_freq);

/*! \brief Configure the specified clock to use the undividded input source
/*! \brief Configure the specified clock to use the undivided input source
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmmm, same 'brief' description for both clock_configure_undivided and clock_configure_int_divider - is that correct, or was it a copy'n'paste error?

@kilograham
Copy link
Contributor Author

Actually it turns out the RP2350 datasheet is incorrect and 1.x IS supported on RP2350… the datasheet will be updated and I’ll make a new PR to correct the function documentation

will-v-pi pushed a commit to will-v-pi/pico-sdk that referenced this pull request Mar 20, 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