From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Nicolas Dufresne <nicolas@ndufresne.ca>
Cc: linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/2] Add V4L stateless video decoder API support to NVIDIA Tegra driver
Date: Wed, 12 Jan 2022 18:39:50 +0300 [thread overview]
Message-ID: <20220112153952.1291-1-digetx@gmail.com> (raw)
Support V4L stateless video decoder API by NVIDIA Tegra decoder driver.
Tested using GStreamer [1] and libvdpau-tegra [2].
[1] https://github.com/grate-driver/gstreamer/commit/b8509bdbb69b534e61419ea1798f32f9ad2f3597
[2] https://github.com/grate-driver/libvdpau-tegra/commit/f822e95911e5e0c39f8ba19f843ddc1e0138d5ce
Dmitry Osipenko (2):
media: staging: tegra-vde: Factor out H.264 code
media: staging: tegra-vde: Support V4L stateless video decoder API
drivers/staging/media/tegra-vde/Kconfig | 7 +
drivers/staging/media/tegra-vde/Makefile | 2 +-
drivers/staging/media/tegra-vde/h264.c | 988 ++++++++++++++++
drivers/staging/media/tegra-vde/h264_reader.c | 264 +++++
drivers/staging/media/tegra-vde/v4l2.c | 1013 +++++++++++++++++
drivers/staging/media/tegra-vde/vde.c | 700 ++----------
drivers/staging/media/tegra-vde/vde.h | 129 +++
7 files changed, 2487 insertions(+), 616 deletions(-)
create mode 100644 drivers/staging/media/tegra-vde/h264.c
create mode 100644 drivers/staging/media/tegra-vde/h264_reader.c
create mode 100644 drivers/staging/media/tegra-vde/v4l2.c
--
2.33.1
next reply other threads:[~2022-01-12 15:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 15:39 Dmitry Osipenko [this message]
2022-01-12 15:39 ` [PATCH v1 1/2] media: staging: tegra-vde: Factor out H.264 code Dmitry Osipenko
2022-01-12 15:39 ` [PATCH v1 2/2] media: staging: tegra-vde: Support V4L stateless video decoder API Dmitry Osipenko
2022-01-12 16:49 ` Nicolas Dufresne
2022-01-12 19:04 ` Dmitry Osipenko
2022-01-18 2:43 ` Nicolas Dufresne
2022-01-18 10:43 ` Dmitry Osipenko
2022-01-12 20:05 ` kernel test robot
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=20220112153952.1291-1-digetx@gmail.com \
--to=digetx@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-tegra@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nicolas@ndufresne.ca \
--cc=thierry.reding@gmail.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).