commit | 4b2cc484f9af46a82bd8e4f3ce81092c4eefa53a | [log] [tgz] |
---|---|---|
author | Roman Stratiienko <roman.o.stratiienko@globallogic.com> | Mon Feb 21 14:53:58 2022 +0200 |
committer | Roman Stratiienko <roman.o.stratiienko@globallogic.com> | Tue May 17 11:20:44 2022 +0300 |
tree | 2df796cb9c3415721f277d4ab9896df3d375e89a | |
parent | e9fbd8d626a22b58efd6d600662a9341e664400e [diff] |
drm_hwcomposer: Reorganize struct DrmHwcLayer 1. Move BlendMode, ColorSpace, SampleRange fields to the struct BufferInfo, allowing extraction of the data from native_handle using Metadata@4 API. Use it when data from HWC2 API can't be used (Currently it's a BlendMode case for CLIENT layer) 2. Rename DrmHwcLayer to LayerData and move it to compositor/ directory. (I was confused in the past because of similarity of names DrmHwcLayer vs HwcLayer, so this step should meke it easier for newcomers to understand the code) 3. Allow clonning of the LayerData to propagate it through the composition pipeline. Thus LayerData can be used by both HwcLayer to track state and by the compositor. Signed-off-by: Roman Stratiienko <roman.o.stratiienko@globallogic.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-14 -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!