| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
This reverts commit f30d43663f07544eb836d0502a5c492895b87324.
This is not working with the 4.2 code base.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
-read value of both scaling_max_freq and screen_off_max_freq from sysfs
(previously, power_hal only did the former)
-if scaling_max_freq is larger than screen_off_max_freq, then save it into our scaling_max_freq variable,
because it is truly the scaling_max_freq
otherwise, the scaling_max_freq sysfs path has had screen_off_max_freq written to it,
so we don't save it to scaling_max_freq.
-write the appropriate value (screen_off_max if screen is off, etc.) to scaling_max_freq sysfs path
Change-Id: I10cd571df61a5d583dd73be0cb6c7c2201477a96
Signed-off-by: nuclearmistake <nuclearmistake@gmail.com>
|
|
|
|
|
|
| |
Code copied from Steve Kondik's commit.
Change-Id: I7576534132940ef0820af91f2d314055fbd84411
|
|
|
|
|
|
|
| |
Review general code
removed non sense comparation "on ?" since is extra
Change-Id: I285368dbb449e4234e9cea8846c087fc4f3200f3
|
|
|
|
|
|
|
| |
This fixes issues when pressing the power button repeatedly in a short
period of time. The "on" call might not run, and when we re-read the
value on screen off to store it, we will be actually reading the capped
screen off value. Make sure that's not the case.
|
|
|
|
| |
Change-Id: I7fc7c517e04eee3933ab7107e788b50e41270b67
|
|
|
|
|
|
| |
And no longer request in-kernel touchscreen boost.
Change-Id: I0d276c5188a7c7b9fb0c3c445b4e1229d26b15a5
|
|
|
|
|
|
|
| |
PowerManagerService will trigger suspend after calling into the
power hal, remove it from here.
Change-Id: I9c6bc42f8615d047000295fb8b100e32c4e46318
|
|
|
|
| |
Change-Id: I018bad401fcc72025d1c3997224eecc54da8ee92
|
|
|
|
| |
Change-Id: I8d296e36222a45599edf7d3cab48a9aa8aae7bd7
|
|
|
|
| |
Change-Id: Icb36ec7fa3057978c7075ddb4e961c1ef403e7f4
|
|
|
|
| |
Change-Id: Ibea0084f48ce0cbea50fb151ade0785822f7222e
|
|
|
|
|
| |
Change-Id: I3a0c72e843c4d9c7a9129a35ed8bbee59acb5599
Signed-off-by: Todd Poynor <toddpoynor@google.com>
|
|
|
|
|
|
|
| |
Require a sustained high CPU load before moving to 920MHz/1.2GHz.
Change-Id: I0eca4bf3c0104bd89c300bb8f28da2f31f479d12
Signed-off-by: Todd Poynor <toddpoynor@google.com>
|
|
* Add Power HAL for Tuna.
* Update cpufreq interactive governor params:
min_sample_time = 100ms to cover bursts of graphics load
go_hispeed_load = 40% to handle graphics loads
* Move screen off maximum frequency to generic cpufreq
scaling_max_freq interface, set when turning screen on/off.
* Move cpufreq init from init.rc to Power HAL.
Change-Id: I12efd9b5fbfe89a487fac926b42ce1fe65980f7a
|