public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Kamil Debski <k.debski@samsung.com>
To: linux-media@vger.kernel.org
Subject: [GIT PULL] mem2mem changes
Date: Fri, 30 Jan 2015 15:45:00 +0100	[thread overview]
Message-ID: <035d01d03c9b$535b8a90$fa129fb0$%debski@samsung.com> (raw)

The following changes since commit a5f43c18fceb2b96ec9fddb4348f5282a71cf2b0:

  [media] Documentation/video4linux: remove obsolete text files (2015-01-29
19:16:30 -0200)

are available in the git repository at:

  git://linuxtv.org/kdebski/media_tree_2.git for-3.20-a

for you to fetch changes up to 403655cc66ee4497cdd7045d71bf1376e88c5909:

  coda: simplify check in coda_buf_queue (2015-01-30 15:14:55 +0100)

----------------------------------------------------------------
Fabian Frederick (2):
      s5p-g2d: remove unnecessary version.h inclusion
      s5p-mfc: remove unnecessary version.h inclusion

Lucas Stach (1):
      coda: adjust sequence offset after unexpected decoded frame

Markus Pargmann (1):
      coda: fix width validity check when starting to decode

Nicolas Dufresne (3):
      s5p-mfc-v6+: Use display_delay_enable CID
      s5p-mfc-dec: Don't use encoder stop command
      media-doc: Fix MFC display delay control doc

Philipp Zabel (18):
      coda: fix encoder rate control parameter masks
      coda: remove context debugfs entry last
      coda: move meta out of padding
      coda: fix job_ready debug reporting for bitstream decoding
      coda: fix try_fmt_vid_out colorspace setting
      coda: properly clear f_cap in coda_s_fmt_vid_out
      coda: initialize SRAM on probe
      coda: clear RET_DEC_PIC_SUCCESS flag in prepare_decode
      coda: remove unused isequence, reset qsequence in stop_streaming
      coda: issue seq_end_work during stop_streaming
      coda: don't ever use subsampling ping-pong buffers as reconstructed
reference buffers
      coda: add coda_estimate_sizeimage and use it in set_defaults
      coda: switch BIT decoder source queue to vmalloc
      coda: make seq_end_work optional
      coda: free context buffers under buffer mutex
      coda: add support for contexts that do not use the BIT processor
      coda: allocate bitstream ringbuffer only for BIT decoder
      coda: simplify check in coda_buf_queue

 Documentation/DocBook/media/v4l/controls.xml    |   11 +-
 drivers/media/platform/Kconfig                  |    1 +
 drivers/media/platform/coda/coda-bit.c          |   25 +++-
 drivers/media/platform/coda/coda-common.c       |  159
+++++++++++++++--------
 drivers/media/platform/coda/coda.h              |    2 +-
 drivers/media/platform/coda/coda_regs.h         |    4 +-
 drivers/media/platform/s5p-g2d/g2d.c            |    1 -
 drivers/media/platform/s5p-mfc/s5p_mfc_dec.c    |    3 +-
 drivers/media/platform/s5p-mfc/s5p_mfc_enc.c    |    1 -
 drivers/media/platform/s5p-mfc/s5p_mfc_opr_v6.c |    6 +-
 10 files changed, 136 insertions(+), 77 deletions(-)


             reply	other threads:[~2015-01-30 14:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-30 14:45 Kamil Debski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-07-01 12:41 [GIT PULL] mem2mem changes Kamil Debski
2016-06-07 15:31 Kamil Debski
2015-12-18 17:22 Kamil Debski
2014-11-05 10:19 Kamil Debski

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='035d01d03c9b$535b8a90$fa129fb0$%debski@samsung.com' \
    --to=k.debski@samsung.com \
    --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