From: Rob Herring <robh@kernel.org>
To: Florent Tomasin <florent.tomasin@arm.com>
Cc: "Vinod Koul" <vkoul@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Boris Brezillon" <boris.brezillon@collabora.com>,
"Steven Price" <steven.price@arm.com>,
"Liviu Dudau" <liviu.dudau@arm.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"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>,
"Christian König" <christian.koenig@amd.com>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Yong Wu" <yong.wu@mediatek.com>,
dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-media@vger.kernel.org, linaro-mm-sig@lists.linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, nd@arm.com,
"Akash Goel" <akash.goel@arm.com>
Subject: Re: [RFC PATCH 1/5] dt-bindings: dma: Add CMA Heap bindings
Date: Thu, 30 Jan 2025 17:20:04 -0600 [thread overview]
Message-ID: <20250130232004.GA1818629-robh@kernel.org> (raw)
In-Reply-To: <771534be8dfa2a3bdc3876502752f518224b9298.1738228114.git.florent.tomasin@arm.com>
On Thu, Jan 30, 2025 at 01:08:57PM +0000, Florent Tomasin wrote:
> Introduce a CMA Heap dt-binding allowing custom
> CMA heap registrations.
>
> * Note to the reviewers:
> The patch was used for the development of the protected mode
> feature in Panthor CSF kernel driver and is not initially thought
> to land in the Linux kernel. It is mostly relevant if someone
> wants to reproduce the environment of testing. Please, raise
> interest if you think the patch has value in the Linux kernel.
Why would panthor need CMA, it has an MMU.
In any case, I agree with Maxime that this is redundant.
Rob
next prev parent reply other threads:[~2025-01-30 23:21 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 13:08 [RFC PATCH 0/5] drm/panthor: Protected mode support for Mali CSF GPUs Florent Tomasin
2025-01-30 13:08 ` [RFC PATCH 1/5] dt-bindings: dma: Add CMA Heap bindings Florent Tomasin
2025-01-30 13:28 ` Maxime Ripard
2025-02-03 13:36 ` Florent Tomasin
2025-02-04 18:12 ` Nicolas Dufresne
2025-02-12 9:49 ` Florent Tomasin
2025-02-12 10:01 ` Maxime Ripard
2025-02-12 10:29 ` Florent Tomasin
2025-02-12 10:49 ` Maxime Ripard
2025-02-12 11:02 ` Florent Tomasin
2025-02-12 10:37 ` Boris Brezillon
2025-01-30 23:20 ` Rob Herring [this message]
2025-02-03 16:18 ` Florent Tomasin
2025-01-30 13:08 ` [RFC PATCH 2/5] cma-heap: Allow registration of custom cma heaps Florent Tomasin
2025-01-30 13:34 ` Maxime Ripard
2025-02-03 13:52 ` Florent Tomasin
2025-01-30 13:08 ` [RFC PATCH 3/5] dt-bindings: gpu: Add protected heap name to Mali Valhall CSF binding Florent Tomasin
2025-01-30 13:25 ` Krzysztof Kozlowski
2025-02-03 15:31 ` Florent Tomasin
2025-02-05 9:13 ` Krzysztof Kozlowski
2025-02-06 21:21 ` Nicolas Dufresne
2025-02-09 11:56 ` Krzysztof Kozlowski
2025-02-12 9:25 ` Florent Tomasin
2025-01-30 13:09 ` [RFC PATCH 4/5] drm/panthor: Add support for protected memory allocation in panthor Florent Tomasin
2025-02-11 11:04 ` Boris Brezillon
2025-02-11 11:20 ` Boris Brezillon
2025-03-12 20:05 ` Adrian Larumbe
2025-01-30 13:09 ` [RFC PATCH 5/5] drm/panthor: Add support for entering and exiting protected mode Florent Tomasin
2025-02-10 14:01 ` Boris Brezillon
2025-01-30 13:46 ` [RFC PATCH 0/5] drm/panthor: Protected mode support for Mali CSF GPUs Maxime Ripard
2025-01-30 15:59 ` Nicolas Dufresne
2025-01-30 16:38 ` Maxime Ripard
2025-01-30 17:47 ` Nicolas Dufresne
2025-02-03 16:43 ` Florent Tomasin
2025-02-04 18:22 ` Nicolas Dufresne
2025-02-05 14:53 ` Maxime Ripard
2025-02-05 18:07 ` Nicolas Dufresne
2025-02-05 14:52 ` Maxime Ripard
2025-02-05 18:14 ` Nicolas Dufresne
2025-02-07 15:02 ` Boris Brezillon
2025-02-07 16:32 ` Nicolas Dufresne
2025-02-07 16:42 ` Boris Brezillon
2025-02-11 13:46 ` Maxime Ripard
2025-02-11 14:32 ` Boris Brezillon
2025-02-20 13:32 ` Maxime Ripard
2025-02-24 11:36 ` Boris Brezillon
2025-01-30 16:15 ` Simona Vetter
2025-02-03 9:25 ` Boris Brezillon
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=20250130232004.GA1818629-robh@kernel.org \
--to=robh@kernel.org \
--cc=Brian.Starkey@arm.com \
--cc=airlied@gmail.com \
--cc=akash.goel@arm.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=benjamin.gaignard@collabora.com \
--cc=boris.brezillon@collabora.com \
--cc=christian.koenig@amd.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=florent.tomasin@arm.com \
--cc=jstultz@google.com \
--cc=krzk+dt@kernel.org \
--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=linux-mediatek@lists.infradead.org \
--cc=liviu.dudau@arm.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthias.bgg@gmail.com \
--cc=mripard@kernel.org \
--cc=nd@arm.com \
--cc=simona@ffwll.ch \
--cc=steven.price@arm.com \
--cc=sumit.semwal@linaro.org \
--cc=tjmercier@google.com \
--cc=tzimmermann@suse.de \
--cc=vkoul@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).