History log of /frameworks/native/services/surfaceflinger/tests/fakehwc/FakeComposerClient.h
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
513476ab1802bf315d70a854512f4940a035fcf9 31-Jan-2018 Chia-I Wu <olv@google.com> fakehwc, libvr_hwc-hal: update for ComposerHal changes

removeClient and enableCallback are removed. dumpDebugInfo,
registerCallback, and unregisterCallback are added.

Test: builds
Change-Id: If366fb24b555393abe5c7bf326027c30c3ceafa4
/frameworks/native/services/surfaceflinger/tests/fakehwc/FakeComposerClient.h
29e146b284b74ae65670a3a4f3698cd9ee155f1d 30-Jan-2018 Chia-I Wu <olv@google.com> fakehwc, libvr_hwc-hal: ComposerClient is moved

ComposerClient is moved to another library with some changes. This
allows us to kill the has-a relation between VrComposerClient and
ComposerClientImpl in VR.

Test: builds
Change-Id: I0c32386f7d62f33e2e4d1271be42953f6880fd75
/frameworks/native/services/surfaceflinger/tests/fakehwc/FakeComposerClient.h
d15d2d2ee3a3f990412c26cfb82d9cce1cac6aee 29-Jan-2018 Chia-I Wu <olv@google.com> fakehwc, libvr_hwc-hal: ComposerBase is moved

ComposerBase is moved to another library and is renamed to
ComposerHal.

Test: builds
Change-Id: Ie9159b9d83558587d75aa6d0ad89a1848a281d01
/frameworks/native/services/surfaceflinger/tests/fakehwc/FakeComposerClient.h
2ae2b3bd5bfbacc3b52f222441bfbbeb9bd54dc7 15-Dec-2017 Lloyd Pique <lpique@google.com> Allow a primary display disconnect

This patch forwards the primary display disconnect event to the
Framework, and otherwise ensures that SurfaceFlinger does not crash
while there is no primary display.

Note that the Framework does not yet accept this change. In particular
the ActivityManager ActivityStackSupervisor code promptly asserts that
one cannot remove the primary display. With this assertion disabled, the
framework does not crash (surprisingly). And if the Framework
subsequently receives a primary display connect event, it does not seem
to do anything useful -- the display remains in a default off state, and
no layer stack/viewport/etc is set on it.

Bug: 38464421
Test: Works (with workarounds as noted) on a Chromebook
Test: Added Unit test passes on Pixel 1 XL

Change-Id: Ia11439030efdc53bc17474b71a0ffb3d3085bb49
/frameworks/native/services/surfaceflinger/tests/fakehwc/FakeComposerClient.h
9c5795640b7a03541ec31b93b6a3217709599a8d 21-Dec-2017 Chia-I Wu <olv@google.com> Merge "surfaceflinger: do not check HWC2::Capability::SkipValidate" am: c770d27ff0 am: 45f9c3871b
am: 7fef217993

Change-Id: Id58026df73f211769764537f5648b83ff6b1b568
41b98d41f9f4e94a1a9a31960a317649cbec3b09 11-Dec-2017 Chia-I Wu <olv@google.com> surfaceflinger: do not check HWC2::Capability::SkipValidate

HWC2::Capability::SkipValidate is not defined in HIDL. We cannot
check against it.

Besides, presentOrValidate is equivalent to validate in HIDL when
the underlying hwcomposer2 implementation does not support the cap.
There is not need to check against it.

Bug: 70407085
Test: boots
Change-Id: Ib0c11e99ce3389ad555605de18e194d9b51b2bc0
/frameworks/native/services/surfaceflinger/tests/fakehwc/FakeComposerClient.h
83ce7c162855742a2d9eeebc0cd70fe48d2cd125 20-Oct-2017 Chia-I Wu <olv@google.com> surfaceflinger: remove USE_HWC2

Remove USE_HWC2 and assume it to be true. Remove all !USE_HWC2
code.

This also fixes a compile error in tests/fakehwc, which never
defines USE_HWC2.

Test: boots taimen and hikey960
Change-Id: Ie6d2fcf884aa6fc715ab0ce19a1e0f7c8acf734c
/frameworks/native/services/surfaceflinger/tests/fakehwc/FakeComposerClient.h
a7de594782a5a7fcfd0300117f362f173631e1af 08-Aug-2017 Kalle Raita <kraita@google.com> Use HWC_DISPLAY_PRIMARY and _EXTERNAL

Some of the code in the SurfaceFlinger and VR composer assume that the
composer has display IDs HWC_DISPLAY_PRIMARY and HWC_DISPLAY_EXTERNAL
for those specific displays. Modify test to follow the requirement.

Bug: 64446190
Test: Run the test on Marlin
Change-Id: I7fef17158d62bd7cd242b97d37724a229f9c7418
/frameworks/native/services/surfaceflinger/tests/fakehwc/FakeComposerClient.h
a099a24c93bfa599fc5c36a647e946c26f68514f 11-Jan-2017 Kalle Raita <kraita@google.com> Faked HWC for SurfaceFlinger testing

Infrastructure and initial port of transaction tests. Faking the HWC
allows exercising the real path through the SurfaceFlinger, not relying
on screen captures. Faked HWC also opens up the possibility of faking
interactions like display hotplugs.

The tests are verifying the composition rectangles instead of a set of
select pixels. GLES rendering differences won't affect the
results. Also, the test expectations become clearer.

The ported transaction tests ran roughly twice as fast when compared
with the original transaction test. This is mostly due to the thighter
control over the vsyncs.

Test: Running the test on Marlin
Change-Id: I1c876cda78db94c1965498af957e64fdd23459ce
/frameworks/native/services/surfaceflinger/tests/fakehwc/FakeComposerClient.h