From: Ezequiel Garcia <ezequiel@collabora.com>
To: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Philipp Zabel <p.zabel@pengutronix.de>,
Jonas Karlman <jonas@kwiboo.se>,
Nicolas Dufresne <nicolas.dufresne@collabora.com>,
Ezequiel Garcia <ezequiel@collabora.com>,
kernel@collabora.com
Subject: [PATCH 0/2] media: hantro/rkvdec handle unsupported H.264 bitstreams
Date: Fri, 26 Jun 2020 14:11:28 -0300 [thread overview]
Message-ID: <20200626171130.27346-1-ezequiel@collabora.com> (raw)
Hi all,
Small patchset to add a check at TRY_EXT_CTRLS time,
via the H264 SPS control and reject unsupported bitstreams.
Properly refusing to decode unsupported bitstreams
allows applications to cleanly fallback to software
decoding.
Note that Rockchip VDEC hardware is capable of decoding High-10
and High-422 bitstreams. This needs more work, so for now
they are refused.
The same approach can be use on Cedrus, but since I'm not
very familiar there, I'll leave that to others.
Applies on top of media master.
Ezequiel Garcia (2):
rkvdec: h264: Refuse to decode unsupported bitstream
hantro: h264: Refuse to decode unsupported bitstream
drivers/staging/media/hantro/hantro_drv.c | 29 ++++++++++++++++++++---
drivers/staging/media/rkvdec/rkvdec.c | 27 +++++++++++++++++++++
2 files changed, 53 insertions(+), 3 deletions(-)
--
2.26.0.rc2
next reply other threads:[~2020-06-26 17:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 17:11 Ezequiel Garcia [this message]
2020-06-26 17:11 ` [PATCH 1/2] rkvdec: h264: Refuse to decode unsupported bitstream Ezequiel Garcia
2020-07-06 9:45 ` Jonas Karlman
2020-07-06 19:19 ` Ezequiel Garcia
2020-06-26 17:11 ` [PATCH 2/2] hantro: " Ezequiel Garcia
2020-06-29 9:12 ` Philipp Zabel
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=20200626171130.27346-1-ezequiel@collabora.com \
--to=ezequiel@collabora.com \
--cc=hverkuil@xs4all.nl \
--cc=jonas@kwiboo.se \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=nicolas.dufresne@collabora.com \
--cc=p.zabel@pengutronix.de \
/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).