mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-13 08:07:32 -04:00
No description
- C 98.2%
- Assembly 1%
- Makefile 0.3%
- Shell 0.2%
- Python 0.1%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
c5e17fee8f
Normally, the TCS needs to wait for completion in both AMC and WAKE sets, since we need to be sure all necessary system resources are available before they are used. However, the display RSC has strict wakeup timelines to meet and thus cannot take the latency hit caused by waiting for completion in the WAKE set. The display RSC will perform additional processing in between when the WAKE request is sent and completed. The apps RSC will hold minimum votes on each required resource to ensure they are enabled, which prevents any unclocked access. The display RSC is just responsible for scaling to the required performance levels. The worst that can happen if the WAKE request isn't satisfied in time is a dropped frame. Change-Id: Id3757b2ffc73ee93ed8f97d7d591e135150c9cdc |
||
| bindings | ||
| qcom | ||
| Makefile | ||