From 23e731fcdba429f48324a7c904e5f655116e4858 Mon Sep 17 00:00:00 2001
From: Mike Blumenkrantz <michael.blumenkrantz@gmail.com>
Date: Tue, 8 Sep 2020 15:08:20 -0400
Subject: [PATCH] zink: export PIPE_CAP_MAX*_VARYINGS values

this is separate from PIPE_SHADER_CAP_MAX_OUTPUTS

fixes mesa/mesa#3105

Reviewed-by: Erik Faye-Lund <erik.faye-lund@collabora.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7110>
---
 src/gallium/drivers/zink/zink_screen.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/src/gallium/drivers/zink/zink_screen.c b/src/gallium/drivers/zink/zink_screen.c
index cc8b5fff642..3daf8143f31 100644
--- a/src/gallium/drivers/zink/zink_screen.c
+++ b/src/gallium/drivers/zink/zink_screen.c
@@ -321,6 +321,12 @@ zink_get_param(struct pipe_screen *pscreen, enum pipe_cap param)
    case PIPE_CAP_TWO_SIDED_COLOR:
       return 0;
 
+   case PIPE_CAP_MAX_SHADER_PATCH_VARYINGS:
+      return screen->info.props.limits.maxTessellationControlPerVertexOutputComponents / 4;
+   case PIPE_CAP_MAX_VARYINGS:
+      /* need to reserve up to 60 of our varying components and 16 slots for streamout */
+      return MIN2(screen->info.props.limits.maxVertexOutputComponents / 4 / 2, 16);
+
    case PIPE_CAP_DMABUF:
       return screen->info.have_KHR_external_memory_fd;