From: Neil Armstrong <neil.armstrong@linaro.org>
To: Christian Hewitt <christianshewitt@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-media@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-staging@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Neil Armstrong <narmstrong@baylibre.com>
Subject: Re: [PATCH] media: meson: vdec: esparser: check parsing state with hardware write pointer
Date: Mon, 23 Jan 2023 10:47:56 +0100 [thread overview]
Message-ID: <3a3d9fc5-0f61-8da7-dc4c-7b57b0272230@linaro.org> (raw)
In-Reply-To: <20230123094300.2816812-1-christianshewitt@gmail.com>
On 23/01/2023 10:43, Christian Hewitt wrote:
> From: Neil Armstrong <narmstrong@baylibre.com>
>
> Also check the hardware write pointer to check if ES Parser has stalled.
>
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
> Signed-off-by: Christian Hewitt <christianshewitt@gmail.com>
> ---
> drivers/staging/media/meson/vdec/esparser.c | 15 +++++++++++----
> 1 file changed, 11 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/staging/media/meson/vdec/esparser.c b/drivers/staging/media/meson/vdec/esparser.c
> index df5956c6141d..41b705f999b2 100644
> --- a/drivers/staging/media/meson/vdec/esparser.c
> +++ b/drivers/staging/media/meson/vdec/esparser.c
> @@ -300,6 +300,7 @@ esparser_queue(struct amvdec_session *sess, struct vb2_v4l2_buffer *vbuf)
> u32 num_dst_bufs = 0;
> u32 offset;
> u32 pad_size;
> + u32 wp, wp2;
>
> /*
> * When max ref frame is held by VP9, this should be -= 3 to prevent a
> @@ -354,15 +355,21 @@ esparser_queue(struct amvdec_session *sess, struct vb2_v4l2_buffer *vbuf)
> }
>
> pad_size = esparser_pad_start_code(core, vb, payload_size);
> + wp = amvdec_read_parser(core, PARSER_VIDEO_WP);
> ret = esparser_write_data(core, phy, payload_size + pad_size);
> + wp2 = amvdec_read_parser(core, PARSER_VIDEO_WP);
>
> if (ret <= 0) {
> - dev_warn(core->dev, "esparser: input parsing error\n");
> - amvdec_remove_ts(sess, vb->timestamp);
> - v4l2_m2m_buf_done(vbuf, VB2_BUF_STATE_ERROR);
> amvdec_write_parser(core, PARSER_FETCH_CMD, 0);
>
> - return 0;
> + if (ret < 0 || wp2 == wp) {
> + dev_err(core->dev, "esparser: input parsing error ret %d (%x <=> %x)\n",
> + ret, wp, wp2);
> + amvdec_remove_ts(sess, vb->timestamp);
> + v4l2_m2m_buf_done(vbuf, VB2_BUF_STATE_ERROR);
> +
> + return 0;
> + }
> }
>
> atomic_inc(&sess->esparser_queued_bufs);
It's weird, but:
Acked-by: Neil Armstrong <neil.armstrong@linaro.org>
Thanks Christian for handling those changes
Neil
next prev parent reply other threads:[~2023-01-23 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 9:43 [PATCH] media: meson: vdec: esparser: check parsing state with hardware write pointer Christian Hewitt
2023-01-23 9:47 ` Neil Armstrong [this message]
2023-01-23 12:04 ` Dan Carpenter
2023-03-21 13:58 ` Hans Verkuil
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=3a3d9fc5-0f61-8da7-dc4c-7b57b0272230@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=christianshewitt@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=martin.blumenstingl@googlemail.com \
--cc=mchehab@kernel.org \
--cc=narmstrong@baylibre.com \
/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).