From: Laura Abbott <labbott@redhat.com>
To: Moritz Fischer <moritz.fischer@ettus.com>, arnd@arndb.de
Cc: gregkh@linuxfoundation.org, arve@android.com,
riandrews@android.com, gioh.kim@lge.com, sumit.semwal@linaro.org,
dan.carpenter@oracle.com, sriram@marirs.net.in,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [RFC 0/2] staging: ion: of_ion_device_get
Date: Tue, 22 Mar 2016 15:51:39 -0700 [thread overview]
Message-ID: <56F1CC7B.7040909@redhat.com> (raw)
In-Reply-To: <1458686031-31031-1-git-send-email-moritz.fischer@ettus.com>
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 ion_device in each of them.
> I couldn't find a way to get to that via devicetree, though. I'll admit that hacking
> up miscdevice is quite hacky, maybe I should add a foo_get_ion_device() to my
> heap implementing platform device?
> If someone can explain me how to correctly do that with what we currently have,
> even better.
>
> Cheers,
>
> Moritz
>
> Moritz Fischer (2):
> misc: Add of_get_misc get a reference from devicetree
> staging: android: ion: Add of_ion_device_get function
>
> drivers/char/misc.c | 38 ++++++++++++++++++++++++++++++++++++++
> drivers/staging/android/ion/ion.c | 10 ++++++++++
> include/linux/miscdevice.h | 3 +++
> 3 files changed, 51 insertions(+)
>
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.
Can you elaborate more on your sharing and allocation flow? This might suggest
another idea.
Thanks,
Laura
next prev parent reply other threads:[~2016-03-22 22:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 22:33 [RFC 0/2] staging: ion: of_ion_device_get Moritz Fischer
2016-03-22 22:33 ` [RFC 1/2] misc: Add of_get_misc get a reference from devicetree Moritz Fischer
2016-03-22 22:54 ` Moritz Fischer
2016-03-22 22:33 ` [RFC 2/2] staging: android: ion: Add of_ion_device_get function Moritz Fischer
2016-03-22 22:50 ` Moritz Fischer
2016-03-23 4:55 ` Dan Carpenter
2016-03-22 22:51 ` Laura Abbott [this message]
2016-03-22 23:08 ` [RFC 0/2] staging: ion: of_ion_device_get Moritz Fischer
2016-03-22 23:20 ` Laura Abbott
2016-03-22 23:38 ` Moritz Fischer
2016-03-22 23:40 ` Moritz Fischer
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=56F1CC7B.7040909@redhat.com \
--to=labbott@redhat.com \
--cc=arnd@arndb.de \
--cc=arve@android.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gioh.kim@lge.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=moritz.fischer@ettus.com \
--cc=riandrews@android.com \
--cc=sriram@marirs.net.in \
--cc=sumit.semwal@linaro.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.