From: Dafna Hirschfeld <dafna3@gmail.com>
To: linux-media@vger.kernel.org
Cc: hverkuil@xs4all.nl, helen.koike@collabora.com,
Dafna Hirschfeld <dafna3@gmail.com>
Subject: [PATCH 0/9] media: vicodec: add support to stateless decoder
Date: Sat, 9 Feb 2019 05:54:18 -0800 [thread overview]
Message-ID: <20190209135427.20630-1-dafna3@gmail.com> (raw)
Changes from previous sets:
---------------------------
Patch 3 - (keep the ref frame according to the format in decoder):
-----------------------------------------------------------------
Move the code that copies the capture buffer to the reference buffer
to a separate function 'copy_cap_to_ref'
Patches 4-6 - fixes according to the code review.
Patch 5 (Introducing stateless fwht defs and struct):
-----------------------------------------------------
add width,height fields to v4l2_ctrl_fwht_params
Patches 7-9 are new
Dafna Hirschfeld (9):
media: vicodec: Move raw frame preparation code to a function
media: vicodec: add field 'buf' to fwht_raw_frame
media: vicodec: keep the ref frame according to the format in decoder
media: vicodec: add struct for encoder/decoder instance
media: vicodec: Introducing stateless fwht defs and structs
media: vicodec: Register another node for stateless decoder
media: vb2: Add func that return buffer by timestamp
media: vicodec: call v4l2_m2m_buf_copy_metadata also upon error
media: vicodec: Add support for stateless decoder.
.../media/common/videobuf2/videobuf2-v4l2.c | 14 +
drivers/media/platform/vicodec/codec-fwht.c | 68 ++-
drivers/media/platform/vicodec/codec-fwht.h | 11 +-
.../media/platform/vicodec/codec-v4l2-fwht.c | 416 +++++-----------
.../media/platform/vicodec/codec-v4l2-fwht.h | 3 +
drivers/media/platform/vicodec/vicodec-core.c | 465 +++++++++++++-----
drivers/media/v4l2-core/v4l2-ctrls.c | 6 +
include/media/videobuf2-v4l2.h | 3 +
include/uapi/linux/v4l2-controls.h | 12 +
include/uapi/linux/videodev2.h | 1 +
10 files changed, 555 insertions(+), 444 deletions(-)
--
2.17.1
next reply other threads:[~2019-02-09 13:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 13:54 Dafna Hirschfeld [this message]
2019-02-09 13:54 ` [PATCH 1/9] media: vicodec: Move raw frame preparation code to a function Dafna Hirschfeld
2019-02-09 13:54 ` [PATCH 2/9] media: vicodec: add field 'buf' to fwht_raw_frame Dafna Hirschfeld
2019-02-09 13:54 ` [PATCH 3/9] media: vicodec: keep the ref frame according to the format in decoder Dafna Hirschfeld
2019-02-09 13:54 ` [PATCH 4/9] media: vicodec: add struct for encoder/decoder instance Dafna Hirschfeld
2019-02-11 8:31 ` Hans Verkuil
2019-02-09 13:54 ` [PATCH 5/9] media: vicodec: Introducing stateless fwht defs and structs Dafna Hirschfeld
2019-02-09 13:54 ` [PATCH 6/9] media: vicodec: Register another node for stateless decoder Dafna Hirschfeld
2019-02-11 8:31 ` Hans Verkuil
2019-02-09 13:54 ` [PATCH 7/9] media: vb2: Add func that return buffer by timestamp Dafna Hirschfeld
2019-02-11 10:11 ` Hans Verkuil
2019-02-09 13:54 ` [PATCH 8/9] media: vicodec: call v4l2_m2m_buf_copy_metadata also upon error Dafna Hirschfeld
2019-02-09 13:54 ` [PATCH 9/9] media: vicodec: Add support for stateless decoder Dafna Hirschfeld
2019-02-11 10:09 ` 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=20190209135427.20630-1-dafna3@gmail.com \
--to=dafna3@gmail.com \
--cc=helen.koike@collabora.com \
--cc=hverkuil@xs4all.nl \
--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;
as well as URLs for NNTP newsgroup(s).