From: Benjamin Gaignard <benjamin.gaignard@linaro.org>
To: Brian Starkey <Brian.Starkey@arm.com>
Cc: John Stultz <john.stultz@linaro.org>,
lkml <linux-kernel@vger.kernel.org>,
Laura Abbott <labbott@redhat.com>,
Sumit Semwal <sumit.semwal@linaro.org>,
Liam Mark <lmark@codeaurora.org>,
Pratik Patel <pratikp@codeaurora.org>,
Vincent Donnefort <Vincent.Donnefort@arm.com>,
Sudipto Paul <Sudipto.Paul@arm.com>,
"Andrew F . Davis" <afd@ti.com>,
Christoph Hellwig <hch@infradead.org>,
Chenbo Feng <fengc@google.com>,
Alistair Strachan <astrachan@google.com>,
Hridya Valsaraju <hridya@google.com>,
Hillf Danton <hdanton@sina.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>, nd <nd@arm.com>
Subject: Re: [PATCH v12 4/5] dma-buf: heaps: Add CMA heap to dmabuf heaps
Date: Fri, 18 Oct 2019 14:03:53 +0200 [thread overview]
Message-ID: <CA+M3ks6KqqXCfqA6VDKnQOsvFLQfaGrUnA+eesnyzMRniFB00A@mail.gmail.com> (raw)
In-Reply-To: <20191018112124.grjgqrn3ckuc7n4v@DESKTOP-E1NTVVP.localdomain>
Le ven. 18 oct. 2019 à 13:21, Brian Starkey <Brian.Starkey@arm.com> a écrit :
>
> On Fri, Oct 18, 2019 at 05:23:22AM +0000, John Stultz wrote:
> > This adds a CMA heap, which allows userspace to allocate
> > a dma-buf of contiguous memory out of a CMA region.
> >
> > This code is an evolution of the Android ION implementation, so
> > thanks to its original author and maintainters:
> > Benjamin Gaignard, Laura Abbott, and others!
> >
> > NOTE: This patch only adds the default CMA heap. We will enable
> > selectively adding other CMA memory regions to the dmabuf heaps
> > interface with a later patch (which requires a dt binding)
Maybe we can use "no-map" DT property to trigger that. If set do not expose the
cma heap.
Benjamin
>
> That'll teach me for reading my email in FIFO order.
>
> This approach makes sense to me.
>
> -Brian
>
next prev parent reply other threads:[~2019-10-18 12:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 5:23 [PATCH v12 0/5] DMA-BUF Heaps (destaging ION) John Stultz
2019-10-18 5:23 ` [PATCH v12 1/5] dma-buf: Add dma-buf heaps framework John Stultz
2019-10-18 11:18 ` Brian Starkey
2019-10-18 18:26 ` John Stultz
2019-10-21 9:35 ` Brian Starkey
2019-10-21 18:32 ` John Stultz
2019-10-18 5:23 ` [PATCH v12 2/5] dma-buf: heaps: Add heap helpers John Stultz
2019-10-18 5:23 ` [PATCH v12 3/5] dma-buf: heaps: Add system heap to dmabuf heaps John Stultz
2019-10-18 5:23 ` [PATCH v12 4/5] dma-buf: heaps: Add CMA " John Stultz
2019-10-18 11:21 ` Brian Starkey
2019-10-18 12:03 ` Benjamin Gaignard [this message]
2019-10-18 13:54 ` Andrew F. Davis
2019-10-18 18:29 ` John Stultz
2019-10-18 5:23 ` [PATCH v12 5/5] kselftests: Add dma-heap test John Stultz
2019-10-18 6:21 ` [PATCH v12 0/5] DMA-BUF Heaps (destaging ION) Sumit Semwal
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=CA+M3ks6KqqXCfqA6VDKnQOsvFLQfaGrUnA+eesnyzMRniFB00A@mail.gmail.com \
--to=benjamin.gaignard@linaro.org \
--cc=Brian.Starkey@arm.com \
--cc=Sudipto.Paul@arm.com \
--cc=Vincent.Donnefort@arm.com \
--cc=afd@ti.com \
--cc=astrachan@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=fengc@google.com \
--cc=hch@infradead.org \
--cc=hdanton@sina.com \
--cc=hridya@google.com \
--cc=john.stultz@linaro.org \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lmark@codeaurora.org \
--cc=nd@arm.com \
--cc=pratikp@codeaurora.org \
--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).