From 0b8007b52316f76c76ca05846c858055f0cc9e38 Mon Sep 17 00:00:00 2001 From: Eric Anholt Date: Thu, 13 Sep 2018 12:59:13 -0700 Subject: v3d: Stop clearing the OQ state at the end of the job. Ever since we added OQ support, we've been clearing OQ state at the start of the job anyway. We're intentionally breaking old-and-new-driver-mix systems, because we need to stop using the unvalidated FLUSH_ALL_STATE. --- src/gallium/drivers/v3d/v3d_context.h | 7 ------- 1 file changed, 7 deletions(-) (limited to 'src/gallium/drivers/v3d/v3d_context.h') diff --git a/src/gallium/drivers/v3d/v3d_context.h b/src/gallium/drivers/v3d/v3d_context.h index 20f357ae4a8..70643e000b0 100644 --- a/src/gallium/drivers/v3d/v3d_context.h +++ b/src/gallium/drivers/v3d/v3d_context.h @@ -300,13 +300,6 @@ struct v3d_job { */ bool needs_flush; - /** - * Set if there is a nonzero address for OCCLUSION_QUERY_COUNTER. If - * so, we need to disable it and flush before ending the CL, to keep - * the next tile from starting with it enabled. - */ - bool oq_enabled; - /** * Set if a packet enabling TF has been emitted in the job (V3D 4.x). */ -- cgit v1.2.3