DispSync: don't compensate for wakeup latency
This change removes the wakeup latency compensation from the software-generated vsync events. Choreographer can't handle timestamps in the future, so don't aim for early wake-ups with the expectation that the actual wake-up will be late. Bug: 11153576
This commit is contained in:
parent
98c197d826
commit
0d5c60edf1
@ -110,7 +110,7 @@ public:
|
|||||||
}
|
}
|
||||||
|
|
||||||
nextEventTime = computeNextEventTimeLocked(now);
|
nextEventTime = computeNextEventTimeLocked(now);
|
||||||
targetTime = nextEventTime - mWakeupLatency;
|
targetTime = nextEventTime;
|
||||||
|
|
||||||
bool isWakeup = false;
|
bool isWakeup = false;
|
||||||
|
|
||||||
@ -228,7 +228,7 @@ private:
|
|||||||
nsecs_t t = computeListenerNextEventTimeLocked(mEventListeners[i],
|
nsecs_t t = computeListenerNextEventTimeLocked(mEventListeners[i],
|
||||||
ref);
|
ref);
|
||||||
|
|
||||||
if (t - mWakeupLatency < now) {
|
if (t < now) {
|
||||||
CallbackInvocation ci;
|
CallbackInvocation ci;
|
||||||
ci.mCallback = mEventListeners[i].mCallback;
|
ci.mCallback = mEventListeners[i].mCallback;
|
||||||
ci.mEventTime = t;
|
ci.mEventTime = t;
|
||||||
|
Loading…
Reference in New Issue
Block a user