All of lore.kernel.org
 help / color / mirror / Atom feed
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 v6 0/5] media: vicodec: source change support
Date: Mon, 21 Jan 2019 03:46:13 -0800	[thread overview]
Message-ID: <20190121114618.115282-1-dafna3@gmail.com> (raw)

Changes from v5
cleanups of 'line too long' warnings'

Dafna Hirschfeld (5):
  media: vicodec: add support for CROP and COMPOSE selection
  media: vicodec: use 3 bits for the number of components
  media: vicodec: Add pixel encoding flags to fwht header
  media: vicodec: Separate fwht header from the frame data
  media: vicodec: Add support for resolution change event.

 drivers/media/platform/vicodec/codec-fwht.c   |  83 ++-
 drivers/media/platform/vicodec/codec-fwht.h   |  25 +-
 .../media/platform/vicodec/codec-v4l2-fwht.c  | 388 +++++++----
 .../media/platform/vicodec/codec-v4l2-fwht.h  |  14 +-
 drivers/media/platform/vicodec/vicodec-core.c | 626 ++++++++++++++----
 5 files changed, 835 insertions(+), 301 deletions(-)

-- 
2.17.1


             reply	other threads:[~2019-01-21 11:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21 11:46 Dafna Hirschfeld [this message]
2019-01-21 11:46 ` [PATCH v6 1/5] media: vicodec: add support for CROP and COMPOSE selection Dafna Hirschfeld
2019-01-21 11:46 ` [PATCH v6 2/5] media: vicodec: use 3 bits for the number of components Dafna Hirschfeld
2019-01-21 11:46 ` [PATCH v6 3/5] media: vicodec: Add pixel encoding flags to fwht header Dafna Hirschfeld
2019-01-21 11:46 ` [PATCH v6 4/5] media: vicodec: Separate fwht header from the frame data Dafna Hirschfeld
2019-01-21 11:46 ` [PATCH v6 5/5] media: vicodec: Add support for resolution change event 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=20190121114618.115282-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 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.