forked from Minki/linux
464ce098e6
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> |
||
|---|---|---|
| .. | ||
| device_include | ||
| Kconfig | ||
| Makefile | ||
| vmwgfx_binding.c | ||
| vmwgfx_binding.h | ||
| vmwgfx_blit.c | ||
| vmwgfx_buffer.c | ||
| vmwgfx_cmdbuf_res.c | ||
| vmwgfx_cmdbuf.c | ||
| vmwgfx_context.c | ||
| vmwgfx_cotable.c | ||
| vmwgfx_dmabuf.c | ||
| vmwgfx_drv.c | ||
| vmwgfx_drv.h | ||
| vmwgfx_execbuf.c | ||
| vmwgfx_fb.c | ||
| vmwgfx_fence.c | ||
| vmwgfx_fence.h | ||
| vmwgfx_fifo.c | ||
| vmwgfx_gmr.c | ||
| vmwgfx_gmrid_manager.c | ||
| vmwgfx_ioctl.c | ||
| vmwgfx_irq.c | ||
| vmwgfx_kms.c | ||
| vmwgfx_kms.h | ||
| vmwgfx_ldu.c | ||
| vmwgfx_marker.c | ||
| vmwgfx_mob.c | ||
| vmwgfx_msg.c | ||
| vmwgfx_msg.h | ||
| vmwgfx_overlay.c | ||
| vmwgfx_prime.c | ||
| vmwgfx_reg.h | ||
| vmwgfx_resource_priv.h | ||
| vmwgfx_resource.c | ||
| vmwgfx_scrn.c | ||
| vmwgfx_shader.c | ||
| vmwgfx_simple_resource.c | ||
| vmwgfx_so.c | ||
| vmwgfx_so.h | ||
| vmwgfx_stdu.c | ||
| vmwgfx_surface.c | ||
| vmwgfx_ttm_glue.c | ||
| vmwgfx_va.c | ||