We had some code that considered the possibility that the destination
might be linear when configuring TFU jobs, but we never actually allow
for this to happen since we avoid hitting these paths in that case, as
the TFU always produces UIF results. Instead, add an assert when
producing the TFU packet to ensure we are expecting a UIF result.
Reviewed-by: Alejandro PiƱeiro <apinheiro@igalia.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/15342>
dst->mem->bo->handle,
dst_offset,
dst_slice->tiling,
- dst_slice->tiling == V3D_TILING_RASTER ?
- dst_slice->stride : dst_slice->padded_height,
+ dst_slice->padded_height,
dst->cpp,
src->mem->bo->handle,
src_offset,
dst_bo->handle,
dst_offset,
slice->tiling,
- slice->tiling == V3D_TILING_RASTER ?
- slice->stride : slice->padded_height,
+ slice->padded_height,
image->cpp,
src_bo->handle,
src_offset,
dst->mem->bo->handle,
dst_offset,
dst_slice->tiling,
- dst_slice->tiling == V3D_TILING_RASTER ?
- dst_slice->stride : dst_slice->padded_height,
+ dst_slice->padded_height,
dst->cpp,
src->mem->bo->handle,
src_offset,
break;
}
+ /* The TFU can handle raster sources but always produces UIF results */
+ assert(dst_tiling != V3D_TILING_RASTER);
+
/* If we're writing level 0 (!IOA_DIMTW), then we need to supply the
* OPAD field for the destination (how many extra UIF blocks beyond
* those necessary to cover the height).