| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Author: Michael Bestas <mkbestas@lineageos.org>
Date: Fri May 25 22:57:04 2018 +0300
power: msm8953: Add support for power profiles
* Based on legacy HAL implementation
* We no longer handle POWER_HINT_INTERACTION and POWER_HINT_LAUNCH,
they're now supported directly by Qualcomm mp-ctl.
Change-Id: If5b239a6fa1880e2e650f0e5c50c1357e8e3ac1a
Author: Corinna Vinschen <xda@vinschen.de>
Date: Sun Aug 26 22:11:49 2018 +0200
power: set_power_profile: handle errors
* Make sure current_power_profile reflects actual setting.
* Propagate error condition up to caller.
* Handle error from set_power_profile in power_hint_override.
Change-Id: I8518d921a94c912c75f59fbf993a8f44116bdca9
Signed-off-by: Corinna Vinschen <xda@vinschen.de>
Author: dianlujitao <dianlujitao@lineageos.org>
Date: Thu Sep 6 21:43:14 2018 +0800
power: Clean up hint IDs
* Group MPCTL v3 opcodes according to major type.
* Remove some unused/dead opcodes.
* Rename some misleading/inconsistency names.
Change-Id: I3a06930c8fff18a50f77cb230951dbd43d62fed3
Author: dianlujitao <dianlujitao@lineageos.org>
Date: Sat Feb 23 20:24:57 2019 +0800
power: Pass NULL parameter in powerHint if data is zero
* This restores the behavior in AOSP and CAF power HAL to avoid
confusion.
Change-Id: I72f5bb9286e2f57121e39eea82d2fe8854989393
Change-Id: I991bb6e3b20a0e6c8674136b309561af491d277f
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Author: BeYkeRYkt <beykerykt@gmail.com>
Date: Thu Dec 13 06:42:35 2018 +0900
power: Handle launch and interaction hints for perf HAL platforms
* MP-CTL does not handle POWER_HINT_INTERACTION and POWER_HINT_LAUNCH
directly. Requests for processing are sent by Qualcomm BoostFramework
(QPerformance) at the framework service level. Since we do not have
BoostFramework, process POWER_HINT_INTERACTION and POWER_HINT_LAUNCH
in PowerHAL to ensure a sufficient level of performance.
* For proper operation, perfboostsconfig.xml file is required.
Change-Id: I4c67d886c9dd74ae07094d32bdffc8ef403e04e7
Author: tomascus <arbiter1000@gmail.com>
Date: Wed Feb 13 14:42:27 2019 +1100
power: don't use SCROLL_PREFILING
The current use of the SCROLL_PREFILING hint hurts scroll performance
and results in a lot of dropped frames.
The hint ID corresponding to SCROLL_PREFILING only takes into effect for
a default timeout value of 80 ms (as found in perfboostsconfig.xml),
while the duration value in the process_interaction_hint function runs
for a much longer time, from 1500 ms up to 5000 ms (bounds of
kMinFlingDuration and kMaxInteractiveDuration). During the period
of time, when the timeout value has elapsed and current time is less
than duration, another interaction hint cannot be processed. Therefore,
if the user decides to scroll during this period, high frame drops can be
experienced as the CPU freq isn't raised by processing another hint to
account for this additional scrolling.
By only using SCROLL_VERTICAL, fluidity can be maintained, improving user
experience.
Furthmore, kMinInteractiveDuration has been lowered to 400 ms for some
platforms as it is more than sufficient to maintain fluidity (minimal
frames dropped) while scrolling.
Change-Id: I42edd07a67c7dca43a10ae2fa1b44b64b7794b43
commit e9063a6956974a2e33652e2df0ecac991ee84c80
Author: tomascus <arbiter1000@gmail.com>
Date: Tue Feb 19 17:15:58 2019 +1100
power: Release launch boost perflock when launch is completed
Currently, the launch boost perflock is held for a fixed duration, either
specified in perfboostsconfig.xml for perf HAL platforms or hardcoded in the
powerHAL for non-perf HAL platforms.
Using a fixed duration for this perflock has two shortcomings:
* perflock can be held for too long, causing the CPU freq and other resources
to be boosted for too long even if the application has finished launching,
resulting in excessive battery drainage
* perflock can be held not long enough if it takes more than the timeout
time to finish launch
The framework sends out a powerhint for both when launch starts and when
launch ends. The launch finish hint can be used to signal when to release the
perflock.
Reference: Wahoo power-libperfmgr
Change-Id: I405cc453c5f58d9fb2583b9c6017f3964a0ce024
Change-Id: I8ef6a890bc191f9504980707107750a720b50da3
|
|
|
|
| |
Change-Id: I079490f8ff61bf278dd69eb89b9dae5ce42e6052
|
|
|
|
|
|
|
|
|
|
|
| |
* Remove debug logs and useless comments
* Consistent return values
* Add back display hints for legacy platforms, they used to live in
power-common.c but removed in commit 561cffcbfa66192e839e040d2da3bff2ecf8dcac
* Check if set_interactive_override handled hints and print
info message if it didn't
Change-Id: Iff9f7327ba71c282e34ff3143c45a3f40f72fc92
|
|
|
|
|
|
|
|
| |
* Unify code style for non legacy SoCs
* Restore legacy SoC handling which used to live in power-common.c
but was removed in commit 561cffcbfa66192e839e040d2da3bff2ecf8dcac
Change-Id: Ieb84e6d6c8d762614e21267e81e6057aa64b36dd
|
|
|
|
| |
Change-Id: I90aed1aaee8d3819d1de921674da924efd0a6c4f
|
|
|
|
|
|
|
|
| |
* These were part of the commit that added mutex locks
for camera hints. We have now removed the locks so
this is no longer necessary
Change-Id: I38b91ce4e8fc811b8d9a04e6ec20521adde1b264
|
|
|
|
|
|
| |
* And fix the build errors
Change-Id: I183203edfd92d4672893d74aa7428bc9f5e17772
|
|
|
|
| |
Change-Id: Ie47d0e6b91b7bba378b0fdf53a345a021b0c2d48
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, get_soc_id() is queried on every SOC ID check in the
SDM660, MSM8916, MSM8952, MSM8953 and MSM8974-family HALs.
This results in extraneous file operations on every SOC ID check.
Cache the result of get_soc_id() during the first query to
reduce the number of file operations being made.
This also brings back the behaviour in LineageOS 15.1 when the
HALs were still stored in device/qcom/common.
Change-Id: Ic17dbf12e7f9ecdb47b73a580f467df9ad630aa0
|
|
|
|
|
|
|
|
|
|
|
| |
Check for whether the display hint has been sent at the start
of the set_interactive() function in the common powerHAL.
This gets rid of the need to replicate the same variable in
every target-specific powerHAL that implements the
set_interactive_override() function.
Change-Id: If7dd11fcb578211f4f83847f9257232c4138ce53
|
|
|
|
|
|
|
| |
- Get soc_id in a common util function
- Return boolean values for the target-specific soc_id checks
Change-Id: I038c435d28855859f36566de7acf881037d070f2
|
|
|
|
|
|
| |
* Don't copy paste the same governor check code multiple times
Change-Id: I2258553deb02a5ae149b0a96aca5fe5584f0ea14
|
|
|
|
|
|
|
| |
* This is not used by any recent qcom SoC
and not used by any SoC using this HAL.
Change-Id: If9b2997104bcd5e3ff27fc39c75590d07e813f85
|
|
|
|
|
|
|
| |
* Using AOSP interface .clang-format
* Clean Android.mk while we are at it
Change-Id: I630f72e3dffb676ca1930e72945e897f62103ada
|
|
|
|
|
|
| |
* No longer needed.
Change-Id: I09fc90b4e5399b3f3b8a409edf3f57361da90100
|
|
|
|
| |
Change-Id: If45b59915022b563d4c5c9bf454b02b431a97833
|
|
|
|
| |
Change-Id: I827c7f5ab27548eec8d6e4ee27a72fa883025002
|
|
|
|
|
|
| |
This is power hal for sdm632 used for camera cases
Change-Id: I9ae230993f6e7cb63b317cc26e5f64e2287d9672
|
|
|
|
| |
Change-Id: Ic2c82d5d734df00c15f628737253dde5d5a0bc4c
|
|
|
|
|
|
|
| |
PowerHAL writes to a sysfs node when it gets display on/off
notification.
Change-Id: I8c3437908f992aec23336ea104c6ac091a961205
|
|
Split module from combined device/qcom/common project into its
own project.
Relocation of some files from device/qcom/common at
b5ce80cb1f60759a142a9338104d3adf3303ec0c.
Change-Id: I6c13729a822f6fb9b5574b759ae9ec12154be464
|