From: Francesco Lavra <francescolavra.fl@gmail.com>
To: sumit.semwal@ti.com
Cc: sumit.semwal@linaro.org, linaro-mm-sig@lists.linaro.org,
dri-devel@lists.freedesktop.org, linux-media@vger.kernel.org
Subject: Re: [Linaro-mm-sig] [PATCH] dma-buf: Add debugfs support
Date: Sun, 16 Dec 2012 17:56:49 +0100 [thread overview]
Message-ID: <50CDFD51.3030800@gmail.com> (raw)
In-Reply-To: <1355477817-5750-1-git-send-email-sumit.semwal@ti.com>
Hi,
On 12/14/2012 10:36 AM, sumit.semwal@ti.com wrote:
> From: Sumit Semwal <sumit.semwal@linaro.org>
>
> Add debugfs support to make it easier to print debug information
> about the dma-buf buffers.
>
> Signed-off-by: Sumit Semwal <sumit.semwal@ti.com>
> ---
> drivers/base/dma-buf.c | 149 +++++++++++++++++++++++++++++++++++++++++++++++
> include/linux/dma-buf.h | 6 +-
> 2 files changed, 154 insertions(+), 1 deletion(-)
[...]
> diff --git a/include/linux/dma-buf.h b/include/linux/dma-buf.h
> index bd2e52c..160453f 100644
> --- a/include/linux/dma-buf.h
> +++ b/include/linux/dma-buf.h
> @@ -112,6 +112,7 @@ struct dma_buf_ops {
> * @file: file pointer used for sharing buffers across, and for refcounting.
> * @attachments: list of dma_buf_attachment that denotes all devices attached.
> * @ops: dma_buf_ops associated with this buffer object.
> + * @list_node: node for dma_buf accounting and debugging.
> * @priv: exporter specific private data for this buffer object.
> */
> struct dma_buf {
> @@ -121,6 +122,8 @@ struct dma_buf {
> const struct dma_buf_ops *ops;
> /* mutex to serialize list manipulation and attach/detach */
> struct mutex lock;
> +
> + struct list_head list_node;
> void *priv;
> };
>
> @@ -183,5 +186,6 @@ int dma_buf_mmap(struct dma_buf *, struct vm_area_struct *,
> unsigned long);
> void *dma_buf_vmap(struct dma_buf *);
> void dma_buf_vunmap(struct dma_buf *, void *vaddr);
> -
> +int dma_buf_debugfs_create_file(const char *name,
> + int (*write)(struct seq_file *));
Why is this function declared in the public header file?
--
Francesco
next prev parent reply other threads:[~2012-12-16 16:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 9:36 [PATCH] dma-buf: Add debugfs support sumit.semwal
2012-12-14 10:29 ` Daniel Vetter
2012-12-14 10:34 ` Daniel Vetter
2012-12-17 8:56 ` Sumit Semwal
2012-12-14 11:57 ` [Linaro-mm-sig] " Maarten Lankhorst
2012-12-14 14:11 ` Rob Clark
2012-12-14 14:35 ` Maarten Lankhorst
[not found] ` <CAO_48GFBEEz1J_o=ZRcBh8rdFUj=eQ7Gr8s0sfL9RpHjZigamA@mail.gmail.com>
2012-12-17 8:57 ` Sumit Semwal
2012-12-16 16:56 ` Francesco Lavra [this message]
2012-12-20 1:26 ` Dave Airlie
2012-12-20 3:13 ` Dave Airlie
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=50CDFD51.3030800@gmail.com \
--to=francescolavra.fl@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-media@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=sumit.semwal@ti.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).