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

Add shutdown mode to sleep api #6081

Closed
ivanccu opened this issue Feb 13, 2018 · 5 comments
Closed

Add shutdown mode to sleep api #6081

ivanccu opened this issue Feb 13, 2018 · 5 comments

Comments

@ivanccu
Copy link

ivanccu commented Feb 13, 2018

Description

  • Type: Enhancement
  • Related issue: Shutdown api
  • Priority: Major

Enhancement

Reason to enhance or problem with existing solution
Currently it is starting to work in the industrial sector with the internet of things.
One of the characteristics of IoT is the low consumption. To achieve this low consumption, manufacturers already have microcontrollers such as the STM32L4 capable of entering ultra-low consumption mode (shutdown), sacrificing information not stored in memory.
This utility is very useful at the moment but, in spite of the fact that in this case ST has implemented this functionality for its microcontroller, this function does not exist in the mbed library.
With the current library (sleep) you can only reach two operating modes (sleep and deepsleep) that have higher consumption than shutdown.
Therefore if you need to use the shutdown function in your project you need to go down to the HAL level and try to do it on your own. Possibly resulting errors since going down to the HAL layer implies losing the thread safety

Suggested enhancement
Add shutdown mode to de mbed library

Pros
-more easy to use for the user
-mbed will be more itnerested for the market, specially on Iot devices

Cons
-invalid function for some microcontrollers

@LMESTM
Copy link
Contributor

LMESTM commented Feb 13, 2018

Please consider adding RTC::alarm service together with shutdown
[Mirrored to Jira]

@adbridge
Copy link
Contributor

adbridge commented Oct 4, 2018

Internal Jira reference: https://jira.arm.com/browse/IOTHAL-83

@jeromecoutant
Copy link
Collaborator

Hi
Why there is no explanation for issue closing ?
Thx

@0xc0170
Copy link
Contributor

0xc0170 commented Dec 20, 2018

This is being tracked internally via another ticket. Thus this was closed and original kept (it's not on Github as an issue).

@donatieng can correct me.

@cmonr
Copy link
Contributor

cmonr commented Dec 20, 2018

Either way, if an issue was closed because it was duplicated, a message indicating what it's a duplicate of should be provided.

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

7 participants