mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jordan Crouse <jcrouse@codeaurora.org>
To: Benjamin Gaignard <benjamin.gaignard@linaro.org>
Cc: labbott@redhat.com, sumit.semwal@linaro.org,
	gregkh@linuxfoundation.org, arve@android.com,
	riandrews@android.com, broonie@kernel.org,
	dan.carpenter@oracle.com, devel@driverdev.osuosl.org,
	linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v6 2/2] staging: ion: create one device entry per heap
Date: Tue, 24 Oct 2017 10:14:44 -0600	[thread overview]
Message-ID: <20171024161444.GA14939@jcrouse-lnx.qualcomm.com> (raw)
In-Reply-To: <1508774137-13835-3-git-send-email-benjamin.gaignard@linaro.org>

On Mon, Oct 23, 2017 at 05:55:37PM +0200, Benjamin Gaignard wrote:
> Instead a getting only one common device "/dev/ion" for
> all the heaps this patch allow to create one device
> entry ("/dev/ionX") per heap.
> Getting an entry per heap could allow to set security rules
> per heap and global ones for all heaps.
> 
> Allocation requests will be only allowed if the mask_id
> match with device minor.
> Query request could be done on any of the devices.
> 
> Ion devices are parentless so it is need to add platform_bus as
> parent and platform_bus_type as bus to be put in /sys/device/paltform.

nit: paltform -> platform.

Jordan

-- 
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2017-10-24 16:14 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-23 15:55 [PATCH v6 0/2] staging: ion: get one device " Benjamin Gaignard
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 [this message]
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
2017-11-06 15:59 ` [PATCH v6 2/2] staging: ion: create one device entry " Benjamin Gaignard
2017-11-09 21:17   ` Laura Abbott
2017-11-27 10:46     ` Benjamin Gaignard
2017-11-27 11:43       ` Greg Kroah-Hartman
2017-11-27 16:12         ` Daniel Vetter
2017-11-27 16:30           ` Mark Brown
2017-11-28 13:32   ` Greg KH
2017-11-28 16:26     ` Mark Brown
2017-11-28 17:08       ` Greg KH
2017-11-28 17:12         ` Mark Brown
2017-11-28 17:28           ` Greg KH
2017-11-28 17:37             ` Mark Brown
2017-11-28 18:00               ` Greg KH
2017-11-29 14:00     ` Benjamin Gaignard
2017-12-02 15:53       ` Greg KH
2017-12-05 23:01         ` Laura Abbott
2017-12-06  6:28           ` Greg KH

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=20171024161444.GA14939@jcrouse-lnx.qualcomm.com \
    --to=jcrouse@codeaurora.org \
    --cc=arve@android.com \
    --cc=benjamin.gaignard@linaro.org \
    --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

Powered by JetHome