diff options
author | Gabriel Krisman Bertazi | 2017-02-16 17:44:42 +0100 |
---|---|---|
committer | Daniel Vetter | 2017-02-26 21:57:24 +0100 |
commit | cd2523569a733d85788b6fc016e4e23cb3549a25 (patch) | |
tree | 378a35ff0ea197ed9cee5bbe4d73108df23b87c6 /firmware | |
parent | drm: drm_printer: add __printf validation (diff) | |
download | kernel-qcow2-linux-cd2523569a733d85788b6fc016e4e23cb3549a25.tar.gz kernel-qcow2-linux-cd2523569a733d85788b6fc016e4e23cb3549a25.tar.xz kernel-qcow2-linux-cd2523569a733d85788b6fc016e4e23cb3549a25.zip |
drm: Always prepare null framebuffer in transitional helper
Despite the documentation claim that cleanup_fb will match prior calls
to prepare_fb, in case of NULL framebuffers in the transitional helpers,
the code will skip the call to prepare_fb but not the corresponding
cleanup_fb call. This asymmetry in semantics is unnecessarily surprising
for developers transitioning drivers to atomic model, specially because
the final atomic handlers don't have the issue - the prepare_fb is
always called, despite the new state framebuffer being null.
The only current user of the transitional helper that doesn't take care
of null framebuffers explicitly inside the prepare_fb hook is
atmel_hlcdc, so we take special care to make sure we don't break
anything there.
Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.co.uk>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Link: http://patchwork.freedesktop.org/patch/msgid/20170216164442.28704-1-krisman@collabora.co.uk
Diffstat (limited to 'firmware')
0 files changed, 0 insertions, 0 deletions