Skip to content

F7/tim: access to bits() without unsafe for single-field registers #700

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
Jul 3, 2022

Conversation

maximeborges
Copy link
Member

When writing to CNT/ARR/CCR%s single-field registers via bits(), it requires the use of unsafe for timers 9 to 14.
This PR allows to use safe bits() writing just like the other timers

@github-actions
Copy link

Memory map comparison

@adamgreig
Copy link
Member

Any reason to close this? Is it already in another PR?

@maximeborges
Copy link
Member Author

I was sure I did a mistake since I forgot to cleanup some code that was using it in the F7 HAL, but it actually looks fine so I'll reopen it

@maximeborges maximeborges reopened this Feb 10, 2022
@maximeborges maximeborges changed the title f7/tim: access to bits() without unsafe for single-field registers F7/tim: access to bits() without unsafe for single-field registers Feb 10, 2022
@newAM newAM added the stm32f7 label Feb 10, 2022
Copy link
Member

@adamgreig adamgreig left a comment

Choose a reason for hiding this comment

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

Makes sense, thanks!

bors r+

@bors bors bot merged commit fa72d11 into stm32-rs:master Jul 3, 2022
@bors
Copy link
Contributor

bors bot commented Jul 3, 2022

Build succeeded:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy