drm/vmwgfx: Get rid of the device-private suspended member
authorThomas Hellstrom <thellstrom@vmware.com>
Thu, 22 Mar 2018 09:30:19 +0000 (10:30 +0100)
committerThomas Hellstrom <thellstrom@vmware.com>
Thu, 22 Mar 2018 11:08:23 +0000 (12:08 +0100)
commit4e3e733b45df457147441b79cf2cb654c82ec402
treebc9abfd0127974426265ee0f89cfe7028e4926e2
parentc3b9b165734492b7e42bdd898aba93e1120f9084
drm/vmwgfx: Get rid of the device-private suspended member

It was used to early block fbdev dirty processing. Replace it with an
unprotected check of the par->dirty.active field. While this might
race with the vmw_fb_off() function, we do a protected check later so
the race will at worst lead to grabbing and releasing a couple of locks.

Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
Reviewed-by: Brian Paul <brianp@vmware.com>
Reviewed-by: Sinclair Yeh <syeh@vmware.com>
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
drivers/gpu/drm/vmwgfx/vmwgfx_fb.c