linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
	"Tomasz Stanislawski/Poland R&D Center-Linux (MSS)/./????"
	<t.stanislaws@samsung.com>
Subject: [GIT PULL FOR 3.5] DMABUF importer feature in V4L2 API
Date: Tue, 15 May 2012 17:45:19 +0200	[thread overview]
Message-ID: <4FB27A0F.9060700@samsung.com> (raw)

Hi Mauro,

The following patch series adds DMABUF importer role to V4L2 API.
I'm sending this on behalf of Tomasz Stanislawski. Please pull for v3.5.

The following changes since commit d509835e32bd761a2b7b446034a273da568e5573:

  [media] media: mx2_camera: Fix mbus format handling (2012-05-15 09:42:17 -0300)

are available in the git repository at:

  git://git.infradead.org/users/kmpark/linux-samsung v4l2_dmabuf

for you to fetch changes up to ac768fa8ad56774b0084dccb727b515e23e467cd:

  v4l: s5p-fimc: support for dmabuf importing (2012-05-15 15:46:49 +0200)

----------------------------------------------------------------
Andrzej Pietrasiewicz (1):
      v4l: vb2-dma-contig: add support for scatterlist in userptr mode

Laurent Pinchart (2):
      v4l: vb2-dma-contig: Shorten vb2_dma_contig prefix to vb2_dc
      v4l: vb2-dma-contig: Reorder functions

Marek Szyprowski (2):
      v4l: vb2: add prepare/finish callbacks to allocators
      v4l: vb2-dma-contig: add prepare/finish to dma-contig allocator

Sumit Semwal (4):
      v4l: Add DMABUF as a memory type
      v4l: vb2: add support for shared buffer (dma_buf)
      v4l: vb: remove warnings about MEMORY_DMABUF
      v4l: vb2-dma-contig: add support for dma_buf importing

Tomasz Stanislawski (4):
      Documentation: media: description of DMABUF importing in V4L2
      v4l: vb2-dma-contig: Remove unneeded allocation context structure
      v4l: s5p-tv: mixer: support for dmabuf importing
      v4l: s5p-fimc: support for dmabuf importing

 Documentation/DocBook/media/v4l/compat.xml             |    4 +
 Documentation/DocBook/media/v4l/io.xml                 |  179
+++++++++++++++++++++++++++++++
 Documentation/DocBook/media/v4l/vidioc-create-bufs.xml |    1 +
 Documentation/DocBook/media/v4l/vidioc-qbuf.xml        |   15 +++
 Documentation/DocBook/media/v4l/vidioc-reqbufs.xml     |   45 ++++----
 drivers/media/video/Kconfig                            |    1 +
 drivers/media/video/s5p-fimc/fimc-capture.c            |    2 +-
 drivers/media/video/s5p-tv/Kconfig                     |    1 +
 drivers/media/video/s5p-tv/mixer_video.c               |    2 +-
 drivers/media/video/videobuf-core.c                    |    4 +
 drivers/media/video/videobuf2-core.c                   |  207
+++++++++++++++++++++++++++++++++++-
 drivers/media/video/videobuf2-dma-contig.c             |  518
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------------
 include/linux/videodev2.h                              |    7 ++
 include/media/videobuf2-core.h                         |   34 ++++++
 14 files changed, 921 insertions(+), 99 deletions(-)

--
Regards,
Sylwester

                 reply	other threads:[~2012-05-15 15:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4FB27A0F.9060700@samsung.com \
    --to=s.nawrocki@samsung.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=t.stanislaws@samsung.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).