commit 3bd1b65ffbc46ee195bdb267eef5f918f38fe15b
author The Android Automerger <android-build@google.com> Tue Oct 15 06:00:54 2013 -0700
committer The Android Automerger <android-build@google.com> Tue Oct 15 06:00:54 2013 -0700
tree 65a66e24b58a3258e84c0d251d579bf47ac7fac3
parent 8e26b28be62e7c0e093900540db5e5cdcf52a0ff
parent 4fec2900a395aac6600b4a65529de2f514c40b7b

merge in klp-release history after reset to klp-dev

services/surfaceflinger/DisplayHardware/HWComposer.cpp

diff --git a/services/surfaceflinger/DisplayHardware/HWComposer.cpp b/services/surfaceflinger/DisplayHardware/HWComposer.cpp
index 179d956..2469f0c 100644
--- a/services/surfaceflinger/DisplayHardware/HWComposer.cpp
+++ b/services/surfaceflinger/DisplayHardware/HWComposer.cpp
@@ -284,13 +284,27 @@
 
 void HWComposer::vsync(int disp, int64_t timestamp) {
     if (uint32_t(disp) < HWC_NUM_PHYSICAL_DISPLAY_TYPES) {
+        {
+            Mutex::Autolock _l(mLock);
+
+            // There have been reports of HWCs that signal several vsync events
+            // with the same timestamp when turning the display off and on. This
+            // is a bug in the HWC implementation, but filter the extra events
+            // out here so they don't cause havoc downstream.
+            if (timestamp == mLastHwVSync[disp]) {
+                ALOGW("Ignoring duplicate VSYNC event from HWC (t=%lld)",
+                        timestamp);
+                return;
+            }
+
+            mLastHwVSync[disp] = timestamp;
+        }
+
         char tag[16];
         snprintf(tag, sizeof(tag), "HW_VSYNC_%1u", disp);
         ATRACE_INT(tag, ++mVSyncCounts[disp] & 1);
 
         mEventHandler.onVSyncReceived(disp, timestamp);
-        Mutex::Autolock _l(mLock);
-        mLastHwVSync[disp] = timestamp;
     }
 }