Andy McFadden 9e9689c111 Fix HDMI unblank behavior ... Two issues: (1) We were announcing the hotplug event before we were ready to handle blank/unblank events, so we were losing the initial unblank that power manager sends us when HDMI is first plugged in. This left the display blank until you toggled the device power off/on. (2) We were retaining fbTargetHandle for HDMI after the display was disconnected. The value didn't get updated when HDMI was reconnected because the display was blank, so we didn't go through that code path. So, when HDMI was re-connected, we passed stale data into the HWC. Bug 7323938 Change-Id: I2335d24fd7b0f00bb23fc63aa7bcf44cb8857c73		2012-10-10 18:17:51 -07:00
..
FramebufferSurface.cpp	we now correctly set-up connected screens during boot	2012-09-20 17:13:58 -07:00
FramebufferSurface.h	we now correctly set-up connected screens during boot	2012-09-20 17:13:58 -07:00
GraphicBufferAlloc.cpp	GraphicBufferAlloc class was declared twice	2012-09-20 17:13:58 -07:00
GraphicBufferAlloc.h	GraphicBufferAlloc class was declared twice	2012-09-20 17:13:58 -07:00
HWComposer.cpp	Fix HDMI unblank behavior	2012-10-10 18:17:51 -07:00
HWComposer.h	fix dumpsys Layer name when using multiple displays	2012-10-08 15:57:17 -07:00
PowerHAL.cpp	don't actuate vsync hint when not needed	2012-04-27 13:55:05 -07:00
PowerHAL.h	don't actuate vsync hint when not needed	2012-04-27 13:55:05 -07:00