Google Git
Sign in
chromium / chromium / src / 6cac2145576d57b47e2ac5977f7c33dae78faffc
commit6cac2145576d57b47e2ac5977f7c33dae78faffc[log] [tgz]
authorSu Hong Koo <sukoo@chromium.org>Wed Aug 07 23:12:49 2024
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Aug 07 23:12:49 2024
tree2bcf997af7f59cd347041795f8afdb0bc16afacc
parent4ba7484a51a439788ad8702e6e29180a034bd597 [diff]
[5/12] ozone/drm: Add tiled display support to DrmDisplay

Refactor DrmDisplay to support representation of tiled displays. Tiled
displays are composed of multiple CRTC/connectors, while DrmDisplay
only supported having 1 CRTC/connector pair.

DrmDisplay was modified to hold a vector of CrtcConnectorPair, a
wrapper struct that holds CRTC and connector info that corresponds to
what was crtc_ and connector_ in DrmDisplay.

DrmDisplay can create multiple CrtcConnectorPairs if the display info
that was passed in has nonprimary tile infos.

DrmDisplay now also has a concept of a primary CRTC/connector.
For nontiled displays, there will only be one CrtcConnectorPair, which
will be the primary. For tiled displays, the primary will be the
CrtcConnectorPair with the same tile location as the display_snapshot
pass into the constructor.

Note that the multiple CRTC/connector pairs available in DrmDisplay is
not propagated downstream to ScreenManager and
HardwareDisplayController in this CL. HardwareDisplayController will
still only has the primary CRTC/connector as its sole CrtcController.
The propagation is done in a subsequent CL.

All color related Set*() functions will now apply to all
CrtcConnectorPairs.

This CL does not add HDCP support for tiled displays.

Bug: b:285923912, b:324237063
Test: ozone_unittests
Change-Id: Ia982a5d7732f038e9a191ba4855ccf34fc4fc231
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5075441
Reviewed-by: Gil Dekel <gildekel@chromium.org>
Commit-Queue: Su Hong Koo <sukoo@chromium.org>
Reviewed-by: Sasha McIntosh <sashamcintosh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1338766}
8 files changed
tree: 2bcf997af7f59cd347041795f8afdb0bc16afacc
  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. clank
  52. internal
  53. ios_internal
  54. native_client
  55. signing_keys
  56. v8
  57. .clang-format
  58. .clang-tidy
  59. .clangd
  60. .eslintrc.js
  61. .git-blame-ignore-revs
  62. .gitallowed
  63. .gitattributes
  64. .gitignore
  65. .gitmodules
  66. .gn
  67. .mailmap
  68. .rustfmt.toml
  69. .vpython3
  70. .yapfignore
  71. ATL_OWNERS
  72. AUTHORS
  73. BUILD.gn
  74. CODE_OF_CONDUCT.md
  75. codereview.settings
  76. CPPLINT.cfg
  77. DEPS
  78. DIR_METADATA
  79. LICENSE
  80. LICENSE.chromium_os
  81. OWNERS
  82. PRESUBMIT.py
  83. PRESUBMIT_test.py
  84. PRESUBMIT_test_mocks.py
  85. README.md
  86. 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.