From: Philipp Zabel <p.zabel@pengutronix.de>
To: Fabio Estevam <festevam@gmail.com>, hverkuil-cisco@xs4all.nl
Cc: nicolas.dufresne@collabora.com, kernel@iktek.de,
linux-media@vger.kernel.org, stable@vger.kernel.org,
Ezequiel Garcia <ezequiel@collabora.com>,
Fabio Estevam <festevam@denx.de>
Subject: Re: [PATCH v4 2/2] media: coda: Add more H264 levels for CODA960
Date: Wed, 06 Apr 2022 16:59:01 +0200 [thread overview]
Message-ID: <219003f3341412cc6241d8c6e73309a74836678d.camel@pengutronix.de> (raw)
In-Reply-To: <20220405135957.3580343-2-festevam@gmail.com>
Hi Fabio,
On Di, 2022-04-05 at 10:59 -0300, Fabio Estevam wrote:
> From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
>
> This add H264 level 4.1, 4.2 and 5.0 to the list of supported
> formats.
> While the hardware does not fully support these levels, it do support
> most of them. The constraints on frame size and pixel formats already
> cover the limitation.
>
> This fixes negotiation of level on GStreamer 1.17.1.
>
> Cc: stable@vger.kernel.org
> Fixes: 42a68012e67c2 ("media: coda: add read-only h.264 decoder
> profile/level controls")
> Signed-off-by: Nicolas Dufresne <nicolas.dufresne@collabora.com>
> Signed-off-by: Ezequiel Garcia <ezequiel@collabora.com>
> Tested-by: Pascal Speck <kernel@iktek.de>
> Signed-off-by: Fabio Estevam <festevam@denx.de>
> Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de>
> ---
> Changes since v3:
> - Rebased against linux-next and took the coda->chips-media rename
> in consideration.
> - Added Philipp's Reviewed-by tag.
I think you rebased the wrong version of this patch.
> drivers/media/platform/chips-media/coda-common.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/media/platform/chips-media/coda-common.c
> b/drivers/media/platform/chips-media/coda-common.c
> index 53b2dd1b268c..f1234ad24f65 100644
> --- a/drivers/media/platform/chips-media/coda-common.c
> +++ b/drivers/media/platform/chips-media/coda-common.c
> @@ -2364,7 +2364,10 @@ static void coda_encode_ctrls(struct coda_ctx
> *ctx)
> (1 << V4L2_MPEG_VIDEO_H264_LEVEL_3_0) |
> (1 << V4L2_MPEG_VIDEO_H264_LEVEL_3_1) |
> (1 << V4L2_MPEG_VIDEO_H264_LEVEL_3_2) |
> - (1 << V4L2_MPEG_VIDEO_H264_LEVEL_4_0)),
> + (1 << V4L2_MPEG_VIDEO_H264_LEVEL_4_0) |
> + (1 << V4L2_MPEG_VIDEO_H264_LEVEL_4_1) |
> + (1 << V4L2_MPEG_VIDEO_H264_LEVEL_4_2) |
> + (1 << V4L2_MPEG_VIDEO_H264_LEVEL_5_0)),
I asked to remove the 5.0 level and to increase the max level to 4.2,
you already fixed this in v3.
> V4L2_MPEG_VIDEO_H264_LEVEL_4_0);
> }
> v4l2_ctrl_new_std(&ctx->ctrls, &coda_ctrl_ops,
> @@ -2437,7 +2440,7 @@ static void coda_decode_ctrls(struct coda_ctx
> *ctx)
> ctx->dev->devtype->product == CODA_7541)
> max = V4L2_MPEG_VIDEO_H264_LEVEL_4_0;
> else if (ctx->dev->devtype->product == CODA_960)
> - max = V4L2_MPEG_VIDEO_H264_LEVEL_4_1;
> + max = V4L2_MPEG_VIDEO_H264_LEVEL_5_0;
Same as above, there is no way to support level 5.0 frame size
requirements.
regards
Philipp
next prev parent reply other threads:[~2022-04-06 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 13:59 [PATCH v4 1/2] media: coda: Fix reported H264 profile Fabio Estevam
2022-04-05 13:59 ` [PATCH v4 2/2] media: coda: Add more H264 levels for CODA960 Fabio Estevam
2022-04-06 14:59 ` Philipp Zabel [this message]
2022-04-06 20:25 ` Fabio Estevam
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=219003f3341412cc6241d8c6e73309a74836678d.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=ezequiel@collabora.com \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=kernel@iktek.de \
--cc=linux-media@vger.kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).