From: Jared Kangas <jkangas@redhat.com>
To: Sumit Semwal <sumit.semwal@linaro.org>
Cc: benjamin.gaignard@collabora.com, Brian.Starkey@arm.com,
jstultz@google.com, tjmercier@google.com,
christian.koenig@amd.com, mripard@kernel.org,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] dma-buf: heaps: Use constant name for CMA heap
Date: Wed, 23 Apr 2025 08:57:32 -0700 [thread overview]
Message-ID: <aAkN7BXIT7RR85PR@jkangas-thinkpadp1gen3.rmtuswa.csb> (raw)
In-Reply-To: <CAO_48GELW3ax5Q3h9=qpWBJJa0Uy3eJwFkEcbaz4ZT56Gq513A@mail.gmail.com>
Hi Sumit,
On Wed, Apr 23, 2025 at 08:53:20PM +0530, Sumit Semwal wrote:
> Hello Jared,
>
> On Wed, 23 Apr 2025 at 00:49, Jared Kangas <jkangas@redhat.com> wrote:
> >
> > Hi all,
> >
> > This patch series is based on a previous discussion around CMA heap
> > naming. [1] The heap's name depends on the device name, which is
> > generally "reserved", "linux,cma", or "default-pool", but could be any
> > arbitrary name given to the default CMA area in the devicetree. For a
> > consistent userspace interface, the series introduces a constant name
> > for the CMA heap, and for backwards compatibility, an additional Kconfig
> > that controls the creation of a legacy-named heap with the same CMA
> > backing.
> >
> > The ideas to handle backwards compatibility in [1] are to either use a
> > symlink or add a heap node with a duplicate minor. However, I assume
> > that we don't want to create symlinks in /dev from module initcalls, and
> > attempting to duplicate minors would cause device_create() to fail.
> > Because of these drawbacks, after brainstorming with Maxime Ripard, I
> > went with creating a new node in devtmpfs with its own minor. This
> > admittedly makes it a little unclear that the old and new nodes are
> > backed by the same heap when both are present. The only approach that I
> > think would provide total clarity on this in userspace is symlinking,
> > which seemed like a fairly involved solution for devtmpfs, but if I'm
> > wrong on this, please let me know.
>
> Thanks indeed for this patch; just one minor nit: the link referred to
> as [1] here seems to be missing. Could you please add it? This would
> make it easier to follow the chain of discussion in posterity.
My bad, I must have dropped the link while revising the cover letter.
Here's the dropped reference:
[1]: https://lore.kernel.org/all/f6412229-4606-41ad-8c05-7bbba2eb6e08@ti.com/
Thanks to you and John for looking this over,
Jared
> >
> > Changelog:
> > v2: Use tabs instead of spaces for large vertical alignment.
> >
> > Jared Kangas (2):
> > dma-buf: heaps: Parameterize heap name in __add_cma_heap()
> > dma-buf: heaps: Give default CMA heap a fixed name
> >
> > Documentation/userspace-api/dma-buf-heaps.rst | 11 ++++---
> > drivers/dma-buf/heaps/Kconfig | 10 +++++++
> > drivers/dma-buf/heaps/cma_heap.c | 30 ++++++++++++++-----
> > 3 files changed, 40 insertions(+), 11 deletions(-)
> >
> > --
> > 2.49.0
> >
>
> Best,
> Sumit
>
prev parent reply other threads:[~2025-04-23 16:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 19:19 Jared Kangas
2025-04-22 19:19 ` [PATCH v2 1/2] dma-buf: heaps: Parameterize heap name in __add_cma_heap() Jared Kangas
2025-04-22 22:22 ` John Stultz
2025-04-22 19:19 ` [PATCH v2 2/2] dma-buf: heaps: Give default CMA heap a fixed name Jared Kangas
2025-04-22 22:36 ` John Stultz
2025-04-24 8:33 ` Maxime Ripard
2025-04-24 16:11 ` Jared Kangas
2025-05-21 15:29 ` Maxime Ripard
2025-04-25 0:13 ` John Stultz
2025-04-25 6:58 ` Maxime Ripard
2025-04-25 19:39 ` John Stultz
2025-04-28 14:51 ` Maxime Ripard
2025-04-29 16:25 ` John Stultz
2025-05-06 13:33 ` Maxime Ripard
2025-04-23 15:23 ` [PATCH v2 0/2] dma-buf: heaps: Use constant name for CMA heap Sumit Semwal
2025-04-23 15:57 ` Jared Kangas [this message]
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=aAkN7BXIT7RR85PR@jkangas-thinkpadp1gen3.rmtuswa.csb \
--to=jkangas@redhat.com \
--cc=Brian.Starkey@arm.com \
--cc=benjamin.gaignard@collabora.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jstultz@google.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=tjmercier@google.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®