From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id CF95643F73 for ; Tue, 23 Aug 2022 08:20:22 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 28A1668BA55; Tue, 23 Aug 2022 11:20:09 +0300 (EEST) Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 88E9F68BA3E for ; Tue, 23 Aug 2022 11:20:01 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1661242807; x=1692778807; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=TwxK3wj5siix+97PNcVIlfqKQDXSW9J3+Mv04bB/Ap0=; b=Xl86bzZz5svZPK7io0QXyRhGhetTHi4wMlluXh1C4llo54f7lIgDv608 C148lt99ilyP0L7Sv6Z/Gel20V6kYDk6PvTlhH7dqPuBtGuMLrl8l2u8r CakkRTdcY4oqkUQB2tDqau6UDNPiEg1nqdYQo+3zw6yEsrjgvNQ0+3WEt IBBdHvWBkidk+lnWwUjwLMH+oLMBOjBoydtJ1Hj0m3JOsJjhroVIiS6z4 o8KSBmxU9ILSoTIKfEWdtmATD7ComRAox8FdcowSawJYU6XQGGCBtO5hA c4qAT07Nnzoagb0S5Ld3UfUJ1f8Dvui4+gbJ5tFVAj/LTEQ2TD+eQR6F3 Q==; X-IronPort-AV: E=McAfee;i="6500,9779,10447"; a="357604448" X-IronPort-AV: E=Sophos;i="5.93,257,1654585200"; d="scan'208";a="357604448" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Aug 2022 01:19:59 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.93,257,1654585200"; d="scan'208";a="638556940" Received: from t.sh.intel.com ([10.239.159.159]) by orsmga008.jf.intel.com with ESMTP; 23 Aug 2022 01:19:58 -0700 From: Fei Wang To: ffmpeg-devel@ffmpeg.org Date: Tue, 23 Aug 2022 16:19:29 +0800 Message-Id: <20220823081929.413947-3-fei.w.wang@intel.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20220823081929.413947-1-fei.w.wang@intel.com> References: <20220823081929.413947-1-fei.w.wang@intel.com> MIME-Version: 1.0 Subject: [FFmpeg-devel] [PATCH v3 3/3] lavc/vaapi_vp9: add surface internal re-allocation capability X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Cc: Fei Wang , Linjie Fu Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: From: Linjie Fu Surfaces need to bound to a vaContext when context is created before VAAPI 1.0.0, it need to reset context if surface change. So re-allocation capability only available after VAAPI 1.0.0. Detail changes in VAAPI: https://github.com/intel/libva/commit/492b692005ccd0d8da190209d5b3ae7b7825f4b8 Signed-off-by: Linjie Fu Signed-off-by: Fei Wang --- update: 1. add va check version 1.0.0 libavcodec/vaapi_vp9.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/libavcodec/vaapi_vp9.c b/libavcodec/vaapi_vp9.c index 776382f683..7dce0250a0 100644 --- a/libavcodec/vaapi_vp9.c +++ b/libavcodec/vaapi_vp9.c @@ -181,5 +181,9 @@ const AVHWAccel ff_vp9_vaapi_hwaccel = { .uninit = ff_vaapi_decode_uninit, .frame_params = ff_vaapi_common_frame_params, .priv_data_size = sizeof(VAAPIDecodeContext), +#if VA_CHECK_VERSION(1, 0, 0) + .caps_internal = HWACCEL_CAP_ASYNC_SAFE | HWACCEL_CAP_INTERNAL_ALLOC, +#else .caps_internal = HWACCEL_CAP_ASYNC_SAFE, +#endif }; -- 2.25.1 _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".