Mobile Power Management

Registered by Leann Ogasawara on 2013-03-28

Start examining our approach to power management in the mobile space.

Abbreviations:
  PE = product engineering
  UDS = unity & display server

* Overall PM
  * Lead: ogasawara
  * Stakeholders: kernel, foundations, desktop, PE, UDS, QA, security?

* System PM policy definition and implementation
  * Description: Define and implement the policy for the system power
    states. Examples: suspend/resume, psuedo-suspend (screen off but system
    still active), system shutdown, perhaps things like airplane mode.
  * Lead: lool
  * Stakeholders: kernel, foundations, desktop, PE, UDS, security?,

* Application lifecycle/APIs
  * Description: Define and implement aspects of application lifecycles
    and APIS related to PM. Examples: app- versus system-centric PM
    approach, background tasks, timers.
  * Lead: tvoss
  * Stakeholders: desktop, PE, UDS, security?

* Hardware PM
  * Description: Define policies around PM for hardware, including the
    CPU, devices (both on- and off-chip), thermal management, etc. Work
    with other teams on defining and implementing interfaces for
    managing device power states (HAL?).
  * Lead: sforshee
  * Stakeholders: kernel, foundations?, desktop?, PE?

* System power benchmarking and testing
  * Description: Identify use cases and metrics useful for measuring
    power use. Estabilsh baseline PM measurement for nexus devices
    running android for use as a reference. Define and implement test
    plan for power.
  * Lead: plars
  * Stakeholders: Everyone

* Application power benchmarking and QA
  * Description: Identify metrics useful for evaluating applications wrt
    power consumption. Identify and develop tools for use by application
    developers (and community?) for evaluating application power
    behavior.
  * Lead: tvoss (to be eventually handed off)
  * Stakeholders: QA, PE?, UDS?, desktop?

Blueprint information

Status:
Started
Approver:
Leann Ogasawara
Priority:
High
Drafter:
Leann Ogasawara
Direction:
Approved
Assignee:
Leann Ogasawara
Definition:
Approved
Series goal:
Accepted for saucy
Implementation:
Started
Milestone target:
milestone icon ubuntu-13.10
Started by
Leann Ogasawara on 2013-03-28

Related branches

Sprints

Whiteboard

Discussions across teams in Canonical are currently underway to breakdown areas of ownership for the items called out in the blueprint description.

== Notes from 2013-04-02 meeting ==

Initial ownership assignments:
* Overall PM: ogasawara
* System PM policy: lool
* App lifecycle and APIs: tvoss
* Hardware PM: sforshee
* System power benchmarking and testing: plars
* Application power benchmarking and QA: tvoss

lool to schedule public meeting to discuss overall system PM architecture. Prior to this meeting various internal research documents which are currently only accessible to Canonical staff should be made public.

There was a discussion around whether to adopt a system-centric or application-centric approach to PM policy. General consensus among the attendees was towards a system-centric approach. Most of the concerns voiced about the system-centric policy were related to how policy will be enforced.

(?)

Work Items

Work items for ubuntu-13.04-month-6:
[leannogasawara] Gather current status for work being done in mobile power management space wrt Canonical teams: DONE
[sforshee] Breakdown areas of ownership for mobile power management: DONE
[leannogasawara] Update PRD line items to properly reflect body of work: DONE
[sforshee] Draft strawman to meet mobile power management goals for 13.10: DONE
[leannogasawara] Create blueprints for PM subtopics: DONE

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.