All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Gustavo Padovan <gustavo.padovan@collabora.co.uk>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: dma-buf/sync_file: de-stage sync_file
Date: Wed, 25 May 2016 22:42:09 -0400	[thread overview]
Message-ID: <20160526024209.GA2840@codemonkey.org.uk> (raw)
In-Reply-To: <20160521053153.14B99661B7C@gitolite.kernel.org>

On Sat, May 21, 2016 at 05:31:53AM +0000, Linux Kernel wrote:
 
 >     dma-buf/sync_file: de-stage sync_file
 >     
 >     sync_file is useful to connect one or more fences to the file. The file is
 >     used by userspace to track fences between drivers that share DMA bufs.
 >     
 >     Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
 >     Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
 >     Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 ...
 
 > +config SYNC_FILE
 > +	bool "sync_file support for fences"
 > +	default n
 > +	select ANON_INODES
 > +	select DMA_SHARED_BUFFER
 > +	---help---
 > +	  This option enables the fence framework synchronization to export
 > +	  sync_files to userspace that can represent one or more fences.

For such a generic sounding CONFIG_ item, this is one of the more obtuse descriptions
in a kconfig we've had in a while, and the commit message doesn't give any more
clues as to why anyone might want to enable this.

I'm guessing this is some graphics thing given that Daniel reviewed it.
>From skimming the other commits, it seems to be some Android thing ?
Are there depends missing perhaps that might make this more obvious ?

Could you elaborate in the help text why someone might want to enable this ?
As is, it's just a bunch of words with no context for anyone who isn't
close to whatever domain this came from.

	Dave

       reply	other threads:[~2016-05-26  2:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160521053153.14B99661B7C@gitolite.kernel.org>
2016-05-26  2:42 ` Dave Jones [this message]
2016-05-27 21:06   ` dma-buf/sync_file: de-stage sync_file Gustavo Padovan

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=20160526024209.GA2840@codemonkey.org.uk \
    --to=davej@codemonkey.org.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=gregkh@linuxfoundation.org \
    --cc=gustavo.padovan@collabora.co.uk \
    --cc=linux-kernel@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.