Introduction

Android supports its own Power Management (on top of the standard Linux Power Management) designed with the premise that the CPU shouldn't consume power if no applications or services require power. For more information regarding standard Linux power management, please see Linux Power Management Support at http://.

Android requires that applications and services request CPU resources with "wake locks" through the Android application framework and native Linux libraries. If there are no active wake locks, Android will shut down the CPU.

The image below illustrates the Android power management architecture.

Wake Locks

Wake locks are used by applications and services to request CPU resources.

A locked wakelock, depending on its type, prevents the system from entering suspend or other low-power states. This document describes how to employ wakelocks.

There are two settings for a wakelock:

• WAKE_LOCK_SUSPEND: prevents a full system suspend.
• WAKE_LOCK_IDLE: low-power states, which often cause large interrupt latencies or that disable a set of interrupts, will not be entered from idle until the wakelocks are released.

Unless the type is specified, this document refers to wakelocks of type WAKE_LOCK_SUSPEND.

If the suspend operation has already started when locking a wakelock, the system will abort the suspend operation as long it has not already reached the suspend_late stage. This means that locking a wakelock from an interrupt handler or a freezeable thread always works, but if you lock a wakelock from a suspend_late handler, you must also return an error from that handler to abort suspend. You can use wakelocks to allow the user-space to decide which keys should wake the full system and turn on the screen. Use set_irq_wake or a platform-specific API to ensure that the keypad interrupt wakes up the CPU. Once the keypad driver has resumed, the sequence of events can look like this:

1. The Keypad driver receives an interrupt, locks the keypad-scan wakelock, and starts scanning the keypad matrix.
2. The keypad-scan code detects a key change and reports it to the input-event driver.
3. The input-event driver sees the key change, enqueues an event, and locks the input-event-queue wakelock.
4. The keypad-scan code detects that no keys are held and unlocks the keypad-scan wakelock.
5. The user-space input-event thread returns from select/poll, locks the process-input-events wakelock, and calls read in the input-event device.
6. The input-event driver dequeues the key-event and, since the queue is now empty, unlocks the input-event-queue wakelock.
7. The user-space input-event thread returns from read. It determines that the key should not wake up the full system, releases the process-input-events wakelock, and calls select or poll.

The simple sequence diagram below illustrates these steps:

     					Key pressed      Key released
|		      |
keypad-scan       		     ++++++++++++++++++++++
input-event-queue 			  +++ 		  +++
process-input-events 		            +++ 	    +++

Driver API

A driver can use the wakelock API by adding a wakelock variable to its state and calling wake_lock_init, as illustrated in the snippet below:

  struct state {
struct wakelock wakelock;
}
init() {
wake_lock_init(&state->wakelock, WAKE_LOCK_SUSPEND, "wakelockname");
}
Before freeing the memory, wake_lock_destroy must be called:
uninit() {
wake_lock_destroy(&state->wakelock);
}

When the driver determines that it needs to run (usually in an interrupt handler), it calls wake_lock:

  wake_lock(&state->wakelock);

When it no longer needs to run, it calls wake_unlock:

  wake_unlock(&state->wakelock);

It can also call wake_lock_timeout to release the wakelock after a delay:

  wake_lock_timeout(&state->wakelock, HZ);

This works whether or not the wakelock is already held. It is useful if the driver woke up other parts of the system that do not use wakelocks but still need to run. Avoid this when possible, since it will waste power if the timeout is long or may fail to finish needed work if the timeout is short.

User-space API

Write lockname or lockname timeout to /sys/power/wake_lock lock and, if needed, create a wakelock. The timeout here is specified in nanoseconds. Write lockname to /sys/power/wake_unlock to unlock a user wakelock.

Do not use randomly generated wakelock names as there is no API to free a user-space wakelock.

Types of Wake Locks

Exploring a Wake Lock Example

All power management calls follow the same basic format:

1. Acquire handle to the PowerManager service.
2. Create a wake lock and specify the power management flags for screen, timeout, etc.
3. Acquire wake lock.
4. Perform operation (play MP3, open HTML page, etc.).
5. Release wake lock.

The snippet below illustrates this process.

PowerManager pm = (PowerManager)mContext.getSystemService(
Context.POWER_SERVICE);
PowerManager.WakeLock wl = pm.newWakeLock(
PowerManager.SCREEN_DIM_WAKE_LOCK
| PowerManager.ON_AFTER_RELEASE,
TAG);
wl.acquire();
// ...
wl.release();

PowerManager class

The Android Framework exposes power management to services and applications through the PowerManager class.

User space native libraries (any hardware function in //device/lib/hardware/ meant to serve as supporting libraries for Android runtime) should never call into Android Power Management directly (see the image above). Bypassing the power management policy in the Android runtime will destabilize the system.

All calls into Power Management should go through the Android runtime PowerManager APIs.

Please visit http://code.google.com/android/reference/android/os/PowerManager.html for a description of the API and examples.

Registering Drivers with the PM Driver

You can register Kernel-level drivers with the Android Power Manager driver so that they're notified immediately before power down or after power up. For example, you might set a display driver to completely power down when a request comes in to power down from the user space (see the Android MSM MDDI display driver for a sample implementation).

To register drivers with the Android PM driver, implement call-back handlers and register them with the Android PM, as illustrated in the snippet below:

android_register_early_suspend(android_early_suspend_t *handler)
android_register_early_resume(android_early_resume_t *handler)

It is critical in a drive to return immediately and not wait for anything to happen in the call back.

Early Suspend

The early-suspend API allows drivers to get notified when user-space writes to /sys/power/request_state to indicate that the user visible sleep state should change. Suspend handlers are called in order of low to high (4 - 1 below) and resume handlers are called in order of high to low (1 - 4 below).

1. EARLY_SUSPEND_LEVEL_BLANK_SCREEN:
• on suspend: the screen should be turned off but the framebuffer must still be accessible.
• on resume: the screen can be turned back on.
2. EARLY_SUSPEND_LEVEL_STOP_DRAWING:
   • on suspend: this level notifies user-space that it should stop accessing the framebuffer and it waits for it to complete.
   • on resume: it notifies user-space that it should resume screen access. Two methods are provided, console switch or a sysfs interface.
3. EARLY_SUSPEND_LEVEL_DISABLE_FB: Turn off the framebuffer
   • on suspend: turn off the framebuffer
   • on resume: turn the framebuffer back on.
4. EARLY_SUSPEND_LEVEL_STOP_INPUT:
   • on suspend: turn off input devices that are not capable of wakeup or where wakeup is disabled.
   • on resume: turn the same devices back on.