summaryrefslogtreecommitdiffstats
path: root/power-845.c
Commit message (Collapse)AuthorAgeFilesLines
* power: Handle launch and interaction hints for perf HAL platformsBeYkeRYkt2019-10-231-6/+73
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* power: Use declared enums where possibleMichael Bestas2019-10-231-1/+1
| | | | Change-Id: I079490f8ff61bf278dd69eb89b9dae5ce42e6052
* power: Clean up and fix set_interactive_overrideMichael Bestas2019-10-231-7/+2
| | | | | | | | | | | * 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
* power: Clean up and fix video encode/decode hint handlingMichael Bestas2019-10-231-3/+0
| | | | | | | | * 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
* power: Use ARRAY_SIZE macro where possibleZhao Wei Liew2019-10-231-1/+1
| | | | Change-Id: Ie47d0e6b91b7bba378b0fdf53a345a021b0c2d48
* power: Avoid interaction build errorsMichael Bestas2019-10-231-3/+0
| | | | Change-Id: I77942f23a9c617abac1a8533cfc1fd7bfa7f66e8
* power: clang-formatMichael Bestas2019-10-231-82/+66
| | | | | | | * Using AOSP interface .clang-format * Clean Android.mk while we are at it Change-Id: I630f72e3dffb676ca1930e72945e897f62103ada
* power: Remove mutex to hintsdianlujitao2019-10-231-9/+0
| | | | | | * No longer needed. Change-Id: I09fc90b4e5399b3f3b8a409edf3f57361da90100
* power: Remove unused arg from power_hint_override/set_interactive_overrideRashed Abdel-Tawab2019-10-231-2/+2
| | | | Change-Id: If45b59915022b563d4c5c9bf454b02b431a97833
* power: Use log/log.h instead of utils/Log.hEthan Chen2019-10-231-1/+1
| | | | Change-Id: I827c7f5ab27548eec8d6e4ee27a72fa883025002
* power: Fix VNDK Compilation ErrorsVinay Verma2018-06-041-0/+2
| | | | | | | VNDK restrictions doesn't includes standard headers by default, add them explicitly. Change-Id: I4c72a28ffa141ecadcfe47cc7c1f62f2a0c8576e
* Relocate power HAL from device/qcom/commonDavid Ng2018-05-241-0/+272
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