From 9b7f547fef1c0b9fac8ccca940259a49f3f82389 Mon Sep 17 00:00:00 2001
From: Constantine Shablia <constantine.shablya@collabora.com>
Date: Thu, 31 Oct 2024 00:35:45 +0000
Subject: [PATCH] panvk: adjust maxSamplerAllocationCount limit

Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/31917>
---
 src/panfrost/vulkan/panvk_physical_device.c | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/src/panfrost/vulkan/panvk_physical_device.c b/src/panfrost/vulkan/panvk_physical_device.c
index 608447bccd6..9a336adf349 100644
--- a/src/panfrost/vulkan/panvk_physical_device.c
+++ b/src/panfrost/vulkan/panvk_physical_device.c
@@ -446,8 +446,11 @@ get_device_properties(const struct panvk_instance *instance,
        * this limit.
        */
       .maxMemoryAllocationCount = UINT32_MAX,
-      /* Again, no hardware limit, but most drivers seem to advertive 64k. */
-      .maxSamplerAllocationCount = 64 * 1024,
+      /* On Mali, VkSampler objects do not use any resources other than host
+       * memory and host address space, availability of which can change
+       * significantly over time.
+       */
+      .maxSamplerAllocationCount = UINT32_MAX,
       /* A cache line. */
       .bufferImageGranularity = 64,
       /* Sparse binding not supported yet. */