[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANDhNCpbX1718t2gH3LULL=RDxfxh+uCJNF4jJH0sbpLMK=oWA@mail.gmail.com>
Date: Tue, 22 Apr 2025 15:36:45 -0700
From: John Stultz <jstultz@...gle.com>
To: Jared Kangas <jkangas@...hat.com>
Cc: sumit.semwal@...aro.org, benjamin.gaignard@...labora.com,
Brian.Starkey@....com, tjmercier@...gle.com, christian.koenig@....com,
mripard@...nel.org, linux-media@...r.kernel.org,
dri-devel@...ts.freedesktop.org, linaro-mm-sig@...ts.linaro.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/2] dma-buf: heaps: Give default CMA heap a fixed name
On Tue, Apr 22, 2025 at 12:19 PM Jared Kangas <jkangas@...hat.com> wrote:
>
> The CMA heap's name in devtmpfs can vary depending on how the heap is
> defined. Its name defaults to "reserved", but if a CMA area is defined
> in the devicetree, the heap takes on the devicetree node's name, such as
> "default-pool" or "linux,cma". To simplify naming, just name it
> "default_cma", and keep a legacy node in place backed by the same
> underlying structure for backwards compatibility.
>
> Signed-off-by: Jared Kangas <jkangas@...hat.com>
Once again, thanks for working out how to improve the standard naming
while keeping compatibility.
I do still hope we can get to the point where other cma regions can be
registered as heaps with unique/purpose-specific names, but I can see
having a standard name for the default region is a nice improvement.
Acked-by: John Stultz <jstultz@...gle.com>
thanks
-john
Powered by blists - more mailing lists