From: Dafna Hirschfeld <dafna3@gmail.com>
To: helen.koike@collabora.com, hverkuil@xs4all.nl, mchehab@kernel.org
Cc: Dafna Hirschfeld <dafna3@gmail.com>, outreachy-kernel@googlegroups.com
Subject: [PATCH vicodec v3 0/3] Add support to more pixel formats in vicodec
Date: Sat, 3 Nov 2018 22:50:26 +0200 [thread overview]
Message-ID: <cover.1541277502.git.dafna3@gmail.com> (raw)
The new supported formats are
V4L2_PIX_FMT_GREY, V4L2_PIX_FMT_ARGB32, V4L2_PIX_FMT_ABGR32.
The returned encoded format is chaned to support various numbers
of planes instead of assuming 3 planes.
The first patch adds new fields to structs.
The second patch adds support for V4L2_PIX_FMT_GREY.
The third patch adds support for V4L2_PIX_FMT_ARGB32, V4L2_PIX_FMT_ABGR32.
Changes from v2:
patch 1,3: - no change
patch 2: bug fix - replace a test 'flags | FWHT_FL_COMPONENTS_NUM_BIT[01]'
with the test 'flags & FWHT_FL_COMPONENTS_NUM_BIT[01]'
Dafna Hirschfeld (3):
media: vicodec: prepare support for various number of planes
media: vicodec: Add support of greyscale format
media: vicodec: Add support for 4 planes formats
drivers/media/platform/vicodec/codec-fwht.c | 73 +++++++----
drivers/media/platform/vicodec/codec-fwht.h | 15 ++-
.../media/platform/vicodec/codec-v4l2-fwht.c | 123 +++++++++++++-----
.../media/platform/vicodec/codec-v4l2-fwht.h | 3 +-
drivers/media/platform/vicodec/vicodec-core.c | 35 ++++-
5 files changed, 182 insertions(+), 67 deletions(-)
--
2.17.1
next reply other threads:[~2018-11-03 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-03 20:50 Dafna Hirschfeld [this message]
2018-11-03 20:50 ` [PATCH vicodec v3 1/3] media: vicodec: prepare support for various number of planes Dafna Hirschfeld
2018-11-03 20:50 ` [PATCH vicodec v3 2/3] media: vicodec: Add support of greyscale format Dafna Hirschfeld
2018-11-05 12:07 ` Hans Verkuil
2018-11-03 20:50 ` [PATCH vicodec v3 3/3] media: vicodec: Add support for 4 planes formats Dafna Hirschfeld
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=cover.1541277502.git.dafna3@gmail.com \
--to=dafna3@gmail.com \
--cc=helen.koike@collabora.com \
--cc=hverkuil@xs4all.nl \
--cc=mchehab@kernel.org \
--cc=outreachy-kernel@googlegroups.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 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.