Confirmed users
1,643
edits
Project Silk: Difference between revisions
Jump to navigation
Jump to search
→VsyncDispatcher
| Line 13: | Line 13: | ||
In chrome process | In chrome process | ||
* VsyncDispathcer creates a dedicated thread, named vsync dispatcher thread, to dispatch vsync-event. Vsync-event dispatching is very performance sensitive, we need to have a dedicate thread in charge of event dispatching to prevent transmission been blocked by irrelevant tasks. | * VsyncDispathcer creates a dedicated thread, named vsync dispatcher thread, to dispatch vsync-event. Vsync-event dispatching is very performance sensitive, we need to have a dedicate thread in charge of event dispatching to prevent transmission been blocked by irrelevant tasks. | ||
* | * VsyncDispatcher object factory. | ||
* Receive HW vsync events from HWComposer. On platforms which have no HW vsync supported, it's fallback to SW vsync driver automatically. | * Receive HW vsync events from HWComposer. On platforms which have no HW vsync supported, it's fallback to SW vsync driver automatically. | ||
* Export registry/unregistry function to users who want to receive vsync-event notification. | * Export registry/unregistry function to users who want to receive vsync-event notification. | ||