For targets that do not support display post processing, setting of
color modes is a no-op. The inclusion of the default Identity color
mode in the color transform map will be avoided when the flag
TARGET_EXCLUDES_DISPLAY_PP is set in order to signify that no color
modes are supported when PP features are not supported in the target
Change-Id: If3929b38ec7a093498c404da1798eaccbc97a281
Validate values read from input parcel as part of handling of
few qclient methods
Change-Id: Icf928f409a5c2ac76a73e95de58cb0ebc59d24d5
CRs-Fixed: 2114346
- Legacy hal doesn't maintaining two different
modes like doze and doze_suspend.
- Legacy hal uses FB_BLANK_VSYNC_SUSPEND.
CRs-Fixed: 2140924
Change-Id: I080b43089d335eff65c29de60c67112d5a4f1dd9
We don't know how to handle blending when scRGB layers show up.
Fallback entirely to GPU.
Bug: 72125973
Change-Id: Ib01ac0c920bd34f011f0a4d3e76e71d4c7b036e2
Publicly visible headers of the lib uses other headers from liblog and
libhardware. Therefore, explicitly export the required headers so that
the client that is using this library doesn't need to add additional
dependency.
Bug: 69526027
Test: mma -j under libgralloc1
Change-Id: I532bc43e0d8ff428008709d95983ec98342017d8
When the vndk is enabled (BOARD_VNDK_VERSION=current),
vendor libraries must only link against vendor variants
in the build system. This also means that they receive
restricted sets of headers and that automatic global
headers are restricted.
Test: build libqservice with BOARD_VNDK_VERSION=current
Bug: 69526027
Change-Id: Id98bf5e2ecc6f514f1d4dd9580d25027f36e0d86
When the vndk is enabled (BOARD_VNDK_VERSION=current),
vendor libraries must only link against vendor variants
in the build system. This also means that they receive
restricted sets of headers and that automatic global
headers are restricted.
Test: build memtrack with BOARD_VNDK_VERSION=current
Bug: 69526027
Change-Id: Ie3cb9ffb72931fbb0cc816f5158a649e09f7bb43
When the vndk is enabled (BOARD_VNDK_VERSION=current),
vendor libraries must only link against vendor variants
in the build system. This also means that they receive
restricted sets of headers and that automatic global
headers are restricted.
Test: build light with BOARD_VNDK_VERSION=current
Bug: 69526027
Change-Id: I8ad1da8aa2802a93493c877644266995c59f18ab
The ClearRequestFlags() method iterates over layer_stack_ instead of
layer_set_. This causes a use-after-free since DestroyLayer() removes
layer from layer_set_ only. Besides that, the method need not be
virtual and has a redundant loop. This change removes the
ClearRequestFlags() method and clears flags in an existing loop.
Present() bails out if layer_set_ is empty or a shutdown is pending.
Since layers could have been destroyed before Present(), ideally
bailing out on re-validation has a higher priority over the rest.
Bug: 71538967
Change-Id: Ic7b31bbd07a22b8df47fccb2024b3415ab3a559b
CRs-fixed: 2165926
Acked-by: Saurabh Shah <saurshah@codeaurora.org>
android-build-team Robot
Alexey Polyudov
Ch Ganesh Kumar
Rohit Kulkarni
Ramkumar Radhakrishnan
Saurabh Shah
Chong Zhang
Alain Vongsouvanh
Rajavenu Kyatham
Sundara Vinayagam
gitbuildkicker
Naseer Ahmed
Adrian Salido
Jiyong Park
TreeHugger Robot
Steven Moreland
Martin Brabham
Dan Albert
Andreas Gampe
Chih-Hung Hsieh