You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
@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.
Uh oh!
There was an error while loading. Please reload this page.
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()
andTimer()
(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 theI2C()
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
The text was updated successfully, but these errors were encountered: