From: Nicolas Dufresne <nicolas@ndufresne.ca>
To: Hirokazu Honda <hiroh@chromium.org>,
ezequiel@collabora.com, mchehab@kernel.org,
gregkh@linuxfoundation.org, linux-media@vger.kernel.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
tfiga@chromium.org
Subject: Re: [PATCH] media: hantro: Support H264 profile control
Date: Fri, 22 Nov 2019 10:09:23 -0500 [thread overview]
Message-ID: <767528be59275265072896e5c679e97575615fdd.camel@ndufresne.ca> (raw)
In-Reply-To: <20191122051608.128717-1-hiroh@chromium.org>
Le vendredi 22 novembre 2019 à 14:16 +0900, Hirokazu Honda a écrit :
> The Hantro G1 decoder supports H.264 profiles from Baseline to High, with
> the exception of the Extended profile.
>
> Expose the V4L2_CID_MPEG_VIDEO_H264_PROFILE control, so that the
> applications can query the driver for the list of supported profiles.
Thanks for this patch. Do you think we could also add the LEVEL control
so the profile/level enumeration becomes complete ?
I'm thinking it would be nice if the v4l2 compliance test make sure
that codecs do implement these controls (both stateful and stateless),
it's essential for stack with software fallback, or multiple capable
codec hardware but with different capabilities.
>
> Signed-off-by: Hirokazu Honda <hiroh@chromium.org>
> ---
> drivers/staging/media/hantro/hantro_drv.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/staging/media/hantro/hantro_drv.c b/drivers/staging/media/hantro/hantro_drv.c
> index 6d9d41170832..9387619235d8 100644
> --- a/drivers/staging/media/hantro/hantro_drv.c
> +++ b/drivers/staging/media/hantro/hantro_drv.c
> @@ -355,6 +355,16 @@ static const struct hantro_ctrl controls[] = {
> .def = V4L2_MPEG_VIDEO_H264_START_CODE_ANNEX_B,
> .max = V4L2_MPEG_VIDEO_H264_START_CODE_ANNEX_B,
> },
> + }, {
> + .codec = HANTRO_H264_DECODER,
> + .cfg = {
> + .id = V4L2_CID_MPEG_VIDEO_H264_PROFILE,
> + .min = V4L2_MPEG_VIDEO_H264_PROFILE_BASELINE,
> + .max = V4L2_MPEG_VIDEO_H264_PROFILE_HIGH,
> + .menu_skip_mask =
> + BIT(V4L2_MPEG_VIDEO_H264_PROFILE_EXTENDED),
> + .def = V4L2_MPEG_VIDEO_H264_PROFILE_MAIN,
> + }
> }, {
> },
> };
next prev parent reply other threads:[~2019-11-22 15:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 5:16 Hirokazu Honda
2019-11-22 15:09 ` Nicolas Dufresne [this message]
2019-11-22 16:00 ` Tomasz Figa
2019-11-22 16:52 ` Nicolas Dufresne
2019-11-29 0:16 ` Tomasz Figa
2020-01-10 12:31 ` Hans Verkuil
2020-01-11 4:59 ` Ezequiel Garcia
2020-01-18 13:31 ` Nicolas Dufresne
2020-02-03 11:13 ` Tomasz Figa
2020-02-03 11:59 ` Hans Verkuil
2020-02-03 13:48 ` Tomasz Figa
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=767528be59275265072896e5c679e97575615fdd.camel@ndufresne.ca \
--to=nicolas@ndufresne.ca \
--cc=devel@driverdev.osuosl.org \
--cc=ezequiel@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=hiroh@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=tfiga@chromium.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®