Just to handle conflicts from internal
Test: make
Merged-In: I6fbc22272ba95b44aa09ff08f9d9a7adbb9ae8be
Change-Id: Ibe3ca5c654057b60fa9f045e6fc1f39d14463b44
This is just a minimal staging of go/oag/topic:"imapper5"
to handle the difference between AOSP's graphics-common
and internal's graphics-common
Test: make
Change-Id: I6fbc22272ba95b44aa09ff08f9d9a7adbb9ae8be
Add a new parameter and member to ComposerClient[Writer/Reader]
representing the only display it should apply to. The caller is
responsible for ensuring that they only ever refer to that same display.
The display is recorded here for error checking. This isn't strictly
necessary, but crashing here verifies that we only use the proper
display.
This is helpful for use with DisplayCapability.MULTI_THREADED_PRESENT,
although it is fine to use a single display per writer/reader without
the capability.
For the Reader, make the display optional, so that a single reader can
continue to be used for multiple displays. This allows devices without
the new DisplayCapability to continue to work without changes.
Remove copy constructor and operator=. Add a move constructor. This
ensures it will be properly moved when used in containers.
Bug: 241285491
Test: make
Change-Id: Ic7116e64138280747a32500c67dedeeabd7c669b
Remove all subfolder OWNERS in favor of single top-level
Update top-level OWNERS
Fixes: 230785548
Test: n/a
Change-Id: I9e4f4fa7938e31f0caf864836889f8ebb5ca5675
Util.h is not used in ComposerServiceWriter so it should not be
included. Otherwise when using ComposerServiceWriter, Util.h is not
found in the local directory.
Bug: 255623263
Test: m
Test: flashall to device
Change-Id: I4ce57b37d6a9a899d114e5ac64d443cfa51d826a
Merged-In: I4ce57b37d6a9a899d114e5ac64d443cfa51d826a
Util.h is not used in ComposerServiceWriter so it should not be
included. Otherwise when using ComposerServiceWriter, Util.h is not
found in the local directory.
Bug:255623263
Test: m
Test: flashall to device
Change-Id: I4ce57b37d6a9a899d114e5ac64d443cfa51d826a
Also update composer3 to the latest version.
Begin writing a test.
Bug: 241285491
Test: atest VtsHalGraphicsComposer3_TargetTest:GraphicsComposerAidlCommandTest.MultiThreadedPresent
Change-Id: I5dbb01fc23abd5e0108c565f96d25e62c77fc16d
- add new VTS for new AIDL interface/API. Disable this new vts case for
now due to no implementation on cuttlefish.
- rev up android.hardware.graphics.composer3-V1-ndk to V2 version.
Bug: 242588489
Test: build, atest VtsHalGraphicsComposer3_TargetTest
Change-Id: I5a5c0d52d7b64d927d211abf77f534f37c4d65d0
This class has no other virtual methods, and it has no subclasses, so
it's unclear why it had a virtual destructor.
Bug: NA
Test: make
Change-Id: Ic87fe6596b6d796ca11822de53af2e4e521f127d
... by updating the toYCbCrLayout function to more closely follow
the requirements found in the comments of `android_flex_plane_t`.
Bug: b/244411455
Test: untested.
Change-Id: I1173253e25583336bf480160d4f6ac9f72882971
interfaces.
- Add new Android.bp in graphics folder and wrap composer and common
AIDL in to separate cc_defaults.
- remove composer3 dependency from allocator's VTS .bp file.
Bug: 243429120
Test: builds
Change-Id: Ia91e4ab87b7ac86248094317185b317d5604e654
When we run the VTS of GraphicsComposerAidlCommandTest, we always meet
segmentation fault issue in some test items. VTS test items crashed
when it deleted the layer or display from resource manager and try to
go next loop.
The problem is the test item try to delete the layer iterator or
display iterator in the loop, so the iterator become an invalid
iterator. Then it try to use the invalid iterator for going to next
iterator. This behavior caused segmentation fault. We use different
way to fix deleting layer and deleting display.
Delete layer: Test item always delete all layer for each display, so
we always delete layer via get the first iterator until
the resource manager is empty.
Delete display: Test item only delete virtual display, so we move the
physical display to a temporary map. After delete all
virtual display, we swap the temporary map and
original map.
Bug: 243781450
Test: 1. test GraphicsComposerAidlCommandTest.SetLayerColorTransform
for deleting layer
2. test GraphicsComposerAidlCommandTest.SetOutputBuffer
for deleting disply
Change-Id: Id467df658e78ed29fdfc039cabc119f8bf62d69d
Some HW may not support crop function for decoration and current API
can't query this capability. Configure decoration layer to full screen
to avoid this limitation.
Bug: 225765061
Test: VtsHalGraphicsComposer3_TargetTest
--gtest_filter=*DisplayDecoration*
Change-Id: If47154adf9d48f9c1b8390b4bee090d8bf40ff3b
(cherry picked from commit 7d55d4269d)
Merged-In: If47154adf9d48f9c1b8390b4bee090d8bf40ff3b
(cherry picked from commit 308f4ac906)
Merged-In: If47154adf9d48f9c1b8390b4bee090d8bf40ff3b
