va: Replace usage of entrypoint UNKNOWN with PROCESSING for VP

Reviewed-by: Boyuan Zhang <Boyuan.Zhang@amd.com>
Reviewed-by: Jesse Natalie <jenatali@microsoft.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17557>
This commit is contained in:
Sil Vilerino 2022-07-21 12:41:45 -04:00 committed by Marge Bot
parent 74c5d01169
commit 721d9eea81
3 changed files with 4 additions and 4 deletions

View File

@ -259,7 +259,7 @@ vlVaCreateConfig(VADriverContextP ctx, VAProfile profile, VAEntrypoint entrypoin
return VA_STATUS_ERROR_UNSUPPORTED_ENTRYPOINT;
}
config->entrypoint = PIPE_VIDEO_ENTRYPOINT_UNKNOWN;
config->entrypoint = PIPE_VIDEO_ENTRYPOINT_PROCESSING;
config->profile = PIPE_VIDEO_PROFILE_UNKNOWN;
supported_rt_formats = VA_RT_FORMAT_YUV420 |
VA_RT_FORMAT_YUV420_10BPP |
@ -441,7 +441,7 @@ vlVaQueryConfigAttributes(VADriverContextP ctx, VAConfigID config_id, VAProfile
case PIPE_VIDEO_ENTRYPOINT_ENCODE:
*entrypoint = VAEntrypointEncSlice;
break;
case PIPE_VIDEO_ENTRYPOINT_UNKNOWN:
case PIPE_VIDEO_ENTRYPOINT_PROCESSING:
*entrypoint = VAEntrypointVideoProc;
break;
default:

View File

@ -252,7 +252,7 @@ vlVaCreateContext(VADriverContextP ctx, VAConfigID config_id, int picture_width,
if (is_vpp) {
context->decoder = NULL;
} else {
if (config->entrypoint != PIPE_VIDEO_ENTRYPOINT_UNKNOWN) {
if (config->entrypoint != PIPE_VIDEO_ENTRYPOINT_PROCESSING) {
max_supported_width = drv->vscreen->pscreen->get_video_param(drv->vscreen->pscreen,
config->profile, config->entrypoint,
PIPE_VIDEO_CAP_MAX_WIDTH);

View File

@ -523,7 +523,7 @@ vlVaQuerySurfaceAttributes(VADriverContextP ctx, VAConfigID config_id,
}
#endif
if (config->entrypoint != PIPE_VIDEO_ENTRYPOINT_UNKNOWN) {
if (config->entrypoint != PIPE_VIDEO_ENTRYPOINT_PROCESSING) {
attribs[i].type = VASurfaceAttribMaxWidth;
attribs[i].value.type = VAGenericValueTypeInteger;
attribs[i].flags = VA_SURFACE_ATTRIB_GETTABLE;