frontends/va/context: don't set max_references with num_render_targets
authorVíctor Manuel Jáquez Leal <vjaquez@igalia.com>
Sun, 6 Dec 2020 13:56:58 +0000 (14:56 +0100)
committerVíctor Manuel Jáquez Leal <vjaquez@igalia.com>
Fri, 22 Jan 2021 13:59:53 +0000 (14:59 +0100)
commit925d701014c2ba084061eae131f4b5c75e595f29
tree0db4bc0a92ebd193814a42aed85a4508b0529ac1
parent824eba2148e56a75d0678011b4f546cabbd5d345
frontends/va/context: don't set max_references with num_render_targets

For HEVC and VP9 template's max_references are tied to the number of
surfaces associated with context. Later, the decoder is created if
max_references is different to zero.

But vaCreateContext() doesn't really need an array of VASurfaceIDs (see
https://lists.01.org/pipermail/intel-vaapi-media/2017-July/000052.html and
https://github.com/intel/libva/issues/251).

This patch removes the validation of the max_references at decoder
creation and also remove the assignation of num_render_targets to
max_references.

Signed-off-by: Víctor Manuel Jáquez Leal <vjaquez@igalia.com>
Reviewed-by: Leo Liu <leo.liu@amd.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7949>
src/gallium/frontends/va/context.c
src/gallium/frontends/va/picture.c