Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1363124
| From | Laura Abbott <labbott@redhat.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC 0/2] staging: ion: of_ion_device_get |
| Date | 2016-03-23 00:30 +0100 |
| Message-ID | <rfDUl-37U-3@gated-at.bofh.it> (permalink) |
| References | <rfD7Y-2AF-11@gated-at.bofh.it> <rfDrk-2Hw-3@gated-at.bofh.it> <rfDB0-310-39@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 03/22/2016 04:08 PM, Moritz Fischer wrote: > Hi Laura, > > On Tue, Mar 22, 2016 at 3:51 PM, Laura Abbott <labbott@redhat.com> wrote: > >> In the past what drivers have done is a foo_ion_client_create which has the >> reference >> to the ion_device created from ion_device_create. Drivers then call the >> foo_ion_client_create function. > > Oh, so you mean you add a function to create a client to the platform > device implementing > the heap and the export this function? > > heap implements: > > foo_create_client(); > > driver calls: > > foo_create_client() ? > Yes, exactly >> Can you elaborate more on your sharing and allocation flow? This might >> suggest >> another idea. > > Well I'll have a bunch of DMA streams to / from an FPGA that contains > DMA engines & accelerators. To that end > my userland software would allocate say 64 buffers, hand them over to > driver A to queue/deque them. > > In future I might want to share these buffers between streams and with > other peripherals on the same bus, > which is why I looked at ION. > If allocation is coming from userspace and drivers are only importing you should be using the dma_buf APIs instead of Ion APIs directly. Ion is a dma_buf exporter and dma_buf APIs are the preferred API. > Thanks, > > Moritz > Thanks, Laura
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[RFC 0/2] staging: ion: of_ion_device_get Moritz Fischer <moritz.fischer@ettus.com> - 2016-03-22 23:40 +0100
[RFC 2/2] staging: android: ion: Add of_ion_device_get function Moritz Fischer <moritz.fischer@ettus.com> - 2016-03-22 23:40 +0100
Re: [RFC 2/2] staging: android: ion: Add of_ion_device_get function Moritz Fischer <moritz.fischer@ettus.com> - 2016-03-23 00:00 +0100
Re: [RFC 2/2] staging: android: ion: Add of_ion_device_get function Dan Carpenter <dan.carpenter@oracle.com> - 2016-03-23 06:00 +0100
Re: [RFC 0/2] staging: ion: of_ion_device_get Laura Abbott <labbott@redhat.com> - 2016-03-23 00:00 +0100
Re: [RFC 0/2] staging: ion: of_ion_device_get Moritz Fischer <moritz.fischer@ettus.com> - 2016-03-23 00:10 +0100
Re: [RFC 0/2] staging: ion: of_ion_device_get Laura Abbott <labbott@redhat.com> - 2016-03-23 00:30 +0100
Re: [RFC 0/2] staging: ion: of_ion_device_get Moritz Fischer <moritz.fischer@ettus.com> - 2016-03-23 00:40 +0100
Re: [RFC 0/2] staging: ion: of_ion_device_get Moritz Fischer <moritz.fischer@ettus.com> - 2016-03-23 00:50 +0100
csiph-web