From: Benjamin Gaignard <benjamin.gaignard@linaro.org>
To: labbott@redhat.com, sumit.semwal@linaro.org,
gregkh@linuxfoundation.org, arve@android.com,
riandrews@android.com, broonie@kernel.org,
dan.carpenter@oracle.com
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-api@vger.kernel.org,
Benjamin Gaignard <benjamin.gaignard@linaro.org>
Subject: [PATCH v6 0/2] staging: ion: get one device per heap
Date: Mon, 23 Oct 2017 17:55:35 +0200 [thread overview]
Message-ID: <1508774137-13835-1-git-send-email-benjamin.gaignard@linaro.org> (raw)
version 6:
- add platform_bus and platform_bus_type when register Ion devices
to make them appear in /sys/devices/platform.
- re-order include files in aphabetic order.
version 5:
- create a configuration flag to keep legacy Ion misc device
version 4:
- add a configuration flag to switch between legacy Ion misc device
and one device per heap version.
This change has been suggested after Laura talks at XDC 2017.
version 3:
- change ion_device_add_heap prototype to return a possible error.
version 2:
- simplify ioctl check like propose by Dan
- make sure that we don't register more than ION_DEV_MAX heaps.
Until now all ion heaps are addressing using the same device "/dev/ion".
This way of working doesn't allow to give access rights (for example with
SElinux rules) per heap.
This series propose to have one device "/dev/ionX" per heap.
Query heaps informations will be possible on each device node but
allocation request will only be possible if heap_mask_id match with device minor number.
Using legacy Ion misc device is still by setting ION_LEGACY_DEVICE_API
configuration flag.
Benjamin Gaignard (2):
staging: ion: simplify ioctl args checking function
staging: ion: create one device entry per heap
drivers/staging/android/TODO | 1 -
drivers/staging/android/ion/Kconfig | 7 +++++
drivers/staging/android/ion/ion-ioctl.c | 29 +++++++++++++-----
drivers/staging/android/ion/ion.c | 53 ++++++++++++++++++++++++++-------
drivers/staging/android/ion/ion.h | 15 ++++++++--
5 files changed, 84 insertions(+), 21 deletions(-)
--
2.7.4
next reply other threads:[~2017-10-23 15:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 15:55 Benjamin Gaignard [this message]
2017-10-23 15:55 ` [PATCH v6 1/2] staging: ion: simplify ioctl args checking function Benjamin Gaignard
2017-10-23 15:55 ` [PATCH v6 2/2] staging: ion: create one device entry per heap Benjamin Gaignard
2017-10-24 16:14 ` Jordan Crouse
2017-10-31 19:03 ` Laura Abbott
2017-10-31 19:11 ` Mark Brown
2017-10-31 19:45 ` Laura Abbott
2017-11-02 10:44 ` Greg KH
2017-11-02 11:10 ` Mark Brown
2017-11-06 14:42 ` Benjamin Gaignard
2017-11-06 14:46 ` Greg KH
2017-11-06 15:59 [PATCH v6 0/2] staging: ion: get one device " Benjamin Gaignard
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=1508774137-13835-1-git-send-email-benjamin.gaignard@linaro.org \
--to=benjamin.gaignard@linaro.org \
--cc=arve@android.com \
--cc=broonie@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=labbott@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riandrews@android.com \
--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 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).