From: Neil Armstrong <narmstrong@baylibre.com>
To: John Stultz <john.stultz@linaro.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Hillf Danton <hdanton@sina.com>,
Sudipto Paul <Sudipto.Paul@arm.com>,
Vincent Donnefort <Vincent.Donnefort@arm.com>,
Chenbo Feng <fengc@google.com>,
Alistair Strachan <astrachan@google.com>,
Liam Mark <lmark@codeaurora.org>,
Christoph Hellwig <hch@infradead.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
"Andrew F . Davis" <afd@ti.com>,
Hridya Valsaraju <hridya@google.com>,
Pratik Patel <pratikp@codeaurora.org>
Subject: Re: [PATCH v13 0/5] DMA-BUF Heaps (destaging ION)
Date: Wed, 23 Oct 2019 09:32:30 +0200 [thread overview]
Message-ID: <b6319fec-8536-a7d1-ee26-cd47438218b0@baylibre.com> (raw)
In-Reply-To: <CALAqxLVjp-qNyy8wjG+fJYQqafK5Fsf8rpb3bNe3_p0X9VLjRg@mail.gmail.com>
On 22/10/2019 17:56, John Stultz wrote:
> On Tue, Oct 22, 2019 at 1:21 AM Neil Armstrong <narmstrong@baylibre.com> wrote:
>>
>> Hi John,
>>
>> On 21/10/2019 21:03, John Stultz wrote:
>>> Lucky number 13! :)
>>>
>>> Last week in v12 I had re-added some symbol exports to support
>>> later patches I have pending to enable loading heaps from
>>> modules. He reminded me that back around v3 (its been awhile!) I
>>> had removed those exports due to concerns about the fact that we
>>> don't support module removal.
>>>
>>> So I'm respinning the patches, removing the exports again. I'll
>>> submit a patch to re-add them in a later series enabling moduels
>>> which can be reviewed indepently.
>>>
>>> With that done, lets get on to the boilerplate!
>>>
>>> The patchset implements per-heap devices which can be opened
>>> directly and then an ioctl is used to allocate a dmabuf from the
>>> heap.
>>>
>>> The interface is similar, but much simpler then IONs, only
>>> providing an ALLOC ioctl.
>>>
>>> Also, I've provided relatively simple system and cma heaps.
>>>
>>> I've booted and tested these patches with AOSP on the HiKey960
>>> using the kernel tree here:
>>> https://git.linaro.org/people/john.stultz/android-dev.git/log/?h=dev/dma-buf-heap
>>
>> Do you have a 4.19 tree with the changes ? I tried but the xarray idr replacement
>> is missing... so I can't test with our android-amlogic-bmeson-4.19 tree.
>>
>> If you can provide, I'll be happy to test the serie and the gralloc changes.
>
> Unfortunately I don't have a 4.19 version of dmabuf heaps (all the
> work has been done this year, post 4.19). I'm planning to backport to
> 5.4 for AOSP, but I've not really thought about 4.19. Most likely I
> won't have time to look at it until after the changes are upstream and
> the 5.4 backport is done.
>
> Is the bmeson tree likely to only stay at 4.19? Or will it move forward?
No idea, I don't have any details on the future plans.
Since we did an upstream-first support, 90% will be available on the future android-5.4 tree anyway.
Neil
>
> thanks
> -john
>
next prev parent reply other threads:[~2019-10-23 7:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 19:03 John Stultz
2019-10-21 19:03 ` [PATCH v13 1/5] dma-buf: Add dma-buf heaps framework John Stultz
2019-10-21 19:03 ` [PATCH v13 2/5] dma-buf: heaps: Add heap helpers John Stultz
2019-10-21 19:03 ` [PATCH v13 3/5] dma-buf: heaps: Add system heap to dmabuf heaps John Stultz
2019-10-21 19:03 ` [PATCH v13 4/5] dma-buf: heaps: Add CMA " John Stultz
2019-10-21 19:03 ` [PATCH v13 5/5] kselftests: Add dma-heap test John Stultz
2019-10-21 19:04 ` [PATCH v13 0/5] DMA-BUF Heaps (destaging ION) John Stultz
2019-10-22 8:21 ` Neil Armstrong
2019-10-22 15:56 ` John Stultz
2019-10-23 7:32 ` Neil Armstrong [this message]
2019-10-22 16:01 ` Andrew F. Davis
2019-10-25 5:56 ` Sumit Semwal
2019-10-25 11:34 ` 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=b6319fec-8536-a7d1-ee26-cd47438218b0@baylibre.com \
--to=narmstrong@baylibre.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=linux-kernel@vger.kernel.org \
--cc=lmark@codeaurora.org \
--cc=pratikp@codeaurora.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
all inboxes | Powered by JetHome®