commit | 60f5e32d4bd25ab8248b6f2f6199854bcf96b55a | [log] [tgz] |
---|---|---|
author | John Stultz <john.stultz@linaro.org> | Mon Aug 27 22:24:40 2018 -0700 |
committer | John Stultz <john.stultz@linaro.org> | Tue Aug 28 14:28:39 2018 -0700 |
tree | c565c93a0ff6535859c7da39ab3039448335e19c | |
parent | 54589d28d0b1ed8e4ea9b20bee25258e2918eb3d [diff] |
drm_hwcomposer: Fixup Sean's HiSi dummy planner The dummy HiSi Planner is careful to not try to emplace layers that aren't HW_FB. However, in some cases we might have a single layer to draw. In that case the dummy importer will pretend it imported the buffer, and the planner will skip over it and not emplace it. Since there were no errors and the layers_ count is the same as the available planes, we won't force client composition, and will try to do device composition for the buffer we didn't really import. This results in the drm layer going a bit wonky. Thus, this patch tries to fix this by erroring out if we try to plan only a single layer, but don't emplace anything. This results in the CreateComposition() function failing, which will force client rendering, making it work (with only minimal logcat noise - only in the single layer case). Change-Id: I563dbba3c2adce5617fae61cb0440368053e5bff Signed-off-by: John Stultz <john.stultz@linaro.org>
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-3.5 -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!