Skip to content

Drivers don't tidy up HW afterwards #8098

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

Closed
RobMeades opened this issue Sep 12, 2018 · 4 comments
Closed

Drivers don't tidy up HW afterwards #8098

RobMeades opened this issue Sep 12, 2018 · 4 comments

Comments

@RobMeades
Copy link
Contributor

RobMeades commented Sep 12, 2018

Description

I guess you're aware of this but several of the mbed drivers don't tidy up the HW when they have been deleted: Serial(), I2C() and Timer() (see #7847) are the examples I know of. There are hints (e.g. in serial_api.h) that this is intended but it is not implemented or, in the I2C() case, not even hinted at.

This means that those HW blocks continue to run and suck power, which is not ideal for low power applications.

Is there a plan/schedule to resolve this in a future mbed-os release?

Issue request type

[x] Question
[ ] Enhancement
[ ] Bug

@ciarmcom
Copy link
Member

ARM Internal Ref: MBOTRIAGE-1642

@deepikabhavnani
Copy link

@RobMeades - Thanks for reporting the issue, mbed-os HAL team is aware of this, and working on this with each HAL+driver API updates.
Since deletion/cleanup of HW needs to be implemented for each and every target it will be bit slow.

Related to #3106.

@deepikabhavnani
Copy link

Closing this. Follow #3106 for tracking.

@RobMeades
Copy link
Contributor Author

Understood, thanks.

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

No branches or pull requests

3 participants