drm/radeon: fix order of doing things in radeon_crtc_cursor_set

if object pin or object lookup in radeon_cursor_set fail, the function
could leave inconsistent mouse width and hight values in radeon_crtc
fixed by moving cursor width and height assignments after all
checks have passed

Signed-off-by: Ilija Hadzic <[e-mail]>
Reviewed-by: Alex Deucher <[e-mail]>
Signed-off-by: Dave Airlie <[e-mail]>

drivers/gpu/drm/radeon/radeon_cursor.c

···
 		return -EINVAL;
 	}
 
-	radeon_crtc->cursor_width = width;
-	radeon_crtc->cursor_height = height;
-
 	obj = drm_gem_object_lookup(crtc->dev, file_priv, handle);
 	if (!obj) {
 		DRM_ERROR("Cannot find cursor object %x for crtc %d\n", handle, radeon_crtc->crtc_id);
···
 	ret = radeon_gem_object_pin(obj, RADEON_GEM_DOMAIN_VRAM, &gpu_addr);
 	if (ret)
 		goto fail;
+
+	radeon_crtc->cursor_width = width;
+	radeon_crtc->cursor_height = height;
 
 	radeon_lock_cursor(crtc, true);
 	/* XXX only 27 bit offset for legacy cursor */