* Read sysfs entries, to get vsync timestamp from kernel.
* External display continues to use in ueventThread.
* A new thread, vsyncThread is created to read and send vsync
timestamps to HAL.
* Disable H/W VSYNC for MDP 5.x targets until kernel changes are
complete.
(cherry picked from commit a61a58cb775631cd3899211f6ff0aed232f5f3c0)
Change-Id: I58e09a092f81d4ff78b8cb4072ff06d2500c6f53
* Poll on FB0 sysfs for VSYNC events. This requires kernel support to
call sysfs_notify instead of sending a uevent.
Change-Id: I48734d8ffdd59dc1de7064fa004af1332ceb7623
- There is a race condition window between initializing hwcomposer as a
whole and registering callback functions for when the uevents arrive. We
can fix this issue by delaying the uevent thread kick off until the
callback functions are registered.
- Add thread name to uevent thread
Change-Id: I30e23b411b92b6578f186b641f562462a8f23179
the hdmi driver can send change uevent anytime, in which case, the
connected state was getting set to 0, due to its default value.
Change-Id: I22dc96acda0272661750277d62c5c11c5156fb3b
- wait for hdmi vsync when connected to hdmi
- add commit to call PANDISPLAY for updating ext display
- add functions to close fb and reset info
Change-Id: Icdd3620bd9d15240a88a26a3f1bf9c07d58d011b
* Use the vsync uevents from the kernel to start
surfaceflinger composition.
* This patch also does some code cleanup
- Move copybit specific functions to copybit files.
- Cleanup verbose logging.
Change-Id: I8ca3cd7a7ceb53655ed0fcf39ac2cb35e6cbe890
