| commit | 97b5abc501dca66848fd5eb47d7be47c194d62dc | [log] [tgz] |
|---|---|---|
| author | Drew Davenport <ddavenport@google.com> | Thu Nov 07 10:43:54 2024 -0700 |
| committer | Drew Davenport <ddavenport@google.com> | Thu Nov 14 10:51:34 2024 -0700 |
| tree | 77bbf2fd431df6bf849665e5862a039d252c5bfc | |
| parent | 897a709d0bcdc8377f7a43f54a6bd1b9efc8964b [diff] |
drm_hwcomposer: Add blocking SetConfig Config changes within the same config group are intended to change the refresh rate and are expected to be seamless, and as such are queued up to be applied along with other frame updates such as pageflips. These commits ought not to result in a full modeset. For config changes that go between config groups, there might be visible artifacts (modesets). Introduce HwcDisplay::SetConfig to implement support for changing between config groups. Config changes that are expected to be seamless and not introduce jank or other visual artifacts should continue to go through HwcDisplay::QueueConfig. Since there may not be an appropriate client buffer available for the initial SetConfig, allocate a CPU-writable buffer for scanout that can be used for the first commit. The buffer can be destroyed after the next frame is presented. Change-Id: I48a87a070130dd2328f415719032486d9659c5b6 Signed-off-by: Drew Davenport <ddavenport@google.com>
Patches to drm_hwcomposer are very much welcome, we really want this to be the universal HW composer implementation for Android and similar platforms. So please bring on porting patches, bugfixes, improvements for documentation and new features.
A short list of contribution guidelines:
Submit changes via gitlab merge requests on gitlab.freedesktop.org.
drm_hwcomposer is Apache 2.0 Licensed and we require contributions to follow the developer's certificate of origin: http://developercertificate.org/.
When submitting new code please follow the naming conventions documented in the generated documentation. Also please make full use of all the helpers and convenience macros provided by drm_hwcomposer. The below command can help you with formatting of your patches:
git diff | clang-format-diff-19 -p 1 -style=file
Hardware specific changes should be tested on relevant platforms before committing.
If you need inspiration, please checkout our TODO issues.
Happy hacking!