commit | 00d85d2158a486a4714e4bee13329c84c30a10ee | [log] [tgz] |
---|---|---|
author | Su Hong Koo <sukoo@chromium.org> | Tue Jun 04 14:23:35 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jun 04 14:23:35 2024 |
tree | 69736d5f1db6a9d2ccf6b309be113cb78ac25734 | |
parent | 146929ca4035a145ce41befe5f8625aa54b2ca49 [diff] |
ozone/drm: Introduce TileProperty to HardwareDisplayControllerInfo TileProperty is a new struct that represents various information about a connector that belongs to a tiled display. TileProperty is parsed from TILE connector property and DisplayID. TileProperty contains information like ID, layout of the tiles, location of the tile corresponding to the connector, tile size, etc. HardwareDisplayControllerInfo represents information required to initialize and configure a native display. If tiled display support flag is enabled, GetDisplayInfosAndInvalidCrtcs() will now populate information about tiled display in HardwareDisplayControllerInfo. Currently, each tile in a tiled display correspond to one HardwareDisplayControllerInfo, which leads to each of the tiles being represented as individual DisplaySnapshot (and therefore displays) throughout the display stack. This change adds logic to DrmGpuDisplayManager::GetDisplays() to consolidate multiple HardwareDisplayControllerInfo for a tiled display into one. For now, only one HDCI with tile location closest to origin is kept per tiled display. The logic to consolidate HDCIs will be fleshed out in future CLs as per go/cros-tile-display-support. Bug: b:285923912, b:324236939 Test: display_unittests, ozone_unittests, and manual testing of the entire CL chain Change-Id: I72ddc829a5c45255c3bc7722877f751c8c439b2f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5473092 Reviewed-by: Gil Dekel <gildekel@chromium.org> Commit-Queue: Su Hong Koo <sukoo@chromium.org> Cr-Commit-Position: refs/heads/main@{#1309937}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.