Confirmed users
346
edits
Project Silk: Difference between revisions
Jump to navigation
Jump to search
→Power on/off screen
| Line 84: | Line 84: | ||
Here HWComposer2D is responsible to notify Vsync events to VsyncDispatcher. Android HWC only supports HW Vsync after android JB. Therefore, we also port SW Vsync into HWComposer2D. If there is no HW Vsync support, the SW Vsync will be used. During initialization phase, VsyncDispatcher registers a Vsync notification callback into HWComposer2D and this callback will be called for every Vsync events. If there is no Vsync observer, we can disable the Vsync notifications inside HWComposer2D. | Here HWComposer2D is responsible to notify Vsync events to VsyncDispatcher. Android HWC only supports HW Vsync after android JB. Therefore, we also port SW Vsync into HWComposer2D. If there is no HW Vsync support, the SW Vsync will be used. During initialization phase, VsyncDispatcher registers a Vsync notification callback into HWComposer2D and this callback will be called for every Vsync events. If there is no Vsync observer, we can disable the Vsync notifications inside HWComposer2D. | ||
==== Power on/off screen ==== | ==== Power on/off screen ==== | ||
We can't control the HW Vsync event on/off during power off. We will always turn off the Vsync event at power off and force to turn on at power on. That's ok if VsyncDispatcher receive an unexpected Vsync event at power on. After receiving the Vsync event, we can just disable the HW Vsync again. | |||
===Testing Plan=== | ===Testing Plan=== | ||