android_device_samsung_msm8.../power/power.c

275 lines
8.1 KiB
C
Raw Normal View History

Custom PowerHAL implementation PowerHAL highlights: * The CPU governor is always interactive. Governor changes are not expected and permissions are set once on boot. * Powersave profile: the CPU frequency is limited 787MHz and the CPU is never boosted on user interaction. This will save power without making the phone unbearably slow. * Performance profile: the CPU is constantly boosted. * Balanced profile: the CPU is boosted on user interaction. When the screen is turned off, the governor is tuned to lower the power consumption to save power in case of long lasting screen off activities such as music playback. * Currently there are no restrictions on the number of active cores. With this PowerHAL cpu-boost is not needed, so keep it disabled. In addition to that, drop all the properties based profiles and set config_perf_profile_prop to "powerhal" to make the framework send hints to PowerHAL when the power profile is changed. msm8226-common: PowerHAL: Initialize mutex Since the mutex is declared as static, this went unnoticed, but mutexes should always be initialized, so do it. msm8226-common: PowerHAL: Don't override user selected profiles Save and restore the last selected profile so that the user preference is not lost when transitioning out the low power mode. Also, don't actually change the profile if in low power mode, but don't discard the user preference. msm8226-common: Refactor PowerHAL Make the HAL generic by keeping the device dependent configuration separate. This allows to easily add or edit the profiles. The HAL should behave exactly as before, except for the fact that now there might be some useless writes when the screen is turned off. Change-Id: I6bb01a14f0058c59986989568e7766f4203150cc
2015-12-05 05:55:29 +00:00
/*
2018-05-24 19:43:45 +00:00
* Copyright (C) 2016 The CyanogenMod Project
Custom PowerHAL implementation PowerHAL highlights: * The CPU governor is always interactive. Governor changes are not expected and permissions are set once on boot. * Powersave profile: the CPU frequency is limited 787MHz and the CPU is never boosted on user interaction. This will save power without making the phone unbearably slow. * Performance profile: the CPU is constantly boosted. * Balanced profile: the CPU is boosted on user interaction. When the screen is turned off, the governor is tuned to lower the power consumption to save power in case of long lasting screen off activities such as music playback. * Currently there are no restrictions on the number of active cores. With this PowerHAL cpu-boost is not needed, so keep it disabled. In addition to that, drop all the properties based profiles and set config_perf_profile_prop to "powerhal" to make the framework send hints to PowerHAL when the power profile is changed. msm8226-common: PowerHAL: Initialize mutex Since the mutex is declared as static, this went unnoticed, but mutexes should always be initialized, so do it. msm8226-common: PowerHAL: Don't override user selected profiles Save and restore the last selected profile so that the user preference is not lost when transitioning out the low power mode. Also, don't actually change the profile if in low power mode, but don't discard the user preference. msm8226-common: Refactor PowerHAL Make the HAL generic by keeping the device dependent configuration separate. This allows to easily add or edit the profiles. The HAL should behave exactly as before, except for the fact that now there might be some useless writes when the screen is turned off. Change-Id: I6bb01a14f0058c59986989568e7766f4203150cc
2015-12-05 05:55:29 +00:00
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
#define LOG_TAG "PowerHAL"
#include <hardware/hardware.h>
#include <hardware/power.h>
#include <errno.h>
#include <fcntl.h>
#include <string.h>
2018-05-24 19:43:45 +00:00
#include <stdlib.h>
Custom PowerHAL implementation PowerHAL highlights: * The CPU governor is always interactive. Governor changes are not expected and permissions are set once on boot. * Powersave profile: the CPU frequency is limited 787MHz and the CPU is never boosted on user interaction. This will save power without making the phone unbearably slow. * Performance profile: the CPU is constantly boosted. * Balanced profile: the CPU is boosted on user interaction. When the screen is turned off, the governor is tuned to lower the power consumption to save power in case of long lasting screen off activities such as music playback. * Currently there are no restrictions on the number of active cores. With this PowerHAL cpu-boost is not needed, so keep it disabled. In addition to that, drop all the properties based profiles and set config_perf_profile_prop to "powerhal" to make the framework send hints to PowerHAL when the power profile is changed. msm8226-common: PowerHAL: Initialize mutex Since the mutex is declared as static, this went unnoticed, but mutexes should always be initialized, so do it. msm8226-common: PowerHAL: Don't override user selected profiles Save and restore the last selected profile so that the user preference is not lost when transitioning out the low power mode. Also, don't actually change the profile if in low power mode, but don't discard the user preference. msm8226-common: Refactor PowerHAL Make the HAL generic by keeping the device dependent configuration separate. This allows to easily add or edit the profiles. The HAL should behave exactly as before, except for the fact that now there might be some useless writes when the screen is turned off. Change-Id: I6bb01a14f0058c59986989568e7766f4203150cc
2015-12-05 05:55:29 +00:00
#include <utils/Log.h>
#include "power.h"
2018-05-24 19:43:45 +00:00
#define CPUFREQ_PATH "/sys/devices/system/cpu/cpu0/cpufreq/"
#define INTERACTIVE_PATH "/sys/devices/system/cpu/cpufreq/interactive/"
Custom PowerHAL implementation PowerHAL highlights: * The CPU governor is always interactive. Governor changes are not expected and permissions are set once on boot. * Powersave profile: the CPU frequency is limited 787MHz and the CPU is never boosted on user interaction. This will save power without making the phone unbearably slow. * Performance profile: the CPU is constantly boosted. * Balanced profile: the CPU is boosted on user interaction. When the screen is turned off, the governor is tuned to lower the power consumption to save power in case of long lasting screen off activities such as music playback. * Currently there are no restrictions on the number of active cores. With this PowerHAL cpu-boost is not needed, so keep it disabled. In addition to that, drop all the properties based profiles and set config_perf_profile_prop to "powerhal" to make the framework send hints to PowerHAL when the power profile is changed. msm8226-common: PowerHAL: Initialize mutex Since the mutex is declared as static, this went unnoticed, but mutexes should always be initialized, so do it. msm8226-common: PowerHAL: Don't override user selected profiles Save and restore the last selected profile so that the user preference is not lost when transitioning out the low power mode. Also, don't actually change the profile if in low power mode, but don't discard the user preference. msm8226-common: Refactor PowerHAL Make the HAL generic by keeping the device dependent configuration separate. This allows to easily add or edit the profiles. The HAL should behave exactly as before, except for the fact that now there might be some useless writes when the screen is turned off. Change-Id: I6bb01a14f0058c59986989568e7766f4203150cc
2015-12-05 05:55:29 +00:00
/* touchkeys */
#define TK_POWER "/sys/class/input/input1/enabled"
/* touchscreen */
#define TS_POWER "/sys/class/input/input2/enabled"
static pthread_mutex_t lock = PTHREAD_MUTEX_INITIALIZER;
static int boostpulse_fd = -1;
static int current_power_profile = -1;
static int requested_power_profile = -1;
static int sysfs_write_str(char *path, char *s)
{
char buf[80];
int len;
int ret = 0;
int fd;
fd = open(path, O_WRONLY);
if (fd < 0) {
strerror_r(errno, buf, sizeof(buf));
ALOGE("Error opening %s: %s\n", path, buf);
return -1 ;
}
len = write(fd, s, strlen(s));
if (len < 0) {
strerror_r(errno, buf, sizeof(buf));
ALOGE("Error writing to %s: %s\n", path, buf);
ret = -1;
}
close(fd);
return ret;
}
static int sysfs_write_int(char *path, int value)
{
char buf[80];
snprintf(buf, 80, "%d", value);
return sysfs_write_str(path, buf);
}
static int is_profile_valid(int profile)
{
return profile >= 0 && profile < PROFILE_MAX;
}
static void power_init(__attribute__((unused)) struct power_module *module)
{
ALOGI("%s", __func__);
}
static int boostpulse_open()
{
pthread_mutex_lock(&lock);
if (boostpulse_fd < 0) {
boostpulse_fd = open(INTERACTIVE_PATH "boostpulse", O_WRONLY);
}
pthread_mutex_unlock(&lock);
return boostpulse_fd;
}
static void power_set_interactive_ext(int on) {
ALOGD("%s: %s input devices", __func__, on ? "enabling" : "disabling");
sysfs_write_str(TK_POWER, on ? "1" : "0");
sysfs_write_str(TS_POWER, on ? "1" : "0");
Custom PowerHAL implementation PowerHAL highlights: * The CPU governor is always interactive. Governor changes are not expected and permissions are set once on boot. * Powersave profile: the CPU frequency is limited 787MHz and the CPU is never boosted on user interaction. This will save power without making the phone unbearably slow. * Performance profile: the CPU is constantly boosted. * Balanced profile: the CPU is boosted on user interaction. When the screen is turned off, the governor is tuned to lower the power consumption to save power in case of long lasting screen off activities such as music playback. * Currently there are no restrictions on the number of active cores. With this PowerHAL cpu-boost is not needed, so keep it disabled. In addition to that, drop all the properties based profiles and set config_perf_profile_prop to "powerhal" to make the framework send hints to PowerHAL when the power profile is changed. msm8226-common: PowerHAL: Initialize mutex Since the mutex is declared as static, this went unnoticed, but mutexes should always be initialized, so do it. msm8226-common: PowerHAL: Don't override user selected profiles Save and restore the last selected profile so that the user preference is not lost when transitioning out the low power mode. Also, don't actually change the profile if in low power mode, but don't discard the user preference. msm8226-common: Refactor PowerHAL Make the HAL generic by keeping the device dependent configuration separate. This allows to easily add or edit the profiles. The HAL should behave exactly as before, except for the fact that now there might be some useless writes when the screen is turned off. Change-Id: I6bb01a14f0058c59986989568e7766f4203150cc
2015-12-05 05:55:29 +00:00
}
static void power_set_interactive(__attribute__((unused)) struct power_module *module, int on)
{
if (!is_profile_valid(current_power_profile)) {
ALOGD("%s: no power profile selected yet", __func__);
return;
}
power_set_interactive_ext(on);
if (on) {
sysfs_write_int(INTERACTIVE_PATH "hispeed_freq",
profiles[current_power_profile].hispeed_freq);
sysfs_write_int(INTERACTIVE_PATH "go_hispeed_load",
profiles[current_power_profile].go_hispeed_load);
2018-05-24 19:43:45 +00:00
sysfs_write_int(INTERACTIVE_PATH "target_loads",
Custom PowerHAL implementation PowerHAL highlights: * The CPU governor is always interactive. Governor changes are not expected and permissions are set once on boot. * Powersave profile: the CPU frequency is limited 787MHz and the CPU is never boosted on user interaction. This will save power without making the phone unbearably slow. * Performance profile: the CPU is constantly boosted. * Balanced profile: the CPU is boosted on user interaction. When the screen is turned off, the governor is tuned to lower the power consumption to save power in case of long lasting screen off activities such as music playback. * Currently there are no restrictions on the number of active cores. With this PowerHAL cpu-boost is not needed, so keep it disabled. In addition to that, drop all the properties based profiles and set config_perf_profile_prop to "powerhal" to make the framework send hints to PowerHAL when the power profile is changed. msm8226-common: PowerHAL: Initialize mutex Since the mutex is declared as static, this went unnoticed, but mutexes should always be initialized, so do it. msm8226-common: PowerHAL: Don't override user selected profiles Save and restore the last selected profile so that the user preference is not lost when transitioning out the low power mode. Also, don't actually change the profile if in low power mode, but don't discard the user preference. msm8226-common: Refactor PowerHAL Make the HAL generic by keeping the device dependent configuration separate. This allows to easily add or edit the profiles. The HAL should behave exactly as before, except for the fact that now there might be some useless writes when the screen is turned off. Change-Id: I6bb01a14f0058c59986989568e7766f4203150cc
2015-12-05 05:55:29 +00:00
profiles[current_power_profile].target_loads);
2018-05-24 19:43:45 +00:00
sysfs_write_int(CPUFREQ_PATH "scaling_min_freq",
profiles[current_power_profile].scaling_min_freq);
Custom PowerHAL implementation PowerHAL highlights: * The CPU governor is always interactive. Governor changes are not expected and permissions are set once on boot. * Powersave profile: the CPU frequency is limited 787MHz and the CPU is never boosted on user interaction. This will save power without making the phone unbearably slow. * Performance profile: the CPU is constantly boosted. * Balanced profile: the CPU is boosted on user interaction. When the screen is turned off, the governor is tuned to lower the power consumption to save power in case of long lasting screen off activities such as music playback. * Currently there are no restrictions on the number of active cores. With this PowerHAL cpu-boost is not needed, so keep it disabled. In addition to that, drop all the properties based profiles and set config_perf_profile_prop to "powerhal" to make the framework send hints to PowerHAL when the power profile is changed. msm8226-common: PowerHAL: Initialize mutex Since the mutex is declared as static, this went unnoticed, but mutexes should always be initialized, so do it. msm8226-common: PowerHAL: Don't override user selected profiles Save and restore the last selected profile so that the user preference is not lost when transitioning out the low power mode. Also, don't actually change the profile if in low power mode, but don't discard the user preference. msm8226-common: Refactor PowerHAL Make the HAL generic by keeping the device dependent configuration separate. This allows to easily add or edit the profiles. The HAL should behave exactly as before, except for the fact that now there might be some useless writes when the screen is turned off. Change-Id: I6bb01a14f0058c59986989568e7766f4203150cc
2015-12-05 05:55:29 +00:00
} else {
sysfs_write_int(INTERACTIVE_PATH "hispeed_freq",
profiles[current_power_profile].hispeed_freq_off);
sysfs_write_int(INTERACTIVE_PATH "go_hispeed_load",
profiles[current_power_profile].go_hispeed_load_off);
2018-05-24 19:43:45 +00:00
sysfs_write_int(INTERACTIVE_PATH "target_loads",
Custom PowerHAL implementation PowerHAL highlights: * The CPU governor is always interactive. Governor changes are not expected and permissions are set once on boot. * Powersave profile: the CPU frequency is limited 787MHz and the CPU is never boosted on user interaction. This will save power without making the phone unbearably slow. * Performance profile: the CPU is constantly boosted. * Balanced profile: the CPU is boosted on user interaction. When the screen is turned off, the governor is tuned to lower the power consumption to save power in case of long lasting screen off activities such as music playback. * Currently there are no restrictions on the number of active cores. With this PowerHAL cpu-boost is not needed, so keep it disabled. In addition to that, drop all the properties based profiles and set config_perf_profile_prop to "powerhal" to make the framework send hints to PowerHAL when the power profile is changed. msm8226-common: PowerHAL: Initialize mutex Since the mutex is declared as static, this went unnoticed, but mutexes should always be initialized, so do it. msm8226-common: PowerHAL: Don't override user selected profiles Save and restore the last selected profile so that the user preference is not lost when transitioning out the low power mode. Also, don't actually change the profile if in low power mode, but don't discard the user preference. msm8226-common: Refactor PowerHAL Make the HAL generic by keeping the device dependent configuration separate. This allows to easily add or edit the profiles. The HAL should behave exactly as before, except for the fact that now there might be some useless writes when the screen is turned off. Change-Id: I6bb01a14f0058c59986989568e7766f4203150cc
2015-12-05 05:55:29 +00:00
profiles[current_power_profile].target_loads_off);
2018-05-24 19:43:45 +00:00
sysfs_write_int(CPUFREQ_PATH "scaling_min_freq",
profiles[current_power_profile].scaling_min_freq_off);
Custom PowerHAL implementation PowerHAL highlights: * The CPU governor is always interactive. Governor changes are not expected and permissions are set once on boot. * Powersave profile: the CPU frequency is limited 787MHz and the CPU is never boosted on user interaction. This will save power without making the phone unbearably slow. * Performance profile: the CPU is constantly boosted. * Balanced profile: the CPU is boosted on user interaction. When the screen is turned off, the governor is tuned to lower the power consumption to save power in case of long lasting screen off activities such as music playback. * Currently there are no restrictions on the number of active cores. With this PowerHAL cpu-boost is not needed, so keep it disabled. In addition to that, drop all the properties based profiles and set config_perf_profile_prop to "powerhal" to make the framework send hints to PowerHAL when the power profile is changed. msm8226-common: PowerHAL: Initialize mutex Since the mutex is declared as static, this went unnoticed, but mutexes should always be initialized, so do it. msm8226-common: PowerHAL: Don't override user selected profiles Save and restore the last selected profile so that the user preference is not lost when transitioning out the low power mode. Also, don't actually change the profile if in low power mode, but don't discard the user preference. msm8226-common: Refactor PowerHAL Make the HAL generic by keeping the device dependent configuration separate. This allows to easily add or edit the profiles. The HAL should behave exactly as before, except for the fact that now there might be some useless writes when the screen is turned off. Change-Id: I6bb01a14f0058c59986989568e7766f4203150cc
2015-12-05 05:55:29 +00:00
}
}
static void set_power_profile(int profile)
{
if (!is_profile_valid(profile)) {
ALOGE("%s: unknown profile: %d", __func__, profile);
return;
}
if (profile == current_power_profile)
return;
ALOGD("%s: setting profile %d", __func__, profile);
sysfs_write_int(INTERACTIVE_PATH "boost",
profiles[profile].boost);
sysfs_write_int(INTERACTIVE_PATH "boostpulse_duration",
profiles[profile].boostpulse_duration);
sysfs_write_int(INTERACTIVE_PATH "go_hispeed_load",
profiles[profile].go_hispeed_load);
sysfs_write_int(INTERACTIVE_PATH "hispeed_freq",
profiles[profile].hispeed_freq);
sysfs_write_int(INTERACTIVE_PATH "min_sample_time",
profiles[profile].min_sample_time);
2018-05-24 19:43:45 +00:00
sysfs_write_int(INTERACTIVE_PATH "timer_rate",
profiles[profile].timer_rate);
sysfs_write_int(INTERACTIVE_PATH "above_hispeed_delay",
profiles[profile].above_hispeed_delay);
sysfs_write_int(INTERACTIVE_PATH "target_loads",
Custom PowerHAL implementation PowerHAL highlights: * The CPU governor is always interactive. Governor changes are not expected and permissions are set once on boot. * Powersave profile: the CPU frequency is limited 787MHz and the CPU is never boosted on user interaction. This will save power without making the phone unbearably slow. * Performance profile: the CPU is constantly boosted. * Balanced profile: the CPU is boosted on user interaction. When the screen is turned off, the governor is tuned to lower the power consumption to save power in case of long lasting screen off activities such as music playback. * Currently there are no restrictions on the number of active cores. With this PowerHAL cpu-boost is not needed, so keep it disabled. In addition to that, drop all the properties based profiles and set config_perf_profile_prop to "powerhal" to make the framework send hints to PowerHAL when the power profile is changed. msm8226-common: PowerHAL: Initialize mutex Since the mutex is declared as static, this went unnoticed, but mutexes should always be initialized, so do it. msm8226-common: PowerHAL: Don't override user selected profiles Save and restore the last selected profile so that the user preference is not lost when transitioning out the low power mode. Also, don't actually change the profile if in low power mode, but don't discard the user preference. msm8226-common: Refactor PowerHAL Make the HAL generic by keeping the device dependent configuration separate. This allows to easily add or edit the profiles. The HAL should behave exactly as before, except for the fact that now there might be some useless writes when the screen is turned off. Change-Id: I6bb01a14f0058c59986989568e7766f4203150cc
2015-12-05 05:55:29 +00:00
profiles[profile].target_loads);
sysfs_write_int(CPUFREQ_PATH "scaling_max_freq",
profiles[profile].scaling_max_freq);
2018-05-24 19:43:45 +00:00
sysfs_write_int(CPUFREQ_PATH "scaling_min_freq",
profiles[profile].scaling_min_freq);
Custom PowerHAL implementation PowerHAL highlights: * The CPU governor is always interactive. Governor changes are not expected and permissions are set once on boot. * Powersave profile: the CPU frequency is limited 787MHz and the CPU is never boosted on user interaction. This will save power without making the phone unbearably slow. * Performance profile: the CPU is constantly boosted. * Balanced profile: the CPU is boosted on user interaction. When the screen is turned off, the governor is tuned to lower the power consumption to save power in case of long lasting screen off activities such as music playback. * Currently there are no restrictions on the number of active cores. With this PowerHAL cpu-boost is not needed, so keep it disabled. In addition to that, drop all the properties based profiles and set config_perf_profile_prop to "powerhal" to make the framework send hints to PowerHAL when the power profile is changed. msm8226-common: PowerHAL: Initialize mutex Since the mutex is declared as static, this went unnoticed, but mutexes should always be initialized, so do it. msm8226-common: PowerHAL: Don't override user selected profiles Save and restore the last selected profile so that the user preference is not lost when transitioning out the low power mode. Also, don't actually change the profile if in low power mode, but don't discard the user preference. msm8226-common: Refactor PowerHAL Make the HAL generic by keeping the device dependent configuration separate. This allows to easily add or edit the profiles. The HAL should behave exactly as before, except for the fact that now there might be some useless writes when the screen is turned off. Change-Id: I6bb01a14f0058c59986989568e7766f4203150cc
2015-12-05 05:55:29 +00:00
current_power_profile = profile;
}
static void power_hint(__attribute__((unused)) struct power_module *module,
power_hint_t hint, void *data)
{
char buf[80];
int len;
switch (hint) {
case POWER_HINT_INTERACTION:
if (!is_profile_valid(current_power_profile)) {
ALOGD("%s: no power profile selected yet", __func__);
return;
}
if (!profiles[current_power_profile].boostpulse_duration)
return;
if (boostpulse_open() >= 0) {
snprintf(buf, sizeof(buf), "%d", 1);
len = write(boostpulse_fd, &buf, sizeof(buf));
if (len < 0) {
strerror_r(errno, buf, sizeof(buf));
ALOGE("Error writing to boostpulse: %s\n", buf);
pthread_mutex_lock(&lock);
close(boostpulse_fd);
boostpulse_fd = -1;
pthread_mutex_unlock(&lock);
}
}
break;
case POWER_HINT_SET_PROFILE:
pthread_mutex_lock(&lock);
set_power_profile(*(int32_t *)data);
pthread_mutex_unlock(&lock);
break;
case POWER_HINT_LOW_POWER:
/* This hint is handled by the framework */
break;
default:
break;
}
}
static int get_feature(__attribute__((unused)) struct power_module *module,
feature_t feature)
{
if (feature == POWER_FEATURE_SUPPORTED_PROFILES) {
return PROFILE_MAX;
}
return -1;
}
2018-05-24 19:43:45 +00:00
static int power_open(const hw_module_t* module, const char* name,
hw_device_t** device)
{
ALOGD("%s: enter; name=%s", __FUNCTION__, name);
if (strcmp(name, POWER_HARDWARE_MODULE_ID)) {
return -EINVAL;
}
power_module_t *dev = (power_module_t *)calloc(1,
sizeof(power_module_t));
if (!dev) {
ALOGD("%s: failed to allocate memory", __FUNCTION__);
return -ENOMEM;
}
dev->common.tag = HARDWARE_MODULE_TAG;
dev->common.module_api_version = POWER_MODULE_API_VERSION_0_2;
dev->common.hal_api_version = HARDWARE_HAL_API_VERSION;
dev->init = power_init;
dev->powerHint = power_hint; // This is handled by framework
dev->setInteractive = power_set_interactive;
dev->getFeature = get_feature;
*device = (hw_device_t*)dev;
ALOGD("%s: exit", __FUNCTION__);
return 0;
}
static struct hw_module_methods_t power_module_methods = {
.open = power_open,
};
Custom PowerHAL implementation PowerHAL highlights: * The CPU governor is always interactive. Governor changes are not expected and permissions are set once on boot. * Powersave profile: the CPU frequency is limited 787MHz and the CPU is never boosted on user interaction. This will save power without making the phone unbearably slow. * Performance profile: the CPU is constantly boosted. * Balanced profile: the CPU is boosted on user interaction. When the screen is turned off, the governor is tuned to lower the power consumption to save power in case of long lasting screen off activities such as music playback. * Currently there are no restrictions on the number of active cores. With this PowerHAL cpu-boost is not needed, so keep it disabled. In addition to that, drop all the properties based profiles and set config_perf_profile_prop to "powerhal" to make the framework send hints to PowerHAL when the power profile is changed. msm8226-common: PowerHAL: Initialize mutex Since the mutex is declared as static, this went unnoticed, but mutexes should always be initialized, so do it. msm8226-common: PowerHAL: Don't override user selected profiles Save and restore the last selected profile so that the user preference is not lost when transitioning out the low power mode. Also, don't actually change the profile if in low power mode, but don't discard the user preference. msm8226-common: Refactor PowerHAL Make the HAL generic by keeping the device dependent configuration separate. This allows to easily add or edit the profiles. The HAL should behave exactly as before, except for the fact that now there might be some useless writes when the screen is turned off. Change-Id: I6bb01a14f0058c59986989568e7766f4203150cc
2015-12-05 05:55:29 +00:00
struct power_module HAL_MODULE_INFO_SYM = {
.common = {
.tag = HARDWARE_MODULE_TAG,
.module_api_version = POWER_MODULE_API_VERSION_0_2,
.hal_api_version = HARDWARE_HAL_API_VERSION,
.id = POWER_HARDWARE_MODULE_ID,
.name = "msm8226 Power HAL",
2018-05-24 19:43:45 +00:00
.author = "The LineageOS Project",
Custom PowerHAL implementation PowerHAL highlights: * The CPU governor is always interactive. Governor changes are not expected and permissions are set once on boot. * Powersave profile: the CPU frequency is limited 787MHz and the CPU is never boosted on user interaction. This will save power without making the phone unbearably slow. * Performance profile: the CPU is constantly boosted. * Balanced profile: the CPU is boosted on user interaction. When the screen is turned off, the governor is tuned to lower the power consumption to save power in case of long lasting screen off activities such as music playback. * Currently there are no restrictions on the number of active cores. With this PowerHAL cpu-boost is not needed, so keep it disabled. In addition to that, drop all the properties based profiles and set config_perf_profile_prop to "powerhal" to make the framework send hints to PowerHAL when the power profile is changed. msm8226-common: PowerHAL: Initialize mutex Since the mutex is declared as static, this went unnoticed, but mutexes should always be initialized, so do it. msm8226-common: PowerHAL: Don't override user selected profiles Save and restore the last selected profile so that the user preference is not lost when transitioning out the low power mode. Also, don't actually change the profile if in low power mode, but don't discard the user preference. msm8226-common: Refactor PowerHAL Make the HAL generic by keeping the device dependent configuration separate. This allows to easily add or edit the profiles. The HAL should behave exactly as before, except for the fact that now there might be some useless writes when the screen is turned off. Change-Id: I6bb01a14f0058c59986989568e7766f4203150cc
2015-12-05 05:55:29 +00:00
.methods = &power_module_methods,
},
.init = power_init,
.setInteractive = power_set_interactive,
.powerHint = power_hint,
.getFeature = get_feature
};