linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: linux-media@vger.kernel.org
Cc: pawel@osciak.com, laurent.pinchart@ideasonboard.com,
	m.szyprowski@samsung.com
Subject: Re: [RFC PATCH 00/12] vb2: improve dma-sg, expbuf.
Date: Mon, 08 Sep 2014 16:47:55 +0200	[thread overview]
Message-ID: <540DC19B.30100@xs4all.nl> (raw)
In-Reply-To: <1410185681-20111-1-git-send-email-hverkuil@xs4all.nl>

On 09/08/2014 04:14 PM, Hans Verkuil wrote:
> The patch series adds an allocation context to dma-sg and uses that to move
> dma_(un)map_sg into the vb2 framework, which is where it belongs.
> 
> Related to that is the addition of buf_prepare/finish _for_cpu variants,
> where the _for_cpu ops are called when the buffer is synced for the cpu, and
> the others are called when it is synced to the device.
> 
> DMABUF export support is added to dma-sg and vmalloc, so now all memory
> models support DMABUF importing and exporting.
> 
> A new flag was added so drivers know when the DMA engine should be
> (re)programmed. This is primarily needed for the dma-sg memory model.

Note: patches for tw68 and cx23885 are missing but can be found in my repo:

http://git.linuxtv.org/cgit.cgi/hverkuil/media_tree.git/log/?h=vb2-prep

Those two drivers were merged/updated just after I posted my patch series :-)

Regards,

	Hans

> 
> Reviews are very welcome.
> 
> Regards,
> 
> 	Hans
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


      parent reply	other threads:[~2014-09-08 14:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-08 14:14 [RFC PATCH 00/12] vb2: improve dma-sg, expbuf Hans Verkuil
2014-09-08 14:14 ` [RFC PATCH 01/12] vb2: introduce buf_prepare/finish_for_cpu Hans Verkuil
2014-09-08 14:14 ` [RFC PATCH 02/12] vb2-dma-sg: add allocation context to dma-sg Hans Verkuil
2014-09-08 14:14 ` [RFC PATCH 03/12] vb2-dma-sg: add prepare/finish memops Hans Verkuil
2014-09-08 14:14 ` [RFC PATCH 04/12] vb2: memop prepare: return errors Hans Verkuil
2014-09-08 14:14 ` [RFC PATCH 05/12] vb2: call memop prepare before the buf_prepare op is called Hans Verkuil
2014-09-08 14:14 ` [RFC PATCH 06/12] vb2-dma-sg: add dmabuf import support Hans Verkuil
2014-09-14  6:55   ` Pawel Osciak
2014-09-08 14:14 ` [RFC PATCH 07/12] vb2-dma-sg: add get_dmabuf Hans Verkuil
2014-09-08 14:14 ` [RFC PATCH 08/12] vb2-vmalloc: add get_dmabuf support Hans Verkuil
2014-09-08 14:14 ` [RFC PATCH 09/12] vb2: replace 'write' by 'dma_dir' Hans Verkuil
2014-09-08 14:14 ` [RFC PATCH 10/12] vb2: add 'new_cookies' flag Hans Verkuil
2014-09-08 14:14 ` [RFC PATCH 11/12] saa7134: don't rebuild the page table unless new_cookies is set Hans Verkuil
2014-09-08 14:14 ` [RFC PATCH 12/12] vivid: enable vb2_expbuf support Hans Verkuil
2014-09-08 14:47 ` Hans Verkuil [this message]

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=540DC19B.30100@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=pawel@osciak.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).