Power Management Scenarios: Difference between revisions
RafaelOrtiz (talk | contribs) m (category) |
m (→System Idle: fix link) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
== |
== Ohm == |
||
Power management on the XO will be controlled by a special application |
Power management on the XO will be controlled by a special application, the Power Management Daemon. It is implemented in Ohm, the Open Hardware Manager daemon originally written for the OpenEmbedded project. Ohm is responsible for processing |
||
power events from both Sugar and the kernel and managing the system accordingly. |
power events from both Sugar and the kernel and managing the system accordingly. Ohm will use these scenarios to resist the useless consumption of power by the system. |
||
| Line 11: | Line 11: | ||
=== On Demand === |
=== On Demand === |
||
The XO enters STR on demand from some application or user input. This does not imply that the user will have a shiny button to press to enter the state, only that the state is not entered automatically by some hardware event or timer. Typically, |
The XO enters STR on demand from some application or user input. This does not imply that the user will have a shiny button to press to enter the state, only that the state is not entered automatically by some hardware event or timer. Typically, Ohm would be notified through DBUS to enter the sleep state. The appropriate wakeup events for this mode would be the Power button, RTC and EC - possibly configurable by the requesting application. Enabling LID events will not be complex, because Ohm can wake up on the LID down event, |
||
turn off the video display and do any other further power reduction, and go back into suspend. |
|||
=== Lid down/up === |
=== Lid down/up === |
||
The XO enters STR when the LID is closed, and resumed when the LID is opened. Upon detecting a lid down event, |
The XO enters STR when the LID is closed, and resumed when the LID is opened. Upon detecting a lid down event, Ohm enables the LID event as a wakeup event and enters the STR state through the /sys/power/state interface. LID up is configured to wake the system when the lid is lifted again. EC wakeups may be enabled to allow the system to process battery and WLAN events, but Ohm will realize that the LID is still down, and that it should process the event and go back to sleep again. Since this mode has the LID down, it is not necessary to keep the DCON alive or the backlight enabled. The DCON should be put into a sleep mode before suspending. |
||
=== System Idle === |
=== System Idle === |
||
The XO enters STR when it is believed that the system has nothing to do. The metric used for "nothing to do", as well as the idle time is |
The XO enters STR when it is believed that the system has nothing to do for some period of time, or until an event occurs (such as a keypress, USB insertion, AC on or off, or packet reception). The metric used for "nothing to do", as well as the idle time is determined by Ohm's heuristics. |
||
See also [[XO power draw]] |
|||
[[Category:Battery & Power]] |
[[Category:Battery & Power]] |
||
Latest revision as of 20:17, 12 September 2008
Ohm
Power management on the XO will be controlled by a special application, the Power Management Daemon. It is implemented in Ohm, the Open Hardware Manager daemon originally written for the OpenEmbedded project. Ohm is responsible for processing power events from both Sugar and the kernel and managing the system accordingly. Ohm will use these scenarios to resist the useless consumption of power by the system.
Suspend to RAM
The following are the scenarios we wish to support for Suspend to RAM (STR):
On Demand
The XO enters STR on demand from some application or user input. This does not imply that the user will have a shiny button to press to enter the state, only that the state is not entered automatically by some hardware event or timer. Typically, Ohm would be notified through DBUS to enter the sleep state. The appropriate wakeup events for this mode would be the Power button, RTC and EC - possibly configurable by the requesting application. Enabling LID events will not be complex, because Ohm can wake up on the LID down event, turn off the video display and do any other further power reduction, and go back into suspend.
Lid down/up
The XO enters STR when the LID is closed, and resumed when the LID is opened. Upon detecting a lid down event, Ohm enables the LID event as a wakeup event and enters the STR state through the /sys/power/state interface. LID up is configured to wake the system when the lid is lifted again. EC wakeups may be enabled to allow the system to process battery and WLAN events, but Ohm will realize that the LID is still down, and that it should process the event and go back to sleep again. Since this mode has the LID down, it is not necessary to keep the DCON alive or the backlight enabled. The DCON should be put into a sleep mode before suspending.
System Idle
The XO enters STR when it is believed that the system has nothing to do for some period of time, or until an event occurs (such as a keypress, USB insertion, AC on or off, or packet reception). The metric used for "nothing to do", as well as the idle time is determined by Ohm's heuristics.
See also XO power draw