etnaviv: Fix how we determine the max supported number of varyings

The driver is written that we should support ETNA_NUM_VARYINGS and reporting
a bigger number will cause some troubles. I had a quick look at galcore's
hw database and there are entries that report a higher value.

So I think what we want is to the minimum value of what kernel driver reports
and what the gallium driver should be able to handle.

Fixes: 84816c22e4 ("etnaviv: ask kernel for max number of supported varyings")
Signed-off-by: Christian Gmeiner <cgmeiner@igalia.com>
Reviewed-by: Lucas Stach <l.stach@pengutronix.de>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27923>
This commit is contained in:
Christian Gmeiner 2023-10-25 13:55:53 +02:00 committed by Marge Bot
parent 14e9894a19
commit 93255abe30

View file

@ -899,7 +899,7 @@ etna_get_specs(struct etna_screen *screen)
DBG("could not get ETNA_GPU_NUM_VARYINGS");
goto fail;
}
screen->specs.max_varyings = MAX2(val, ETNA_NUM_VARYINGS);
screen->specs.max_varyings = MIN2(val, ETNA_NUM_VARYINGS);
if (etna_gpu_get_param(screen->gpu, ETNA_GPU_NN_CORE_COUNT, &val)) {
DBG("could not get ETNA_GPU_NN_CORE_COUNT");