diff options
author | Andrew Dodd <atd7@cornell.edu> | 2012-09-15 11:55:36 -0400 |
---|---|---|
committer | Gerrit Code Review <gerrit@review.cyanogenmod.com> | 2012-10-04 03:54:45 -0700 |
commit | 1579100c872e6b76f09bd8f79dd85faf6076e5d9 (patch) | |
tree | 0b2cc27accb0c0ab355f840e1c3a649348c99374 /configs | |
parent | 6f4d2ebc76f0c662815d5bfd7116f0d7e66fc1e2 (diff) | |
download | device_samsung_galaxys2-common-1579100c872e6b76f09bd8f79dd85faf6076e5d9.zip device_samsung_galaxys2-common-1579100c872e6b76f09bd8f79dd85faf6076e5d9.tar.gz device_samsung_galaxys2-common-1579100c872e6b76f09bd8f79dd85faf6076e5d9.tar.bz2 |
power_profile: Add cpu.awake parameter
One of the remaining issues with the new profile is lack
of a cpu.awake parameter - without this, wakelock holders
won't be penalized in battery stats.
Make a wild-ass guesstimate of 15 mA, based on:
Best-case consumption is around 0.5%/hour with radio on, assume
8.25 mA consumption of non-CPU stuff in deep sleep.
Best case consumption when wakelocked is usually around 1.25-1.5%/hour,
assume then, about 25 mA total when wakelocked.
Subtract the baseline and it's 15-16 mA. Let's just round to a
multiple of 5 here, since it IS a WAG.
Also, consumption when the CPU is running at 200 MHz (for example,
governor set to ignore nice load, and a program is endlessly looping
but niced to avoid bumping the gov) is usually around 4-5%/hour,
which is semi-consistent with a number of 55 mA for 200 MHz op.
Change-Id: I6aa08842dd2acfced0c70a95d973aa0b415799cc
Diffstat (limited to 'configs')
0 files changed, 0 insertions, 0 deletions