From: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
To: John Stultz <john.stultz@linaro.org>
Cc: Sumit Semwal <sumit.semwal@linaro.org>,
"Andrew F . Davis" <afd@ti.com>,
Benjamin Gaignard <benjamin.gaignard@linaro.org>,
Liam Mark <lmark@codeaurora.org>,
Laura Abbott <labbott@redhat.com>,
Brian Starkey <Brian.Starkey@arm.com>,
Christian Koenig <christian.koenig@amd.com>,
linux-media@vger.kernel.org,
dri-devel <dri-devel@lists.freedesktop.org>,
"moderated list:DMA BUFFER SHARING FRAMEWORK"
<linaro-mm-sig@lists.linaro.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dma-buf: heaps: Introduce dma_heap_add_cma() for non-default CMA heap
Date: Fri, 21 Aug 2020 18:14:01 +0900 [thread overview]
Message-ID: <377e6e65-0b44-ecd0-cfc5-6fbc82be35d5@socionext.com> (raw)
In-Reply-To: <CALAqxLVzUnc5CH_pA7h3ygXFPRz05KtNZx+_M3eAXXrm7hhGBQ@mail.gmail.com>
On 2020/08/01 4:38, John Stultz wrote:
> On Fri, Jul 31, 2020 at 2:32 AM Kunihiko Hayashi
> <hayashi.kunihiko@socionext.com> wrote:
>> On 2020/07/29 4:17, John Stultz wrote:
>>> Do you have a upstream driver that you plan to make use this new call?
>>
>> Unfortunately I don't have an upstream driver using this call.
>>
>> This call is called from dma-buf heaps "importer" or "customer",
>> and I only made an example (do nothing) importer driver
>> to test the call.
>>
>>> We want to have in-tree users of code added.
>>
>> I think this is a generic way to use non-default CMA heaps, however,
>> we need in-tree "importer" drivers to want to use non-default CMA heaps.
>> I don't find it from now.
>>
>
> Yea, I and again, I do agree this is functionality that will be
> needed. But we'll need to wait for a user (camera driver, etc which
> would utilize the reserved cma region) before we can merge it
> upstream. :( Do let me know if you have an out of tree driver that
> would make use of it, and we can see what can be done to help upstream
> things.
Sorry for late.
Before I prepare or find a user driver as "importer",
I think something is different in this patch.
This patch makes it possible to treat non-default CMA connected to
"importer" device with memory-region as dma-buf heaps.
However, the allocated memory from this dma-buf heaps can be used
for "any" devices, and the "importer" can treat memories from other
dma-buf heaps.
So, the "importer" and the non-default CMA aren't directly related,
and I think an "exporter" for the non-default CMA should be enabled.
In paticular, the kernel initializer (as an "exporter") calls
dma_heap_add_cma() for all CMAs defined in Devicetree, and
the device files associated with each CMA appear under "/dev/dma_heap/".
For example:
/dev/dma_heap/linux,cma@10000000
/dev/dma_heap/linux,cma@11000000
/dev/dma_heap/linux,cma@12000000
...
All of these device files can be fairly allocated to any "importer" device.
Actually I think that the kernel should executes dma_heap_add_cma()
for ALL defined reserved-memory nodes.
If this idea hasn't been discussed yet and this is reasonable,
I'll prepare RFC patches.
Thank you,
---
Best Regards
Kunihiko Hayashi
next prev parent reply other threads:[~2020-08-21 9:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 1:10 [PATCH] dma-buf: heaps: Introduce dma_heap_add_cma() for non-default CMA heap Kunihiko Hayashi
2020-07-28 19:17 ` John Stultz
2020-07-31 9:32 ` Kunihiko Hayashi
2020-07-31 19:38 ` John Stultz
2020-08-21 9:14 ` Kunihiko Hayashi [this message]
2020-08-21 18:32 ` John Stultz
2020-08-25 11:09 ` Kunihiko Hayashi
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=377e6e65-0b44-ecd0-cfc5-6fbc82be35d5@socionext.com \
--to=hayashi.kunihiko@socionext.com \
--cc=Brian.Starkey@arm.com \
--cc=afd@ti.com \
--cc=benjamin.gaignard@linaro.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=john.stultz@linaro.org \
--cc=labbott@redhat.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lmark@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).