From 3b9aaf25a00db63f3e2ae6ec047e23f54277f90f Mon Sep 17 00:00:00 2001 From: Iago Toral Quiroga Date: Wed, 21 Jun 2023 10:29:07 +0200 Subject: [PATCH] v3dv: expose scalarBlockLayout on V3D 7.x MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This version of V3D doesn't have the restriction that vector accesses must not cross 16-byte boundaries. Reviewed-by: Alejandro Piñeiro Part-of: --- src/broadcom/vulkan/v3dv_device.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/broadcom/vulkan/v3dv_device.c b/src/broadcom/vulkan/v3dv_device.c index c4307f84504..f8adb03b3c3 100644 --- a/src/broadcom/vulkan/v3dv_device.c +++ b/src/broadcom/vulkan/v3dv_device.c @@ -308,7 +308,7 @@ get_features(const struct v3dv_physical_device *physical_device, * problematic, we would always have to scalarize. Overall, this would * not lead to best performance so let's just not support it. */ - .scalarBlockLayout = false, + .scalarBlockLayout = physical_device->devinfo.ver >= 71, /* This tells applications 2 things: * * 1. If they can select just one aspect for barriers. For us barriers