Age | Commit message (Collapse) | Author | |
---|---|---|---|
2021-10-13 | SF: acquire/release screen for active display only | Ady Abraham | |
SurfaceFlinger assumes that there is at most a single internal display powered on at a given time, and mark it as the active display. However, in order to be robust against rare race conditions where displays might be on together for a short period of time, we add a check to make sure that we tell the scheduler that the screen was acquired/released only for the active display. Bug: 201605862 Test: SF unit tests Change-Id: I25b3f807d9f5d93ae88ac8a6026cee76cb69f493 | |||
2021-01-29 | SF: Query display modes only once during display creation / update | Marin Shalamanov | |
Currently HWComposer::getActiveMode / getModes is called multiple times when creating or updating a display. This is unnecessary and risky because the getActiveMode may return a different value if a hotplug event has ocured in between. In this CL we call getActiveMode and getModes only once and propagate the values using DisplayDeviceState. Bug: 159590486 Test: presubmit Change-Id: I97418163426a0ae19f79bc2912a7d725c953ad01 | |||
2020-10-09 | SF: Split DisplayTransactionTest | Marin Shalamanov | |
Test: atest libsurfaceflinger_unittests Change-Id: Ia29e8fa68ccd128923d52c33e106aafb6c5e9b9c |