From d11d83dee69f6a123f13312528839c4f1307f169 Mon Sep 17 00:00:00 2001 From: Valentine Burley Date: Fri, 31 Oct 2025 10:24:31 +0100 Subject: [PATCH] panfrost: Don't dump shader disassembly by default on CSF Dumping disassembly when not explicitly requested to do so was probably helpful during early CSF bringup. But the CSF code is relatively robust now, so let's move this to only happen if PAN_DBG_TRACE is set, similar to what we do in the JM backend. Signed-off-by: Valentine Burley Reviewed-by: Erik Faye-Lund Reviewed-by: Boris Brezillon Part-of: --- src/gallium/drivers/panfrost/pan_csf.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/src/gallium/drivers/panfrost/pan_csf.c b/src/gallium/drivers/panfrost/pan_csf.c index 7d9b2eebf56..c8688636224 100644 --- a/src/gallium/drivers/panfrost/pan_csf.c +++ b/src/gallium/drivers/panfrost/pan_csf.c @@ -615,10 +615,8 @@ csf_submit_wait_and_dump(struct panfrost_batch *batch, /* Jobs won't be complete if blackhole rendering, that's ok */ if (!ctx->is_noop && (dev->debug & PAN_DBG_SYNC) && - *((uint64_t *)batch->csf.cs.state.cpu) != 0) { + *((uint64_t *)batch->csf.cs.state.cpu) != 0) crash = true; - dump = true; - } if (dump) { const struct drm_panthor_queue_submit *qsubmits =