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}
10 files changed
tree: 69736d5f1db6a9d2ccf6b309be113cb78ac25734
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. webkit/
  51. .clang-format
  52. .clang-tidy
  53. .clangd
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitallowed
  57. .gitattributes
  58. .gitignore
  59. .gitmodules
  60. .gn
  61. .mailmap
  62. .rustfmt.toml
  63. .vpython3
  64. .yapfignore
  65. ATL_OWNERS
  66. AUTHORS
  67. BUILD.gn
  68. CODE_OF_CONDUCT.md
  69. codereview.settings
  70. CPPLINT.cfg
  71. DEPS
  72. DIR_METADATA
  73. LICENSE
  74. LICENSE.chromium_os
  75. OWNERS
  76. PRESUBMIT.py
  77. PRESUBMIT_test.py
  78. PRESUBMIT_test_mocks.py
  79. README.md
  80. WATCHLISTS
README.md

Logo Chromium

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.