Skip to content
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

Motors: unify types for PWM to be uint16_t #1380

Merged
merged 2 commits into from
Oct 7, 2024

Conversation

whoenig
Copy link
Contributor

@whoenig whoenig commented May 29, 2024

This uses the uint16_t type more consistently. For uSD logging this will reduce the memory needed. For CRTP logging it should not have any impact, since the user-code requests the logging variables with a desired type. Thus, "legacy" code might request the logging variable as uint32_t and it will be converted accordingly.

@tobbeanton
Copy link
Member

I'm trying to figure out if they where assigned uin32 in the first place. Looks like they originate from a pull-request and perhaps there is no real reason they are not uint16. For me it makes most sense to have them as uint16 so I'm approving the pull-request. Any other opinions?

@tobbeanton tobbeanton self-requested a review May 31, 2024 08:11
@ataffanel
Copy link
Member

We have looked at it and it is a good change, no idea why it became 32 bits and it should not break anything to change it back to 16 bit. Thanks!

@ataffanel ataffanel merged commit 0eda02a into bitcraze:master Oct 7, 2024
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants