Improve handling of hwcomposer with unsupported present fences
An implementation such as HWC2OnFbAdapter always returns -1 for the present fence. FrameTimeline should not ignore invalid fences in mPendingPresentFences, since in this case every fence is invalid, resulting in resource leaks. Similarly, PresentLatencyTracker should not be used if HWC doesn't support present fences. Test: no logspam running on starnix (fuchsia), which uses framebuffer Test: booted emulator, no behavior change Test: booted panther, no behavior change Change-Id: I4a11edc443a1cd3a395fc8f97b93a5474d11fe31
Loading
Please register or sign in to comment