GraphicsComposerCallback Extend BnComposerCallback
-> This will ensure that callback can be used for the binder.
Test: atest VtsHalGraphicsComposer3_TargetTest
BUG: 202053621
Change-Id: I739217cc40ede49601446306bd6ce0029a77cfba
Test: atest VtsHalGraphicsComposer3_TargetTest, test are not run yet as we don't have the service yet.
BUG: 202446967
Change-Id: I5a9a807c8984cfc3db18440b6ee9ea2b43085324
If service exists then we can proceed with test otherwise tests will be skipped.
Test: atest VtsHalGraphicsComposer3_TargetTest but tests don't just work yet. as we don't have service implementation.
BUG: 202053621
NOTE: Efforts to migrate reader/writer based tests will be done under b/202765481
Composition tests will be migrate under b/202766745
CHECK: https://googleplex-android-review.git.corp.google.com/c/platform/hardware/interfaces/+/16202961/4..6
GetClientTargetSupport_2_2 and GetClientTargetSupport_2_2BadDisplay are removed as per b/203093280
Change-Id: I7bea002072390b9e19bf9fe31de00087cf4d0bf3
If service exists then we can proceed with test otherwise tests will be skipped.
Test: atest VtsHalGraphicsComposer3_TargetTest but tests don't just work yet. as we don't have service implementation.
BUG: 202053621
CHECK: https://googleplex-android-review.git.corp.google.com/c/platform/hardware/interfaces/+/16019271/3..8
NOTE: Efforts to migrate reader/writer based tests will be done under b/202549950
Change-Id: I1a515a8ce53f4d314d517272a81a9a504a144eb2
If service exists then we can proceed with test otherwise tests will be skipped.
Test: atest VtsHalGraphicsComposer3_TargetTest but tests don't just work yet. as we don't have service implementation.
BUG: 202053621
NOTE: Efforts to migrate reader/writer based tests will be done under b/202446967
CHECK: https://googleplex-android-review.git.corp.google.com/c/platform/hardware/interfaces/+/15987347/7..14
Change-Id: Ie7a81bbec463a471d9c88edf32cde6d86197991a
Test: atest VtsHalGraphicsComposer3_TargetTest but tests don't just work yet. as we don't have service implementation.
BUG: 202053621
Change-Id: I96fc1f6bcb4ce4907342b3a73994f80b9347ea9f
Create composer callback for tests.
Test: atest VtsHalGraphicsComposer3_TargetTest, test are not run yet but
BUG: 202401906
Change-Id: I87396cdae7d083a2d2529617648fdd784e9097db
use dupToAidl to store handles in the command writer instead of
makeToAidl, to match the HIDL behaviour
Bug: 198190384
Test: build
Change-Id: Idb46de2182048d4fb3d6b598246c62e1969f629b
HWC2_CAPABILITY_SKIP_VALIDATE was never defined for HIDL,
and instead there was a hack to just pass the value to the client
(see commit 6a05e9113a).
Test: build
Bug: 198690211
Change-Id: I2b06ad792237eb99e4dfe6b5c1ef808d5de45bd7
This reverts commit 37c5495c52.
This "clarification" was in fact a change of the HAL interface,
introducing a new requirement which was not present in earlier
Android releases. There are devices on the market that switch
seamlessly between configs that differ in resolution and DPI,
and therefore have those configs in a config group.
Bug: 200184776
Merged-In: I5bba1c6532f5f46da874385164a0bc0cc0435225
Change-Id: I5bba1c6532f5f46da874385164a0bc0cc0435225
This reverts commit 6f36dd6e31.
Differing only by vsync period was not a requirement on Android R, and
it shouldn't be added after-the-fact to an existing HAL version.
There are devices on the market that switch seamlessly between configs
that differ in resolution/dpi, and therefore have those configs in a
common group.
Bug: 200184776
Change-Id: Id0bfc67e55d5139fddb2b359cabafd9281c33734
This reverts commit 37c5495c52.
This "clarification" was in fact a change of the HAL interface,
introducing a new requirement which was not present in earlier
Android releases. There are devices on the market that switch
seamlessly between configs that differ in resolution and DPI,
and therefore have those configs in a config group.
Bug: 200184776
Test: m
Change-Id: I5bba1c6532f5f46da874385164a0bc0cc0435225
Check EXPECT_TRUE with status ok and Error none for valid display. and EXPECT_FALSE with status ok.
If service exists then we can proceed with test otherwise tests will be skipped.
Test: atest VtsHalGraphicsComposer3_TargetTest but tests don't just work yet. as we don't have service implementation.
BUG: 202053621
Change-Id: Iff8f4ca1e102ad8333ca63b0722b1fbd26414d06
* Add layer-level SDR white point. When there are mixed HDR/SDR layers
on the display, HDR layers should remain at display brightness, or
whatever the HDR standard is (e.g., keep HLG content at 1000 nits), while
SDR layers should be "dimmed" to the appropriate perceptual brightness.
* Add SDR white point to the client composited client target buffer.
When there are mixed HDR/SDR layers in client compostion, HWC must tell
SurfaceFlinger the target white point of the client target buffer so
that SurfaceFlinger-applied dimming may be atomically applied as a
brightness mode change.
Bug: 200310158
Test: builds
Change-Id: Ifbfe3125ede1a4de04978c6e644a5c911c33d3b6
If service exists then we can proceed with test otherwise we skip tests
This should help us write all the tests until we have the service implementation.
Test: atest VtsHalGraphicsComposer3_TargetTest Tests don't just work yet, we don't have service implemented yet.
BUG: 202053621
Change-Id: Ia9506dada0f1b5da446d6e2086aa4534c60d5565