summaryrefslogtreecommitdiff
path: root/libs/binder/IActivityManager.cpp
diff options
context:
space:
mode:
author Alec Mouri <alecmouri@google.com> 2020-11-09 18:35:20 -0800
committer Alec Mouri <alecmouri@google.com> 2020-11-24 15:12:51 -0800
commitc7f6c8b43f78ff4b469d2d7e283d176cb0f4f1ac (patch)
treee288e4085f77cf6765eaaae9f6fac7e30b40dfab /libs/binder/IActivityManager.cpp
parent733c24fba800afcfd242ce0ac1f3aa215c6af1a8 (diff)
Introduce AutoBackendTexture into Skia-RenderEngine
Conceptually this is the same class as AutoBackendTextureRelease in libhwui. We require this because: * As with the equivalent class in libhwui, buffers are reused and therefore their content is mutable, but SkImages are defined to be immutable, so the workaround is to cache the backing texture instead. * Color spaces associated with a buffer are not guaranteed to be constant. The HWC is allowed to request a different color space for the client target depending on the set of input layers. This means that SkSurfaces need to be recreated when the color space changes. Furthermore, since LinearEffects performs tone-mapping and wants to sidestep Skia's built-in tone mapping process, this means that when tone-mapping is enabled we lie about the color space of the input buffers so that we don't do multiple tone-mapping passes. But this means that SkImages need to be recreated for those scenarios too so that the input content can be reinterpreted with a different color space. Also, append additional trace points onto this CL to get a better handle on RenderEngine perf. Bug: 164223050 Test: On a Pixel 3, play HDR content on Youtube with PQ and HLG transfer functions, and toggle full-screen GL composition on and off. Change-Id: Ic53a422545b4fb563c7e75c73d978350d38181d5
Diffstat (limited to 'libs/binder/IActivityManager.cpp')
0 files changed, 0 insertions, 0 deletions