aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/devicetree
diff options
context:
space:
mode:
authorMaarten Lankhorst <maarten.lankhorst@linux.intel.com>2017-09-27 10:35:32 +0200
committerMaarten Lankhorst <maarten.lankhorst@linux.intel.com>2017-10-06 11:06:11 +0200
commit331494eb51002d0ee99414e3918e06d5e9a3962d (patch)
treec32d1bfea43da323fda926caa28bd6b9111c8a1a /Documentation/devicetree
parentdrm/atomic: Remove unneeded null check for private objects (diff)
downloadlinux-dev-331494eb51002d0ee99414e3918e06d5e9a3962d.tar.xz
linux-dev-331494eb51002d0ee99414e3918e06d5e9a3962d.zip
drm/atomic: Make atomic iterators less surprising
Commit 669c9215afea ("drm/atomic: Make async plane update checks work as intended, v2.") assumed incorrectly that if only 1 plane is matched in the loop, the variables will be set to that plane. In reality we reset them to NULL every time a new plane was iterated. This behavior is surprising, so fix this by making the for loops only assign the variables on a match. When we have not added all the planes/crtc/connector to the state, and there's a few NULL ones after the last one we iterated, te assumption is broken that the pointers will hold the values from the last loop iteration, which holds true for all other for_each macros we're using. Except of course the iterator pointer itself, but that one really is entirely internal. Cc: Dmitry Osipenko <digetx@gmail.com> Fixes: 669c9215afea ("drm/atomic: Make async plane update checks work as intended, v2.") Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20170927083532.5756-2-maarten.lankhorst@linux.intel.com Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch> Tested-by: Dmitry Osipenko <digetx@gmail.com>
Diffstat (limited to 'Documentation/devicetree')
0 files changed, 0 insertions, 0 deletions