diff options
| author | Rob Clark | 2016-11-05 15:52:01 +0100 |
|---|---|---|
| committer | Daniel Vetter | 2016-11-08 11:18:39 +0100 |
| commit | 7abc7d47510c75dd984380ebf819616e574c9604 (patch) | |
| tree | ce3b38a961ca8b8a3d39c54299957bb6864f7bf4 /drivers/gpu/drm/drm_atomic.c | |
| parent | drm/uapi: Add a warning that mode flags must match the xrandr definitions (diff) | |
| download | kernel-qcow2-linux-7abc7d47510c75dd984380ebf819616e574c9604.tar.gz kernel-qcow2-linux-7abc7d47510c75dd984380ebf819616e574c9604.tar.xz kernel-qcow2-linux-7abc7d47510c75dd984380ebf819616e574c9604.zip | |
drm: don't override possible_crtcs for primary/cursor planes
It is kind of a pointless restriction. If userspace does silly things
like using crtcA's cursor plane on crtcB, and then setcursor on crtcA,
it will end up with the overlay disabled on crtcB. But userspace is
allowed to shoot itself like this.
v2: don't WARN_ON() if caller did not set ->possible_crtcs. This keeps
the existing behavior by default, if caller does not set the
->possible_crtcs.
Signed-off-by: Rob Clark <robdclark@gmail.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Link: http://patchwork.freedesktop.org/patch/msgid/1478357521-26542-1-git-send-email-robdclark@gmail.com
Diffstat (limited to 'drivers/gpu/drm/drm_atomic.c')
0 files changed, 0 insertions, 0 deletions