From: Ezequiel Garcia <ezequiel@collabora.com>
To: linux-media@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Tomasz Figa <tfiga@chromium.org>,
kernel@collabora.com, Jonas Karlman <jonas@kwiboo.se>,
Heiko Stuebner <heiko@sntech.de>,
Hans Verkuil <hverkuil@xs4all.nl>,
Alexandre Courbot <acourbot@chromium.org>,
Jeffrey Kardatzke <jkardatzke@chromium.org>,
gustavo.padovan@collabora.com,
Ezequiel Garcia <ezequiel@collabora.com>
Subject: [PATCH v3 0/3] media: rkvdec: Add a VP9 backend
Date: Tue, 5 May 2020 10:41:07 -0300 [thread overview]
Message-ID: <20200505134110.3435-1-ezequiel@collabora.com> (raw)
Third iteration of the VP9 stateless codec uAPI, plus
support for Rockchip VDEC.
This series addresses an issue I found while testing,
not sure how it slipped before! See patch 1.
Keep in mind the same issue should likely be fixed
on Hantro and Cedrus. We can create a helper for it
as a follow-up.
Other than that, minor documentation and smatch-detected
warnings are fixed.
Thanks!
Ezequiel
Changelog
---------
v3:
* Fix documentation issues found by Hans.
* Fix smatch detected issues as pointed out by Hans.
* Added patch to fix wrong bytesused set on .buf_prepare.
v2:
* Documentation style issues pointed out by Nicolas internally.
* s/VP9_PROFILE_MAX/V4L2_VP9_PROFILE_MAX/
* Fix wrong kfree(ctx).
* constify a couple structs on rkvdec-vp9.c
Boris Brezillon (2):
media: uapi: Add VP9 stateless decoder controls
media: rkvdec: Add the VP9 backend
Ezequiel Garcia (1):
media: rkvdec: Fix .buf_prepare
.../userspace-api/media/v4l/biblio.rst | 10 +
.../media/v4l/ext-ctrls-codec.rst | 581 ++++++
drivers/media/v4l2-core/v4l2-ctrls.c | 242 +++
drivers/media/v4l2-core/v4l2-ioctl.c | 1 +
drivers/staging/media/rkvdec/Makefile | 2 +-
drivers/staging/media/rkvdec/rkvdec-vp9.c | 1577 +++++++++++++++++
drivers/staging/media/rkvdec/rkvdec.c | 66 +-
drivers/staging/media/rkvdec/rkvdec.h | 6 +
include/media/v4l2-ctrls.h | 1 +
include/media/vp9-ctrls.h | 510 ++++++
10 files changed, 2991 insertions(+), 5 deletions(-)
create mode 100644 drivers/staging/media/rkvdec/rkvdec-vp9.c
create mode 100644 include/media/vp9-ctrls.h
--
2.26.0.rc2
next reply other threads:[~2020-05-05 13:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 13:41 Ezequiel Garcia [this message]
2020-05-05 13:41 ` [PATCH v3 1/3] media: rkvdec: Fix .buf_prepare Ezequiel Garcia
2020-05-05 13:56 ` Tomasz Figa
2020-05-05 13:59 ` Ezequiel Garcia
2020-05-05 14:05 ` Tomasz Figa
2020-05-05 14:27 ` Ezequiel Garcia
2020-05-13 23:38 ` Nicolas Dufresne
2020-05-14 14:50 ` Nicolas Dufresne
2020-05-05 13:41 ` [PATCH v3 2/3] media: uapi: Add VP9 stateless decoder controls Ezequiel Garcia
2020-05-08 10:27 ` Hans Verkuil
2020-05-08 12:28 ` Ezequiel Garcia
2020-05-08 13:16 ` Hans Verkuil
2020-05-11 12:17 ` Nicolas Dufresne
2020-05-05 13:41 ` [PATCH v3 3/3] media: rkvdec: Add the VP9 backend Ezequiel Garcia
2020-05-08 10:34 ` Hans Verkuil
2020-05-08 16:26 ` Ezequiel Garcia
2020-05-08 16:56 ` Tomasz Figa
2020-05-11 13:26 ` Ezequiel Garcia
2020-05-08 11:21 ` Jonas Karlman
2020-05-08 11:21 ` Jonas Karlman
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=20200505134110.3435-1-ezequiel@collabora.com \
--to=ezequiel@collabora.com \
--cc=acourbot@chromium.org \
--cc=gustavo.padovan@collabora.com \
--cc=heiko@sntech.de \
--cc=hverkuil@xs4all.nl \
--cc=jkardatzke@chromium.org \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.