Skip to content

PwmOut Destructor doesn't call pwmout_free() #5442

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.

Sign up for GitHub

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

Jump to bottom
Closed
MikeDK opened this issue Nov 7, 2017 · 1 comment
Closed

PwmOut Destructor doesn't call pwmout_free() #5442

MikeDK opened this issue Nov 7, 2017 · 1 comment

Comments

@MikeDK
Copy link
Contributor

MikeDK commented Nov 7, 2017

Description

  • Type: Bug
  • Priority: Major

Bug

Expected behavior
In PwmOut Constructor, pwmout_init() is called, so I guess there should be a call to pwmout_free() within the PwmOut Destructor.

Actual behavior
pwmout_free() is not called. So a pin stays initialized, when a PwmOut object is destroyed.
Depending on the target's implementation, this could lead to sleep modes not unblocked, timers not uninitialized, etc...
@0xc0170
Copy link
Contributor

0xc0170 commented Nov 7, 2017

Please see #3106 (capturing all drivers), this will be addressed.

I'll close this as duplicate.

@0xc0170 0xc0170 closed this as completed Nov 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MikeDK @0xc0170