drm/vmwgfx: Reorder device takedown somewhat
authorThomas Hellstrom <thellstrom@vmware.com>
Thu, 5 Mar 2015 10:33:24 +0000 (02:33 -0800)
committerBen Hutchings <ben@decadent.org.uk>
Sat, 9 May 2015 22:16:29 +0000 (23:16 +0100)
commit2269bf3c2fb60c8d6e1511f55e7f1b08e82e252b
tree74cc773dfe4753732a6dc16d878ed599eaa0200f
parent6dc77dfffb8317d01fc9c2d25d0288c7b31b8623
drm/vmwgfx: Reorder device takedown somewhat

commit 3458390b9f0ba784481d23134798faee27b5f16f upstream.

To take down the MOB and GMR memory types, the driver may have to issue
fence objects and thus make sure that the fence manager is taken down
after those memory types.
Reorder device init accordingly.

Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
Reviewed-by: Sinclair Yeh <syeh@vmware.com>
[bwh: Backported to 3.2:
 - Adjust context
 - Only the GMR memory type is used]
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c