drm/etnaviv: remove -EAGAIN handling from submit path

Now that the userptr BO handling doesn't rely on the userspace restarting
the submit after object population, there is no need to special case the
-EAGAIN return value anymore.

Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de>

diff --git a/drivers/gpu/drm/etnaviv/etnaviv_gem_submit.c b/drivers/gpu/drm/etnaviv/etnaviv_gem_submit.c
index ff911541a190a4819e0809ea60159c0e08d3f6e0..8fa31ab1fb0a4ebff70e89d0379d05d14ac91751 100644 (file)
--- a/drivers/gpu/drm/etnaviv/etnaviv_gem_submit.c
+++ b/drivers/gpu/drm/etnaviv/etnaviv_gem_submit.c
@@ -534,14 +534,6 @@ int etnaviv_ioctl_gem_submit(struct drm_device *dev, void *data,
 out:
        submit_unpin_objects(submit);
 
-       /*
-        * If we're returning -EAGAIN, it may be due to the userptr code
-        * wanting to run its workqueue outside of any locks. Flush our
-        * workqueue to ensure that it is run in a timely manner.
-        */
-       if (ret == -EAGAIN)
-               flush_workqueue(priv->wq);
-
 err_submit_objects:
        if (in_fence)
                dma_fence_put(in_fence);