summaryrefslogtreecommitdiffstats
path: root/services/powermanager
diff options
context:
space:
mode:
authorPrashant Malani <pmalani@google.com>2014-05-25 01:36:31 -0700
committerPrashant Malani <pmalani@google.com>2014-06-05 16:35:52 -0700
commit2c9b11f0291210c9b9513a1a0cce6afebd361b3b (patch)
tree47ba276853c591e558553ee5e0eefabbc7db4625 /services/powermanager
parentedcf7f4d3ac452500d68e254d367f559d538695d (diff)
downloadframeworks_native-2c9b11f0291210c9b9513a1a0cce6afebd361b3b.zip
frameworks_native-2c9b11f0291210c9b9513a1a0cce6afebd361b3b.tar.gz
frameworks_native-2c9b11f0291210c9b9513a1a0cce6afebd361b3b.tar.bz2
surfaceflinger: Replace blank/unblank with setPowerMode
We replace the blank/unblank calls in surfaceFlinger with a more generic setPowerMode() routine. Some displays support different power modes (for example, with reduced color palettes). Depending on the use case we should be able to toggle these modes, so as to achieve incremental power savings. Initially, three power modes will be supported: - HWC_POWER_MODE_OFF - HWC_POWER_MODE_DOZE - HWC_POWER_MODE_NORMAL HWC_POWER_MODE_OFF will correspond to blanking the display, while HWC_POWER_MODE_NORMAL will correspond to unblanking. HWC_POWER_MODE_DOZE will put the display into a low power setting, if it is supported in hardware. If such a low power mode is not supported, it should be treated as a call to set the mode to HWC_POWER_MODE_NORMAL. As a consequence of adding the mPowerMode field, the mScreenAcquired is no longer required, and thus references to it are removed and replaced equivalent references to mPowerMode. We also add the glue code to connect the services invocation of setting a power mode and the HAL implementation in HWComposer. Bug: 13472578 Change-Id: I431595ecf16d2f2c94259272db3dd42f29636204 Signed-off-by: Prashant Malani <pmalani@google.com>
Diffstat (limited to 'services/powermanager')
0 files changed, 0 insertions, 0 deletions