From: Randy Dunlap <rdunlap@infradead.org>
To: Gerd Hoffmann <kraxel@redhat.com>, dri-devel@lists.freedesktop.org
Cc: laurent.pinchart@ideasonboard.com, daniel@ffwll.ch,
Sumit Semwal <sumit.semwal@linaro.org>,
Jonathan Corbet <corbet@lwn.net>,
"open list:DMA BUFFER SHARING FRAMEWORK"
<linux-media@vger.kernel.org>,
"moderated list:DMA BUFFER SHARING FRAMEWORK"
<linaro-mm-sig@lists.linaro.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/3] udmabuf: add documentation
Date: Wed, 12 Sep 2018 09:40:37 -0700 [thread overview]
Message-ID: <4d4ffe16-f46d-5dda-68b6-38f59e228214@infradead.org> (raw)
In-Reply-To: <20180912063316.21047-2-kraxel@redhat.com>
Hi Gerd,
Missed one from yesterday:
On 9/11/18 11:33 PM, Gerd Hoffmann wrote:
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
> include/uapi/linux/udmabuf.h | 51 +++++++++++++++++++++++++++++++++---
> Documentation/driver-api/dma-buf.rst | 8 ++++++
> 2 files changed, 56 insertions(+), 3 deletions(-)
>
> diff --git a/include/uapi/linux/udmabuf.h b/include/uapi/linux/udmabuf.h
> index 46b6532ed8..281e2c52f1 100644
> --- a/include/uapi/linux/udmabuf.h
> +++ b/include/uapi/linux/udmabuf.h
> @@ -5,8 +5,39 @@
> #include <linux/types.h>
> #include <linux/ioctl.h>
>
> +/**
> + * DOC: udmabuf
> + *
> + * udmabuf is a device driver which allows userspace to create
> + * dmabufs. The memory used for these dmabufs must be backed by
> + * memfd. The memfd must have F_SEAL_SHRINK and it must not have
> + * F_SEAL_WRITE.
> + *
> + * The driver has two ioctls, one to create a dmabuf from a single
> + * memory block and one to create a dmabuf from a list of memory
> + * blocks.
> + *
> + * UDMABUF_CREATE - _IOW('u', 0x42, udmabuf_create)
> + *
> + * UDMABUF_CREATE_LIST - _IOW('u', 0x43, udmabuf_create_list)
> + */
> +
> +#define UDMABUF_CREATE _IOW('u', 0x42, struct udmabuf_create)
> +#define UDMABUF_CREATE_LIST _IOW('u', 0x43, struct udmabuf_create_list)
> +
> #define UDMABUF_FLAGS_CLOEXEC 0x01
>
> +/**
> + * struct udmabuf_create - create a dmabuf from a single memory block.
> + *
> + * @memfd: The file handle.
> + * @offset: Start of the buffer (from memfd start).
> + * Must be page aligned.
> + * @size: Size of the buffer. Must be rounded to page size.
> + *
> + * @flags:
> + * UDMABUF_FLAGS_CLOEXEC: set CLOEXEC flag for the dmabuf.
> + */
> struct udmabuf_create {
> __u32 memfd;
> __u32 flags;
> @@ -14,6 +45,14 @@ struct udmabuf_create {
> __u64 size;
> };
>
> +/**
> + * struct udmabuf_create_item - one memory block list item.
> + *
> + * @memfd: The file handle.
> + * @offset: Start of the buffer (from memfd start).
> + * Must be page aligned.
> + * @size: Size of the buffer. Must be rounded to page size.
> + */
> struct udmabuf_create_item {
> __u32 memfd;
> __u32 __pad;
> @@ -21,13 +60,19 @@ struct udmabuf_create_item {
> __u64 size;
> };
>
> +/**
> + * struct udmabuf_create_list - create a dmabuf from a memory block list.
> + *
> + * @count: The number of list elements.
> + * @list: The memory block list
> + *
> + * flags:
@flags:
> + * UDMABUF_FLAGS_CLOEXEC: set CLOEXEC flag for the dmabuf.
> + */
> struct udmabuf_create_list {
> __u32 flags;
> __u32 count;
> struct udmabuf_create_item list[];
> };
--
~Randy
prev parent reply other threads:[~2018-09-12 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180912063316.21047-1-kraxel@redhat.com>
2018-09-12 6:33 ` [PATCH v3 1/3] udmabuf: add documentation Gerd Hoffmann
2018-09-12 16:40 ` Randy Dunlap [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=4d4ffe16-f46d-5dda-68b6-38f59e228214@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=sumit.semwal@linaro.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;
as well as URLs for NNTP newsgroup(s).