As of VNDK deprecation, any libraries that defines vndk is no longer
valid anymore. This change removes all VNDK definition(s) from modules
which was VNDK.
Bug: 328994089
Test: AOSP CF build succeeded
Change-Id: Ifdade9c052db29c989ce7d804ba725361c4c0f8e
Merged-In: Ic4f19113c1a25dc1fb60cdfbf9c0f2d8d7d09726
This CL is created as a best effort to migrate test targets
to the new android ownership model. If you find incorrect or unnecessary
attribution in this CL, please create a separate CL to fix that.
For more details please refer to the link below,
<add g3 doc link>
Bug: 304529413
Test: N/A
Change-Id: I3322344f595f974f730dc824af0110388076d838
Ensure the primary display power on before run the
SetDisplayBrightness test item.
Bug: 313794734
Test: atest VtsHalGraphicsComposer3_TargetTest:PerInstance/
GraphicsComposerAidlCommandTest#SetDisplayBrightness/
0_android_hardware_graphics_composer3_IComposer_default
-- --abi arm64-v8a
Change-Id: I94fb700704bcbd8543f2a608dd75b9e745e40e37
Merged-In: I94fb700704bcbd8543f2a608dd75b9e745e40e37
* changes:
[Composer3-VTS] Test Composer3-V3 for refreshPeriodNanos and vsyncPeriodNanos
[HWC3] AIDL change to add refreshPeriodNanos to RefreshRateChangedDebugData
This CL adds the new aidl/apis for HWC command batching feature.
Bug: 290685621
Test: atest VtsHalGraphicsComposer3_TargetTest
atest PerInstance/GraphicsComposerAidlBatchedCommandTest
Change-Id: Ibccc2cb30954f5d054f8e45e59a0b831fd15a304
This CL adds the new aidl/apis for HWC command batching feature.
Bug: 290685621
Test: atest VtsHalGraphicsComposer3_TargetTest
atest PerInstance/GraphicsComposerAidlBatchedCommandTest
Change-Id: I9e8a8afefb03e04a4cd4d8db36d72e29d30e975f
IIUC, oneway makes the callback a non-blocking call. Hwcomposer
implementations are expected to call onHotplug/onHotplugEvent during
the initial hwcomposer->registerCallback(). However, a oneway callback
would not block and cause the hwcomposer's implementation of
registerCallback() to return immediately. Example log:
11-30 23:32:32.962 508 508 E RanchuHwc: registerCallback
11-30 23:32:32.962 508 508 E RanchuHwc: registerCallback:
display:0
11-30 23:32:32.962 508 508 E RanchuHwc: setCallbacks for display:0
11-30 23:32:32.962 508 508 E RanchuHwc: registerCallback:
display:1
11-30 23:32:32.962 508 508 E RanchuHwc: setCallbacks for display:1
11-30 23:32:32.962 508 508 E RanchuHwc: registerCallback initial
registration, hotplug connecting display:0
11-30 23:32:32.962 508 508 E RanchuHwc: registerCallback initial
registration, hotplug connecting display:1
11-30 23:32:32.962 572 592 E SurfaceFlinger: jasonjason
SurfaceFlinger::onComposerHalHotplugEvent()
11-30 23:32:32.962 572 572 F SurfaceFlinger: Initial display
configuration failed: HWC did not hotplug
11-30 23:32:32.962 572 592 E SurfaceFlinger: jasonjason SurfaceFlinger::onComposerHalHotplugEvent()
<SurfaceFlinger aborts from the Fatal "HWC did not hotplug">
Bug: b/314208907
Test: Launch Cuttlefish with ag/25521493 then
vts -m VtsHalGraphicsComposer3_TargetTest
Change-Id: Ibfea0b21e1d4c8b0de17bbe25dc55483050700b7
Introduce the concept of hdrSdrRatio for ClientTargets, so that:
* 1.0 is treated as SDR luminance
* hdrSdrRatio is provided to scale the content into display luminance
range during composition. That is, 1.0 maps to SDR max, and
hdrSdrRatio maps to display max luminance
Bug: 236745178
Test: builds
Change-Id: Id82a102eaca82f85bf3982538786dd2ae6cb8e61
When a display is connected, error may occur, this new api introduces
an event variable to specify the hotplug event, including errors.
This new api should be used, and the old onHotplug method is deprecated.
Bug: 241286153
Test: manual
Change-Id: I20ea685c5012015836024e7cab4dc0e68ebb835f
Originally landed as I5dbb01fc23abd5e0108c565f96d25e62c77fc16d and
previously reverted in I6265f8de3db31f07506906cee82a91fe3baac0bc due to
timeline constraints.
Add a test presenting from multiple threads. Split up execute() so that
it can be called for a single display. Update MultiThreadedPresent
(test) to offload presentDisplay to a separate thread, similar to how
Ib9d074671e32c95875ef7e0791dd95d6e595e47a does it, as described in
go/multi-threaded-present.
Bug: 259132483
Bug: 284156408
Fixes: 251842321
Fixes: 295841597
Test: VtsHalGraphicsComposer3_TargetTest
Change-Id: If975ee9bb0b9c6f64ef50401e2aee32f934e3f08
We deliberately use a deprecated API to test that it is not used. Ignore
warnings from using it in this test.
In PresentDisplayNoLayerStateChanges, remove the check for
SKIP_VALIDATE, removing the other warning. As written, the test would be
skipped without SKIP_VALIDATE support. But devices should *not* claim
Capability::SKIP_VALIDATE, meaning the test would always be skipped. The
docs state that the behavior previously indicated by SKIP_VALIDATE is
now the default, so we should always be running the test.
Bug: NA
Test: atest VtsHalGraphicsComposer3_TargetTest (no warnings)
Change-Id: Icc89a82b4850428c2f0940be0f78f5ebff1881b3
Right now this only makes sure that extended sRGB buffers aren't
corrupted by the time it hits the display. This is especially important
for Ultra HDR, because display compensation is defined by the spec.
Bug: 276331687
Bug: 259144781
Test: VtsHalGraphicsComposer3_ReadbackTest
Change-Id: Ib6c39858289d5559ae76280ca1a0ef756f2daef0
The nit information was used when we set exact nit values rather than a
relative brightness per layer. But we only need nit values for the
renderengine interface, which isn't tied to any hwc or panel
capabilities.
Bug: 301261125
Test: VtsHalGraphicsComposer3_TargetTest
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:712b3d9880b6aff51ab17d539bfcbdf3785cc6ca)
Merged-In: I770dc5620648df2eab608e030c5e76cf190f315d
Change-Id: I770dc5620648df2eab608e030c5e76cf190f315d
The nit information was used when we set exact nit values rather than a
relative brightness per layer. But we only need nit values for the
renderengine interface, which isn't tied to any hwc or panel
capabilities.
Bug: 301261125
Test: VtsHalGraphicsComposer3_TargetTest
Change-Id: I770dc5620648df2eab608e030c5e76cf190f315d
This reverts commit f850701be0.
Reason for revert: Delaying rename to avoid churn for external partner work.
Change-Id: If96786d074a61ac0f781540e98d020a6f7fd673b
Color management is now turned on by default, so there's no reason to
explicitly enable it in renderengine.
Bug: 295966830
Test: builds
Change-Id: I42c8afb30950081cd57072680da06895dcc02f2c
Test getDisplayConfigurations with vrr parameters
Test notifyExpectedPresent does not return error
Test: atest VtsHalGraphicsComposer3_TargetTest
BUG: 287517352
BUG: 284881912
Change-Id: I49d6876922e9fde47e531200a29413495458b8a5
