summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/sti/sti_vtg.c
diff options
context:
space:
mode:
authorVille Syrjälä <ville.syrjala@linux.intel.com>2018-05-25 20:50:34 +0200
committerVille Syrjälä <ville.syrjala@linux.intel.com>2018-06-11 19:22:44 +0200
commit464ce098e69cf886ce99a08cb3ebf5f8c53820b5 (patch)
tree17572fd79f0f77acea4cc4ade2ec3fc7d4e00b3a /drivers/gpu/drm/sti/sti_vtg.c
parentdrm/vmwgfx: Stop using plane->fb in vmw_kms_atomic_check_modeset() (diff)
downloadlinux-464ce098e69cf886ce99a08cb3ebf5f8c53820b5.tar.xz
linux-464ce098e69cf886ce99a08cb3ebf5f8c53820b5.zip
drm/vmwgfx: Stop using plane->fb in vmw_kms_helper_dirty()
Instead of plane->fb (which we're going to deprecate for atomic drivers) we need to look at plane->state->fb. The maze of code leading to vmw_kms_helper_dirty() wasn't particularly clear, but my analysis concluded that the calls originating from vmw_*_primary_plane_atomic_update() all pass in the crtc which means we'll never end up in this branch of the function. All other callers use drm_modeset_lock_all() somewhere higher up, which means accessing plane->state is safe. v2: Drop the comment and make the code do what it did before (Thomas) v3: Drop the bogus lockdep assert Cc: Deepak Rawat <drawat@vmware.com> Cc: Thomas Hellstrom <thellstrom@vmware.com> Cc: Sinclair Yeh <syeh@vmware.com> Cc: VMware Graphics <linux-graphics-maintainer@vmware.com> Cc: Daniel Vetter <daniel.vetter@ffwll.ch> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20180525185045.29689-3-ville.syrjala@linux.intel.com Reviewed-by: Sinclair Yeh <syeh@vmware.com>
Diffstat (limited to 'drivers/gpu/drm/sti/sti_vtg.c')
0 files changed, 0 insertions, 0 deletions