From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org
Cc: damm@igel.co.jp, hannes@cmpxchg.org, hverkuil@xs4all.nl,
lethal@linux-sh.org, mchehab@infradead.org
Subject: + videobuf-dma-contig-zero-copy-userptr-support-v3-comments.patch added to -mm tree
Date: Tue, 12 May 2009 14:49:11 -0700 [thread overview]
Message-ID: <200905122149.n4CLnBrx005519@imap1.linux-foundation.org> (raw)
The patch titled
videobuf-dma-contig: zero copy USERPTR V3 comments
has been added to the -mm tree. Its filename is
videobuf-dma-contig-zero-copy-userptr-support-v3-comments.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: videobuf-dma-contig: zero copy USERPTR V3 comments
From: Magnus Damm <damm@igel.co.jp>
This patch adds function descriptions to V3 of the V4L2
videobuf-dma-contig USERPTR zero copy patch.
Signed-off-by: Magnus Damm <damm@igel.co.jp>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: Paul Mundt <lethal@linux-sh.org>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Hans Verkuil <hverkuil@xs4all.nl>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/media/video/videobuf-dma-contig.c | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff -puN drivers/media/video/videobuf-dma-contig.c~videobuf-dma-contig-zero-copy-userptr-support-v3-comments drivers/media/video/videobuf-dma-contig.c
--- a/drivers/media/video/videobuf-dma-contig.c~videobuf-dma-contig-zero-copy-userptr-support-v3-comments
+++ a/drivers/media/video/videobuf-dma-contig.c
@@ -110,6 +110,12 @@ static struct vm_operations_struct video
.close = videobuf_vm_close,
};
+/**
+ * videobuf_dma_contig_user_put() - reset pointer to user space buffer
+ * @mem: per-buffer private videobuf-dma-contig data
+ *
+ * This function resets the user space pointer
+ */
static void videobuf_dma_contig_user_put(struct videobuf_dma_contig_memory *mem)
{
mem->is_userptr = 0;
@@ -117,6 +123,16 @@ static void videobuf_dma_contig_user_put
mem->size = 0;
}
+/**
+ * videobuf_dma_contig_user_get() - setup user space memory pointer
+ * @mem: per-buffer private videobuf-dma-contig data
+ * @vb: video buffer to map
+ *
+ * This function validates and sets up a pointer to user space memory.
+ * Only physically contiguous pfn-mapped memory is accepted.
+ *
+ * Returns 0 if successful.
+ */
static int videobuf_dma_contig_user_get(struct videobuf_dma_contig_memory *mem,
struct videobuf_buffer *vb)
{
_
Patches currently in -mm which might be from damm@igel.co.jp are
linux-next.patch
videobuf-dma-contig-zero-copy-userptr-support-v3.patch
videobuf-dma-contig-zero-copy-userptr-support-v3-comments.patch
reply other threads:[~2009-05-12 21:52 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=200905122149.n4CLnBrx005519@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=damm@igel.co.jp \
--cc=hannes@cmpxchg.org \
--cc=hverkuil@xs4all.nl \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mm-commits@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.