pan/cs: Fix cs_run_fragment() calls with swapped arguments

Fix non-functional issue where calls to cs_run_fragment() had swapped
tile_order and enable_tem arguments. Both arguments evaluate to 0.
Hence, no functional change.

Fixes: 53f780ec91 ("panfrost: Remove progress_increment from all CS builders")
Reviewed-by: Lars-Ivar Hesselberg Simonsen <lars-ivar.simonsen@arm.com>
Reviewed-by: Christian Gmeiner <cgmeiner@igalia.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/40840>
This commit is contained in:
Marc Alcala Prieto 2026-04-08 10:47:24 +02:00 committed by Marge Bot
parent eaf68f744b
commit 0d08b197f2

View file

@ -151,7 +151,7 @@ csf_oom_handler_init(struct panfrost_context *ctx)
/* Run the fragment job and wait */
cs_select_endpoint_sb(&b, 3);
cs_run_fragment(&b, MALI_TILE_RENDER_ORDER_Z_ORDER, false);
cs_run_fragment(&b, false, MALI_TILE_RENDER_ORDER_Z_ORDER);
cs_wait_slot(&b, 3);
/* Increment counter */
@ -877,7 +877,7 @@ GENX(csf_emit_fragment_job)(struct panfrost_batch *batch,
}
/* Run the fragment job and wait */
cs_run_fragment(b, MALI_TILE_RENDER_ORDER_Z_ORDER, false);
cs_run_fragment(b, false, MALI_TILE_RENDER_ORDER_Z_ORDER);
cs_wait_slot(b, 2);
/* Gather freed heap chunks and add them to the heap context free list