diff options
| author | 2019-09-24 10:43:03 -0700 | |
|---|---|---|
| committer | 2019-09-24 10:47:59 -0700 | |
| commit | fe671024887b3f6d59025993d507380ae04e3ed8 (patch) | |
| tree | 1f94db11d93d02578eb73b14aa9d106550c76f00 /vulkan/libvulkan/api.cpp | |
| parent | cb2744f082bab4b89b8f94bd67e0e594ea255f40 (diff) | |
CE: Reset forceClientComposition on geometry update
If the output layer state ever had forceClientComposition set to true,
nothing would ever reset it to false. This would cause client
composition to be used when not necessary.
This regressed in my refactoring work. It was originally cleared in
SurfaceFlinger.cpp when the geometry was invalidated.
This patch adds it back, in an equivalent spot in the CompositionEngine
code.
Bug: 138853920
Bug: 139820579
Test: atest cts/tests/camera/src/android/hardware/camera2/cts/RecordingTest.java#testRecordingFramerateLowToHigh
Test: atest google/perf/jank/UIBench/UIBench
Test: atest libsurfaceflinger_unittest libcompositionengine_test
Test: atest CtsColorModeTestCases
Test: atest CtsDisplayTestCases
Test: atest CtsGraphicsTestCases
Test: atest CtsUiRenderingTestCases
Test: atest CtsViewTestCases
Test: atest android.media.cts.EncodeVirtualDisplayWithCompositionTest
Test: go/wm-smoke
Change-Id: I47f18094cea8ca298eae3bad1b1a9e56cb9ba6e0
Diffstat (limited to 'vulkan/libvulkan/api.cpp')
0 files changed, 0 insertions, 0 deletions