From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
To: linux-media@vger.kernel.org
Cc: kernel@collabora.com
Subject: Re: [PATCH v2 0/4] media: rkvdec: Fix H.264 error resilience
Date: Fri, 23 Dec 2022 14:51:19 -0500 [thread overview]
Message-ID: <2ad38f3d4998a3e912c5acbb40053ff04d26fa8e.camel@collabora.com> (raw)
In-Reply-To: <20221223193807.914935-1-nicolas.dufresne@collabora.com>
fyi, this cover letter was v2.
Le vendredi 23 décembre 2022 à 14:38 -0500, Nicolas Dufresne a écrit :
> This patch serie changes the decoding mode from "exit on error"
> to "keep decoding". Using this mode and re-enabling error detection
> allow getting error resilience without loosing the ability to report
> errors to userland. This have showed great results, but might be a
> little more risky since this is not the mode that the reference code
> uses and the documentation is very brief. With this in place,
> userspace can chose to skip or display corrupted frames depending
> on its application requirement. Previsouly, applicaiton would have
> had no choice but to present the corrupted frames.
>
> Changes since V1:
> - Removed merged patch
> - Changed usage of pr_debug into v4l2_dbg
> - Fix typos in commit messages and comments
>
> Nicolas Dufresne (5):
> media: rkvdec: Disable H.264 error detection
> media: rkvdec: Add an ops to check for decode errors
> media: rkvdec: Fix RKVDEC_ERR_PKT_NUM macro
> media: rkvdec: Re-enable H.264 error detection
> rkvdec: Improve error handling
>
> drivers/staging/media/rkvdec/rkvdec-h264.c | 23 +++++++++++++--
> drivers/staging/media/rkvdec/rkvdec-regs.h | 2 +-
> drivers/staging/media/rkvdec/rkvdec.c | 34 ++++++++++++++++++----
> drivers/staging/media/rkvdec/rkvdec.h | 2 ++
> 4 files changed, 51 insertions(+), 10 deletions(-)
>
next prev parent reply other threads:[~2022-12-23 19:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 19:38 [PATCH v1 0/4] media: rkvdec: Fix H.264 error resilience Nicolas Dufresne
2022-12-23 19:38 ` [PATCH v2 1/4] media: rkvdec: Add an ops to check for decode errors Nicolas Dufresne
2022-12-26 22:15 ` Ezequiel Garcia
2022-12-23 19:38 ` [PATCH v2 2/4] media: rkvdec: Fix RKVDEC_ERR_PKT_NUM macro Nicolas Dufresne
2022-12-23 19:38 ` [PATCH v2 3/4] media: rkvdec: Re-enable H.264 error detection Nicolas Dufresne
2022-12-26 4:17 ` Chen-Yu Tsai
2023-01-09 19:59 ` Nicolas Dufresne
2022-12-26 21:33 ` Ezequiel Garcia
2023-01-09 20:00 ` Nicolas Dufresne
2022-12-23 19:38 ` [PATCH v2 4/4] rkvdec: Improve error handling Nicolas Dufresne
2022-12-26 22:32 ` Ezequiel Garcia
2022-12-23 19:51 ` Nicolas Dufresne [this message]
2022-12-26 4:20 ` [PATCH v1 0/4] media: rkvdec: Fix H.264 error resilience Chen-Yu Tsai
2023-01-09 20:18 ` Nicolas Dufresne
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=2ad38f3d4998a3e912c5acbb40053ff04d26fa8e.camel@collabora.com \
--to=nicolas.dufresne@collabora.com \
--cc=kernel@collabora.com \
--cc=linux-media@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