From: Andrew Sayers <ffmpeg-devel@pileofstuff.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v9 11/13] avutil/hwcontext_d3d12va: add Flags for resource creation
Date: Tue, 21 May 2024 17:32:03 +0100
Message-ID: <ZkzMg1W_arWdVOng@andrews-2024-laptop.sayers> (raw)
In-Reply-To: <20240520145222.291-11-tong1.wu@intel.com>
(Only reviewing documentation, not code)
On Mon, May 20, 2024 at 10:52:20PM +0800, tong1.wu-at-intel.com@ffmpeg.org wrote:
> From: Tong Wu <tong1.wu@intel.com>
>
> Flags field is added to support diffferent resource creation.
>
> Signed-off-by: Tong Wu <tong1.wu@intel.com>
> ---
> doc/APIchanges | 3 +++
> libavutil/hwcontext_d3d12va.c | 2 +-
> libavutil/hwcontext_d3d12va.h | 8 ++++++++
> libavutil/version.h | 2 +-
> 4 files changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/doc/APIchanges b/doc/APIchanges
> index 269fd36559..808ba02f2d 100644
> --- a/doc/APIchanges
> +++ b/doc/APIchanges
> @@ -2,6 +2,9 @@ The last version increases of all libraries were on 2024-03-07
>
> API changes, most recent first:
>
> +2024-01-xx - xxxxxxxxxx - lavu 59.20.100 - hwcontext_d3d12va.h
> + Add AVD3D12VAFramesContext.flags
> +
> 2024-05-xx - xxxxxxxxxx - lavu 59.19.100 - hwcontext_qsv.h
> Add AVQSVFramesContext.info
>
> diff --git a/libavutil/hwcontext_d3d12va.c b/libavutil/hwcontext_d3d12va.c
> index cfc016315d..6507cf69c1 100644
> --- a/libavutil/hwcontext_d3d12va.c
> +++ b/libavutil/hwcontext_d3d12va.c
> @@ -247,7 +247,7 @@ static AVBufferRef *d3d12va_pool_alloc(void *opaque, size_t size)
> .Format = hwctx->format,
> .SampleDesc = {.Count = 1, .Quality = 0 },
> .Layout = D3D12_TEXTURE_LAYOUT_UNKNOWN,
> - .Flags = D3D12_RESOURCE_FLAG_NONE,
> + .Flags = hwctx->flags,
> };
>
> frame = av_mallocz(sizeof(AVD3D12VAFrame));
> diff --git a/libavutil/hwcontext_d3d12va.h b/libavutil/hwcontext_d3d12va.h
> index ff06e6f2ef..608dbac97f 100644
> --- a/libavutil/hwcontext_d3d12va.h
> +++ b/libavutil/hwcontext_d3d12va.h
> @@ -129,6 +129,14 @@ typedef struct AVD3D12VAFramesContext {
> * If unset, will be automatically set.
> */
> DXGI_FORMAT format;
> +
> + /**
> + * This field is used to specify options for working with resources.
> + * If unset, this will be D3D12_RESOURCE_FLAG_NONE.
> + *
> + * @see: https://learn.microsoft.com/en-us/windows/win32/api/d3d12/ne-d3d12-d3d12_resource_flags.
> + */
> + D3D12_RESOURCE_FLAGS flags;
Some nitpicks:
* "This field is used to specify" is redundant, you can save the reader
a few seconds by starting the sentence with just "Options..."
* "@see" starts a paragraph, so the rendered documentation will look better
without the ":"
* the full stop after the URL makes it harder to copy/paste the text -
remove the full stop or use a [markdown link](...)
_______________________________________________
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".
next prev parent reply other threads:[~2024-05-21 16:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 14:52 [FFmpeg-devel] [PATCH v9 01/13] avcodec/vaapi_encode: introduce a base layer for vaapi encode tong1.wu-at-intel.com
2024-05-20 14:52 ` [FFmpeg-devel] [PATCH v9 02/13] avcodec/vaapi_encode: add async_depth to common options tong1.wu-at-intel.com
2024-05-20 14:52 ` [FFmpeg-devel] [PATCH v9 03/13] avcodec/vaapi_encode: add picture type name to base tong1.wu-at-intel.com
2024-05-20 14:52 ` [FFmpeg-devel] [PATCH v9 04/13] avcodec/vaapi_encode: move pic->input_surface initialization to encode_alloc tong1.wu-at-intel.com
2024-05-20 14:52 ` [FFmpeg-devel] [PATCH v9 05/13] avcodec/vaapi_encode: move the dpb logic from VAAPI to base layer tong1.wu-at-intel.com
2024-05-20 14:52 ` [FFmpeg-devel] [PATCH v9 06/13] avcodec/vaapi_encode: extract the init and close function " tong1.wu-at-intel.com
2024-05-20 14:52 ` [FFmpeg-devel] [PATCH v9 07/13] avcodec/vaapi_encode: extract gop configuration and two options " tong1.wu-at-intel.com
2024-05-20 14:52 ` [FFmpeg-devel] [PATCH v9 08/13] avcodec/vaapi_encode: extract set_output_property " tong1.wu-at-intel.com
2024-05-20 14:52 ` [FFmpeg-devel] [PATCH v9 09/13] avcodec/vaapi_encode: extract a get_recon_format function " tong1.wu-at-intel.com
2024-05-20 14:52 ` [FFmpeg-devel] [PATCH v9 10/13] avcodec/vaapi_encode: extract a free funtion " tong1.wu-at-intel.com
2024-05-20 14:52 ` [FFmpeg-devel] [PATCH v9 11/13] avutil/hwcontext_d3d12va: add Flags for resource creation tong1.wu-at-intel.com
2024-05-21 16:32 ` Andrew Sayers [this message]
2024-05-22 1:29 ` Wu, Tong1
2024-05-20 14:52 ` [FFmpeg-devel] [PATCH v9 12/13] avcodec: add D3D12VA hardware HEVC encoder tong1.wu-at-intel.com
2024-05-20 14:52 ` [FFmpeg-devel] [PATCH v9 13/13] Changelog: add D3D12VA HEVC encoder changelog tong1.wu-at-intel.com
2024-05-23 16:11 ` [FFmpeg-devel] [PATCH v9 01/13] avcodec/vaapi_encode: introduce a base layer for vaapi encode Lynne via ffmpeg-devel
2024-05-24 15:39 ` Wu, Tong1
2024-05-24 16:35 ` Lynne via ffmpeg-devel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZkzMg1W_arWdVOng@andrews-2024-laptop.sayers \
--to=ffmpeg-devel@pileofstuff.org \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git