| commit | 3fcfd8b6d7d222ec6b220debf806733e36d6d285 | [log] [tgz] |
|---|---|---|
| author | Ady Abraham <adyabr@google.com> | Tue Jul 12 12:31:00 2022 -0700 |
| committer | Ady Abraham <adyabr@google.com> | Tue Aug 09 23:39:48 2022 +0000 |
| tree | 5c5cf1a670112808719745cbb4f9703758dc8d17 | |
| parent | fdff5cded8c1cc5c86a77947e0d1c6b3c1179abb [diff] |
SF: avoid dispatching close vsyncs When the vsync period changes, the next vsync callback might be targeting the same vsync event, that now has a newer time based on the current period. This means that the client might be woken up for 2 frames within the same vsync. This change tries to avoid that by making sure that the vsync callbacks are at least a vsync period apart minus a safe distance. Test: new unit test Bug: 235566681 Change-Id: Ifb9b3f8b726976452d5131c8b758d1d5ca0e3639