Re: [RFC 0/2] staging: ion: of_ion_device_get

On Tue, Mar 22, 2016 at 4:20 PM, Laura Abbott wrote: > 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. Ok, thanks.

Re: [RFC 0/2] staging: ion: of_ion_device_get

On Tue, Mar 22, 2016 at 4:20 PM, Laura Abbott wrote: > 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. Ok, thanks. Sounds reasonable.

Re: [RFC 0/2] staging: ion: of_ion_device_get

On Tue, Mar 22, 2016 at 4:20 PM, Laura Abbott wrote: > On 03/22/2016 04:08 PM, Moritz Fischer wrote: >> >> Hi Laura, >> >> On Tue, Mar 22, 2016 at 3:51 PM, Laura Abbott wrote: >> >>> In the past what drivers have done is a foo_ion_client_create which has

Re: [RFC 0/2] staging: ion: of_ion_device_get

On Tue, Mar 22, 2016 at 4:20 PM, Laura Abbott wrote: > On 03/22/2016 04:08 PM, Moritz Fischer wrote: >> >> Hi Laura, >> >> On Tue, Mar 22, 2016 at 3:51 PM, Laura Abbott wrote: >> >>> In the past what drivers have done is a foo_ion_client_create which has >>> the >>> reference >>> to the

Re: [RFC 0/2] staging: ion: of_ion_device_get

On 03/22/2016 04:08 PM, Moritz Fischer wrote: Hi Laura, On Tue, Mar 22, 2016 at 3:51 PM, Laura Abbott 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

Re: [RFC 0/2] staging: ion: of_ion_device_get

On 03/22/2016 04:08 PM, Moritz Fischer wrote: Hi Laura, On Tue, Mar 22, 2016 at 3:51 PM, Laura Abbott 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

Re: [RFC 0/2] staging: ion: of_ion_device_get

Hi Laura, On Tue, Mar 22, 2016 at 3:51 PM, Laura Abbott 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

Re: [RFC 0/2] staging: ion: of_ion_device_get

Hi Laura, On Tue, Mar 22, 2016 at 3:51 PM, Laura Abbott 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

Re: [RFC 0/2] staging: ion: of_ion_device_get

On 03/22/2016 03:33 PM, Moritz Fischer wrote: Hi all, probably I'm doing this all wrong. I'm playing around with a bunch of accelerators and I need to share buffers between them. I have my heaps implemented as a platform device and from what I understand I'll need a reference to the struct

Re: [RFC 0/2] staging: ion: of_ion_device_get

On 03/22/2016 03:33 PM, Moritz Fischer wrote: Hi all, probably I'm doing this all wrong. I'm playing around with a bunch of accelerators and I need to share buffers between them. I have my heaps implemented as a platform device and from what I understand I'll need a reference to the struct

[RFC 0/2] staging: ion: of_ion_device_get

Hi all, probably I'm doing this all wrong. I'm playing around with a bunch of accelerators and I need to share buffers between them. I have my heaps implemented as a platform device and from what I understand I'll need a reference to the struct ion_device in each of them. I couldn't find a way

[RFC 0/2] staging: ion: of_ion_device_get

Hi all, probably I'm doing this all wrong. I'm playing around with a bunch of accelerators and I need to share buffers between them. I have my heaps implemented as a platform device and from what I understand I'll need a reference to the struct ion_device in each of them. I couldn't find a way