mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Jens Wiklander <jens.wiklander@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
	op-tee@lists.trustedfirmware.org,
	linux-arm-kernel@lists.infradead.org,
	Olivier Masse <olivier.masse@nxp.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	Yong Wu <yong.wu@mediatek.com>,
	Sumit Semwal <sumit.semwal@linaro.org>,
	Benjamin Gaignard <benjamin.gaignard@collabora.com>,
	Brian Starkey <Brian.Starkey@arm.com>,
	John Stultz <jstultz@google.com>,
	"T . J . Mercier" <tjmercier@google.com>,
	Sumit Garg <sumit.garg@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	azarrabi@qti.qualcomm.com, Simona Vetter <simona.vetter@ffwll.ch>,
	Daniel Stone <daniel@fooishbar.org>,
	Rouven Czerwinski <rouven.czerwinski@linaro.org>
Subject: Re: [PATCH v9 2/9] dma-buf: dma-heap: export declared functions
Date: Thu, 22 May 2025 13:52:14 +0200	[thread overview]
Message-ID: <1a65f370-2df2-4169-85f9-c45e7c537447@amd.com> (raw)
In-Reply-To: <CAHUa44Ec0+GPoDkcEG+Vg9_TY1NC=nh3yr0F=ezHMbaeX_A0Bg@mail.gmail.com>

On 5/22/25 08:56, Jens Wiklander wrote:
> On Wed, May 21, 2025 at 9:13 AM Christian König
> <christian.koenig@amd.com> wrote:
>>
>> On 5/20/25 17:16, Jens Wiklander wrote:
>>> Export the dma-buf heap functions declared in <linux/dma-heap.h>.
>>
>> That is what this patch does and that should be obvious by looking at it. You need to explain why you do this.
>>
>> Looking at the rest of the series it's most likely ok, but this commit message should really be improved.
> 
> I'm considering something like this for the next version:
> Export the dma-buf heap functions declared in <linux/dma-heap.h> to allow
> them to be used by kernel modules. This will enable drivers like the OP-TEE
> driver, to utilize these interfaces for registering and managing their
> specific DMA heaps.

Works for me, but it doesn't needs to be so detailed.

Something like this here would be optimal I think:

Export the dma-buf heap functions to allow them to be used by the OP-TEE driver.
The OP-TEE driver wants to register and manage specific secure DMA heaps with it.

Regards,
Christian.

> 
> Thanks,
> Jens
> 
>>
>> Regards,
>> Christian.
>>
>>>
>>> Signed-off-by: Jens Wiklander <jens.wiklander@linaro.org>
>>> ---
>>>  drivers/dma-buf/dma-heap.c | 3 +++
>>>  1 file changed, 3 insertions(+)
>>>
>>> diff --git a/drivers/dma-buf/dma-heap.c b/drivers/dma-buf/dma-heap.c
>>> index 3cbe87d4a464..cdddf0e24dce 100644
>>> --- a/drivers/dma-buf/dma-heap.c
>>> +++ b/drivers/dma-buf/dma-heap.c
>>> @@ -202,6 +202,7 @@ void *dma_heap_get_drvdata(struct dma_heap *heap)
>>>  {
>>>       return heap->priv;
>>>  }
>>> +EXPORT_SYMBOL(dma_heap_get_drvdata);
>>>
>>>  /**
>>>   * dma_heap_get_name - get heap name
>>> @@ -214,6 +215,7 @@ const char *dma_heap_get_name(struct dma_heap *heap)
>>>  {
>>>       return heap->name;
>>>  }
>>> +EXPORT_SYMBOL(dma_heap_get_name);
>>>
>>>  /**
>>>   * dma_heap_add - adds a heap to dmabuf heaps
>>> @@ -303,6 +305,7 @@ struct dma_heap *dma_heap_add(const struct dma_heap_export_info *exp_info)
>>>       kfree(heap);
>>>       return err_ret;
>>>  }
>>> +EXPORT_SYMBOL(dma_heap_add);
>>>
>>>  static char *dma_heap_devnode(const struct device *dev, umode_t *mode)
>>>  {
>>


  reply	other threads:[~2025-05-22 11:52 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-20 15:16 [PATCH v9 0/9] TEE subsystem for protected dma-buf allocations Jens Wiklander
2025-05-20 15:16 ` [PATCH v9 1/9] optee: sync secure world ABI headers Jens Wiklander
2025-05-23  9:00   ` Sumit Garg
2025-05-20 15:16 ` [PATCH v9 2/9] dma-buf: dma-heap: export declared functions Jens Wiklander
2025-05-21  7:13   ` Christian König
2025-05-22  6:56     ` Jens Wiklander
2025-05-22 11:52       ` Christian König [this message]
2025-05-22 12:36         ` Jens Wiklander
2025-05-20 15:16 ` [PATCH v9 3/9] tee: implement protected DMA-heap Jens Wiklander
2025-05-23 13:03   ` Sumit Garg
2025-05-26  7:11     ` Jens Wiklander
2025-05-30  2:13   ` Amirreza Zarrabi
2025-06-02 16:00     ` Jens Wiklander
2025-05-20 15:16 ` [PATCH v9 4/9] tee: refactor params_from_user() Jens Wiklander
2025-05-20 15:16 ` [PATCH v9 5/9] tee: new ioctl to a register tee_shm from a dmabuf file descriptor Jens Wiklander
2025-05-23 13:31   ` Sumit Garg
2025-05-26  8:34     ` Jens Wiklander
2025-05-20 15:16 ` [PATCH v9 6/9] tee: add tee_shm_alloc_dma_mem() Jens Wiklander
2025-05-22 16:49   ` kernel test robot
2025-05-26  7:22   ` Sumit Garg
2025-05-26  9:21     ` Jens Wiklander
2025-05-26  9:33       ` Sumit Garg
2025-05-27 14:21         ` Jens Wiklander
2025-05-20 15:16 ` [PATCH v9 7/9] optee: support protected memory allocation Jens Wiklander
2025-05-26  7:33   ` Sumit Garg
2025-05-27 14:32     ` Jens Wiklander
2025-05-20 15:16 ` [PATCH v9 8/9] optee: FF-A: dynamic " Jens Wiklander
2025-05-26  8:09   ` Sumit Garg
2025-05-27 15:07     ` Jens Wiklander
2025-05-20 15:16 ` [PATCH v9 9/9] optee: smc abi: " Jens Wiklander
2025-05-26  8:13   ` Sumit Garg
2025-05-27 14:43     ` Jens Wiklander

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=1a65f370-2df2-4169-85f9-c45e7c537447@amd.com \
    --to=christian.koenig@amd.com \
    --cc=Brian.Starkey@arm.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=azarrabi@qti.qualcomm.com \
    --cc=benjamin.gaignard@collabora.com \
    --cc=daniel@fooishbar.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jens.wiklander@linaro.org \
    --cc=jstultz@google.com \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=olivier.masse@nxp.com \
    --cc=op-tee@lists.trustedfirmware.org \
    --cc=rouven.czerwinski@linaro.org \
    --cc=simona.vetter@ffwll.ch \
    --cc=sumit.garg@kernel.org \
    --cc=sumit.semwal@linaro.org \
    --cc=thierry.reding@gmail.com \
    --cc=tjmercier@google.com \
    --cc=yong.wu@mediatek.com \
    /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®