6
edits
Project Silk: Difference between revisions
m
no edit summary
mNo edit summary |
|||
| Line 20: | Line 20: | ||
* VsyncDispatcherHostImpl creates a dedicated thread, named as <b>vsync dispatcher thread</b>, to dispatch vsync-event. Since vsync-event dispatching is very performance sensitive, we create a dedicate thread which only works on event dispatching to prevent transmission flow from being blocked by irrelevant tasks. | * VsyncDispatcherHostImpl creates a dedicated thread, named as <b>vsync dispatcher thread</b>, to dispatch vsync-event. Since vsync-event dispatching is very performance sensitive, we create a dedicate thread which only works on event dispatching to prevent transmission flow from being blocked by irrelevant tasks. | ||
* Receive vsync events from PlatformVsyncTimer. We use HWComposer to implement the PlatformVsyncTimer in Gonk. On platforms which have no HW vsync supported, it's fallback to SW vsync driver automatically. | * Receive vsync events from PlatformVsyncTimer. We use HWComposer to implement the PlatformVsyncTimer in Gonk. On platforms which have no HW vsync supported, it's fallback to SW vsync driver automatically. | ||
* Export registry functions to clients who want to receive vsync-event notification. Currently, we have | * Export registry functions to clients who want to receive vsync-event notification. Currently, we have three types of clients: refresh driver, compositor and input dispatcher. | ||
* Sent vsync notifications to registered listeners, on the <b>vsync dispatcher thread</b>. | * Sent vsync notifications to registered listeners, on the <b>vsync dispatcher thread</b>. | ||