[PATCH v13 0/5] DMA-BUF Heaps (destaging ION)
narmstrong at baylibre.com
Wed Oct 23 07:32:30 UTC 2019
On 22/10/2019 17:56, John Stultz wrote:
> On Tue, Oct 22, 2019 at 1:21 AM Neil Armstrong <narmstrong at 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
>>> 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:
>> 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.
More information about the dri-devel