summaryrefslogtreecommitdiffstats
path: root/power-8998.c
Commit message (Collapse)AuthorAgeFilesLines
* power: don't use SCROLL_PREFILINGtomascus2019-02-281-7/+2
| | | | | | | | | | | | | | | | | | | | | | | | 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
* power: Release launch boost perflock when launch is completedtomascus2019-02-281-4/+23
| | | | | | | | | | | | | | | | | | | | | 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
* power: Pass NULL parameter in powerHint if data is zerodianlujitao2019-02-281-3/+4
| | | | | | | * This restores the behavior in AOSP and CAF power HAL to avoid confusion. Change-Id: I72f5bb9286e2f57121e39eea82d2fe8854989393
* power: Handle launch and interaction hints for perf HAL platformsBeYkeRYkt2019-01-121-3/+60
| | | | | | | | | | | * 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
* power: set_power_profile: handle errorsCorinna Vinschen2018-10-021-14/+26
| | | | | | | | | * 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>
* power: Spring cleanupMichael Bestas2018-05-251-40/+39
| | | | | | | | | | | | * Cleanup SoC specific files: - Fix code spacing and indentation - Remove dead code - Remove useless comments - Remove useless logs - Make code uniform between the files so it's easier to diff - Use declared enums when possible for power hints Change-Id: Ie1378c94c53b33299927c5eb1bfc19f1a42b8743
* power: Consistent skipping of non perf profile hintsMichael Bestas2018-04-161-3/+5
| | | | Change-Id: I9129de9046df7b922af7b32eac94167776f820cf
* power: Use consistent LOG_TAGMichael Bestas2018-03-261-1/+1
| | | | Change-Id: I4d28a01b62ea5f962cdb2f741f00903f1e9a6899
* power: Don't advertise power profile when interaction boost disableddianlujitao2018-03-041-0/+2
| | | | | | * Power profile is fake news without interaction boost. Change-Id: Iceea885e6cb176f0620e76cfc335b7da500a0c2b
* power: msm8998: Fix perf mode switchdianlujitao2018-02-081-1/+1
| | | | | | | * Checking a pointer is NULL or not makes no sense, and as a result perf mode cannot be turned off. Fix it by checking the value. Change-Id: I4feb37da72b757631619e1aa2917f2a345a8032b
* power: msm8998: Support power profilesdianlujitao2018-02-081-0/+74
| | | | Change-Id: I8a11aa9db00051cfaae650273d980ce5080f6567
* power: Convert to fully binderized 1.1 implementationRashed Abdel-Tawab2017-12-291-12/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Based on commits c043816b3ceb8d8094c13f76341d4c86f09a44d1 and f3e845ce21adf40b4caa8982447b0bf99eeeee81 from AOSP device/google/wahoo. Commit 1: commit: c043816b3ceb8d8094c13f76341d4c86f09a44d1 author: Ahmed ElArabawy <arabawy@google.com> date: Wed Apr 12 09:50:07 2017 -0700 power hal: Add power HAL API 1.1 impl for Wahoo Add a full binderized implementation for Power hal Many subsystems (e.g.wifi) could be living on an independent power island (sourced from VBatt directly) and might even have their own dedicated XTAL to source their clocks. Since these SOCs are capable of autonomously operating (while the platform is in one of the sleep states), they are still drawing power from the VBatt. Hence it is critical to understand the (SOC) level low power statistics as well when the battery level changes and be able to find any correlation in event of unexpected battery drain. This commit adds the support of the Power Hal 1.1 to wahoo based devices(that includes Muskie/walleye). This includes the new api for wlan specific power stats Bug: 29339696 Test: Manual Change-Id: Iee4e38f2d9ced31f8b6a333b535fa1d9a302ec26 Signed-off-by: Ahmed ElArabawy <arabawy@google.com> Commit 2: commit: f3e845ce21adf40b4caa8982447b0bf99eeeee81 author: Ahmed ElArabawy <arabawy@google.com> aate: Wed May 24 15:28:04 2017 +0000 Re-introduce of POWER HAL API 1.1 impl for Wahoo Power HAL 1.1 support for wahoo based devices was initially introduced in CL ag/2098359 However, this caused a regression in application startup times due to a bug in passing parameters for power hints on application launch Hence, that CL was reverted in CL ag/2270791 This commit brings back the support of the Power Hal 1.1 to wahoo based devices. This includes the changes of the original CL as will as a fix for the app startup time regression The fix is similar to that in ag/1767023 (done for power HAL 1.0 default implementation) where a NULL is passed to the powerHint function when the passed data is Zero (instead of passing a pointer to the data). This enable the App Launch power hints to work properly The commit has been tested not to cause that regression Bug: 62040325 Test: Performance Tests along with other tests Change-Id: I29ce38b2de92c2b9ad878b0076288b689695b8a0 Signed-off-by: Ahmed ElArabawy <arabawy@google.com>
* power: Fix power hal compiler warningsAdrian Salido2017-12-291-2/+2
| | | | | | Bug: 30432975 Test: compile power hal for walleye without warnings Change-Id: I0d90c26462c662690f8a179250000b9a449a109f
* power: Build with VNDK=currentRashed Abdel-Tawab2017-12-291-1/+2
| | | | Change-Id: I27b9a90dbb5214cc8973d8de0775eb9fe30922ec
* Changes to handle VR state transition in power HALSathish Ambley2017-07-061-85/+96
| | | | Change-Id: Ieb104ca1a8d7dce3678f9d22a6e820049f70fe3d
* power: Using PerfHAL APIAnanth Raghavan Subramanian2017-07-061-65/+17
| | | | | | Using the PerfHAL API to comply with Treble Change-Id: I0ce40bbefb8c867dda8ee5eb1f948af2106e692d
* power: PowerHAL for 8998Ananth Raghavan Subramanian2017-03-281-0/+261
PowerHAL now parses xml for resource list Change-Id: Ic5c2c1836e3b092e5cdc3827e323a2ffc816f5a3
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-15 21:10:37 +0000