Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
ui/ozone: Update DrmDisplays during conflict resolution
Patch https://crrev.com/c/3032738 introduced logic to detect and resolve EDID-based display ID collisions in freshly created DisplaySnapshots, but neglected to update the underlying DrmDisplays in Ozone. This CL is rectifying this oversight. In addition, it resolves similar conflicts during initialization, when dummy display representations are created while the GPU process is coming online. Of note, this CL separates DisplaySnapshot creation from DrmDisplay object state updates. This allows us to resolve the collisions before caching the new display ID within each DrmDisplay representation. Bug: b:193019614, b:193027414 Test: display_unittests && ozone_unittests Change-Id: I274f6912a9c8cf1d9b08e30406eed80077a2ed9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4071916 Commit-Queue: Gil Dekel <gildekel@chromium.org> Reviewed-by: Daniel Nicoara <dnicoara@chromium.org> Cr-Commit-Position: refs/heads/main@{#1078439}
- Loading branch information
Gil Dekel
authored and
Chromium LUCI CQ
committed
Dec 2, 2022
1 parent
75774f7
commit 8b1c513
Showing
5 changed files
with
77 additions
and
43 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters