diff options
| author | Vishnu Nair <vishnun@google.com> | 2020-10-22 17:41:30 -0700 |
|---|---|---|
| committer | Vishnu Nair <vishnun@google.com> | 2020-10-22 18:03:22 -0700 |
| commit | ce1a64848444719eef38f1c65a725ff2b5dbbbd2 (patch) | |
| tree | 7148f59fd212a5cdba1369fce1f1ea3054e791dc /PREUPLOAD.cfg | |
| parent | d544d34cd2900fb3fb5cfc269f8cb260c526df6e (diff) | |
Allow creating child surfaces from BlastBufferQueue
App such as Chrome create child surfaces and parent them to
surfaces provided by SurfaceView. When we enable the blast
adapter for SurfaceView, the IGBP returned to the app is
created in the client and SurfaceFlinger does not know about it.
When the app creates a child surface and provides the IGBP as the
parent surface identifier, SF fails to validate the IGBP and the
surface is not created. This can be avoid if the client creates the
child surface from the SV SurfaceControl but we still need to
support existing APIs.
To fix this, when we create a Surface from the adapter, pass in
the handle of the Blast SurfaceControl. When calling
ASurfaceControl_createFromWindow, use this handle to identify
the parent.
Bug: 168917217
Test: adb shell settings put global use_blast_adapter_sv 1 & launch chrome
Change-Id: I879b411c47e8558397516bd7b7278813e79e005f
Diffstat (limited to 'PREUPLOAD.cfg')
| -rw-r--r-- | PREUPLOAD.cfg | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/PREUPLOAD.cfg b/PREUPLOAD.cfg index f66d12a69594..cdf5df6c6bd3 100644 --- a/PREUPLOAD.cfg +++ b/PREUPLOAD.cfg @@ -9,6 +9,7 @@ clang_format = --commit ${PREUPLOAD_COMMIT} --style file --extensions c,h,cc,cpp cmds/uinput/ core/jni/ libs/input/ + native/ services/core/jni/ services/incremental/ tests/ |