From: "Xiang, Haihao" <haihao.xiang-at-intel.com@ffmpeg.org>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/6] lavu/hwcontext_qsv: specify Shift for each format
Date: Sun, 9 Oct 2022 01:44:43 +0000
Message-ID: <bb61a6b14428948e42331abd8b3d2e948f3db2c7.camel@intel.com> (raw)
In-Reply-To: <20221006073538.27710-1-haihao.xiang@intel.com>
On Thu, 2022-10-06 at 15:35 +0800, Xiang, Haihao wrote:
> From: Haihao Xiang <haihao.xiang@intel.com>
>
> We can't get Shift from bit depth for some formats in the SDK. For
> example, bit depth is 10, however Shift is 0 for Y410 (XV30 in FFmpeg).
> In order to support these formats in the next commits, this patch
> specified Shift for each format
>
> Signed-off-by: Haihao Xiang <haihao.xiang@intel.com>
> ---
> libavutil/hwcontext_qsv.c | 27 +++++++++++++++++++--------
> 1 file changed, 19 insertions(+), 8 deletions(-)
>
> diff --git a/libavutil/hwcontext_qsv.c b/libavutil/hwcontext_qsv.c
> index 9fa0dfa1c0..2272df52f2 100644
> --- a/libavutil/hwcontext_qsv.c
> +++ b/libavutil/hwcontext_qsv.c
> @@ -109,20 +109,21 @@ typedef struct QSVFramesContext {
> static const struct {
> enum AVPixelFormat pix_fmt;
> uint32_t fourcc;
> + uint16_t mfx_shift;
> } supported_pixel_formats[] = {
> - { AV_PIX_FMT_NV12, MFX_FOURCC_NV12 },
> - { AV_PIX_FMT_BGRA, MFX_FOURCC_RGB4 },
> - { AV_PIX_FMT_P010, MFX_FOURCC_P010 },
> - { AV_PIX_FMT_PAL8, MFX_FOURCC_P8 },
> + { AV_PIX_FMT_NV12, MFX_FOURCC_NV12, 0 },
> + { AV_PIX_FMT_BGRA, MFX_FOURCC_RGB4, 0 },
> + { AV_PIX_FMT_P010, MFX_FOURCC_P010, 1 },
> + { AV_PIX_FMT_PAL8, MFX_FOURCC_P8, 0 },
> #if CONFIG_VAAPI
> { AV_PIX_FMT_YUYV422,
> - MFX_FOURCC_YUY2 },
> + MFX_FOURCC_YUY2, 0 },
> { AV_PIX_FMT_Y210,
> - MFX_FOURCC_Y210 },
> + MFX_FOURCC_Y210, 1 },
> // VUYX is used for VAAPI child device,
> // the SDK only delares support for AYUV
> { AV_PIX_FMT_VUYX,
> - MFX_FOURCC_AYUV },
> + MFX_FOURCC_AYUV, 0 },
> #endif
> };
>
> @@ -170,6 +171,16 @@ static uint32_t qsv_fourcc_from_pix_fmt(enum
> AVPixelFormat pix_fmt)
> return 0;
> }
>
> +static uint16_t qsv_shift_from_pix_fmt(enum AVPixelFormat pix_fmt)
> +{
> + for (int i = 0; i < FF_ARRAY_ELEMS(supported_pixel_formats); i++) {
> + if (supported_pixel_formats[i].pix_fmt == pix_fmt)
> + return supported_pixel_formats[i].mfx_shift;
> + }
> +
> + return 0;
> +}
> +
> #if CONFIG_D3D11VA
> static uint32_t qsv_get_d3d11va_bind_flags(int mem_type)
> {
> @@ -503,7 +514,7 @@ static int qsv_init_surface(AVHWFramesContext *ctx,
> mfxFrameSurface1 *surf)
>
> surf->Info.BitDepthLuma = desc->comp[0].depth;
> surf->Info.BitDepthChroma = desc->comp[0].depth;
> - surf->Info.Shift = desc->comp[0].depth > 8;
> + surf->Info.Shift = qsv_shift_from_pix_fmt(ctx->sw_format);
>
> if (desc->log2_chroma_w && desc->log2_chroma_h)
> surf->Info.ChromaFormat = MFX_CHROMAFORMAT_YUV420;
Will apply,
-Haihao
_______________________________________________
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".
prev parent reply other threads:[~2022-10-09 1:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 7:35 Xiang, Haihao
2022-10-06 7:35 ` [FFmpeg-devel] [PATCH 2/6] lavc/qsv: specify Shift for each format too Xiang, Haihao
2022-10-06 7:35 ` [FFmpeg-devel] [PATCH 3/6] lavu/hwcontext_qsv: add support for 10bit 4:4:4 content on Linux Xiang, Haihao
2022-10-06 7:35 ` [FFmpeg-devel] [PATCH 4/6] lavc/qsv: add support for decoding & encoding 10bit 4:4:4 content Xiang, Haihao
2022-10-06 7:35 ` [FFmpeg-devel] [PATCH 5/6] lavu/hwcontext_qsv: add support for 12bit content on Linux Xiang, Haihao
2022-10-06 7:35 ` [FFmpeg-devel] [PATCH 6/6] lavc/qsv: add support for decoding & encoding 12bit content Xiang, Haihao
2022-10-09 1:44 ` Xiang, Haihao [this message]
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=bb61a6b14428948e42331abd8b3d2e948f3db2c7.camel@intel.com \
--to=haihao.xiang-at-intel.com@ffmpeg.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