linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: inki.dae@samsung.com (Inki Dae)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v2] dmabuf-sync: Introduce buffer synchronization framework
Date: Wed, 19 Jun 2013 14:45:15 +0900	[thread overview]
Message-ID: <008601ce6cb0$2c8cec40$85a6c4c0$%dae@samsung.com> (raw)
In-Reply-To: <1371548849.4276.6.camel@weser.hi.pengutronix.de>



> -----Original Message-----
> From: Lucas Stach [mailto:l.stach at pengutronix.de]
> Sent: Tuesday, June 18, 2013 6:47 PM
> To: Inki Dae
> Cc: 'Russell King - ARM Linux'; 'linux-fbdev'; 'Kyungmin Park'; 'DRI
> mailing list'; 'myungjoo.ham'; 'YoungJun Cho'; linux-arm-
> kernel at lists.infradead.org; linux-media at vger.kernel.org
> Subject: Re: [RFC PATCH v2] dmabuf-sync: Introduce buffer synchronization
> framework
> 
> Am Dienstag, den 18.06.2013, 18:04 +0900 schrieb Inki Dae:
> [...]
> >
> > > a display device driver.  It shouldn't be used within a single driver
> > > as a means of passing buffers between userspace and kernel space.
> >
> > What I try to do is not really such ugly thing. What I try to do is to
> > notify that, when CPU tries to access a buffer , to kernel side through
> > dmabuf interface. So it's not really to send the buffer to kernel.
> >
> > Thanks,
> > Inki Dae
> >
> The most basic question about why you are trying to implement this sort
> of thing in the dma_buf framework still stands.
> 
> Once you imported a dma_buf into your DRM driver it's a GEM object and
> you can and should use the native DRM ioctls to prepare/end a CPU access
> to this BO. Then internally to your driver you can use the dma_buf
> reservation/fence stuff to provide the necessary cross-device sync.
> 

I don't really want that is used only for DRM drivers. We really need it for all other DMA devices; i.e., v4l2 based drivers. That is what I try to do. And my approach uses reservation to use dma-buf resources but not dma fence stuff anymore. However, I'm looking into Radeon DRM driver for why we need dma fence stuff, and how we can use it if needed.

Thanks,
Inki Dae

> Regards,
> Lucas
> --
> Pengutronix e.K.                           | Lucas Stach                 |
> Industrial Linux Solutions                 | http://www.pengutronix.de/  |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5076 |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2013-06-19  5:45 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13  8:28 [RFC PATCH] dmabuf-sync: Introduce buffer synchronization framework Inki Dae
2013-06-13 11:25 ` Inki Dae
2013-06-13 17:26 ` Russell King - ARM Linux
2013-06-14  2:32   ` Inki Dae
2013-06-17 11:15 ` [RFC PATCH v2] " Inki Dae
2013-06-17 11:34   ` Maarten Lankhorst
2013-06-17 13:04     ` Inki Dae
2013-06-17 13:31       ` Russell King - ARM Linux
     [not found]         ` <CAAQKjZO_t_kZkU46bUPTpoJs_oE1KkEqS2OTrTYjjJYZzBf+XA@mail.gmail.com>
2013-06-17 15:42           ` Russell King - ARM Linux
2013-06-17 16:01             ` Russell King - ARM Linux
     [not found]             ` <CAAQKjZOokFKN85pygVnm7ShSa+O0ZzwxvQ0rFssgNLp+RO5pGg@mail.gmail.com>
2013-06-17 18:21               ` Russell King - ARM Linux
2013-06-18  5:27                 ` Inki Dae
2013-06-18  8:43                   ` Russell King - ARM Linux
2013-06-18  9:04                     ` Inki Dae
2013-06-18  9:38                       ` Russell King - ARM Linux
2013-06-18  9:47                       ` Lucas Stach
2013-06-19  5:45                         ` Inki Dae [this message]
2013-06-19 10:22                           ` Lucas Stach
2013-06-19 10:44                             ` Inki Dae
2013-06-19 12:34                               ` Lucas Stach
     [not found]                                 ` <CAAQKjZNJD4HpnJQ7iE+Gez36066M6U0YQeUEdA0+UcSOKqeghg@mail.gmail.com>
2013-06-19 18:29                                   ` Russell King - ARM Linux
2013-06-20  6:43                                     ` Inki Dae
2013-06-20  7:47                                       ` Lucas Stach
2013-06-20  8:17                                         ` Russell King - ARM Linux
2013-06-20  8:26                                           ` Lucas Stach
2013-06-20  8:24                                         ` Inki Dae
2013-06-20 10:11                                           ` Lucas Stach
2013-06-20 11:15                                             ` Inki Dae
2013-06-21  8:54                                               ` Lucas Stach
     [not found]                                                 ` <CAAQKjZOxOMuL3zh_yV7tU2LBcZ7oVryiKa+LgjTM5HLY+va8zQ@mail.gmail.com>
2013-06-21 12:27                                                   ` Lucas Stach
2013-06-21 16:55                                                     ` Inki Dae
2013-06-21 19:02                                                       ` Jerome Glisse
     [not found]                                                         ` <CAAQKjZNnJRddACHzD+VF=A8vJpt9SEy2ttnS3Kw0y3hexu8dnw@mail.gmail.com>
2013-06-25 11:32                                                           ` [RFC PATCH] " Rob Clark
2013-06-25 14:17                                                             ` Inki Dae
2013-06-25 14:49                                                               ` Jerome Glisse
2013-06-26 16:06                                                                 ` Inki Dae
2013-06-18  7:00             ` [RFC PATCH v2] " Daniel Vetter
2013-06-18 10:46               ` Russell King - ARM Linux
2013-06-25  9:23                 ` Daniel Vetter
2013-06-26 17:18                   ` Russell King - ARM Linux
2013-06-17 13:31       ` Maarten Lankhorst
2013-06-19  9:10   ` [RFC PATCH v3] " Inki Dae

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='008601ce6cb0$2c8cec40$85a6c4c0$%dae@samsung.com' \
    --to=inki.dae@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.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).