From: "Rob Herring (Arm)" <robh@kernel.org>
To: Saravana Kannan <saravanak@google.com>,
Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Patrice Chotard <patrice.chotard@foss.st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-remoteproc@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: [PATCH 0/3] of: Common "memory-region" parsing
Date: Mon, 17 Mar 2025 18:24:20 -0500 [thread overview]
Message-ID: <20250317232426.952188-1-robh@kernel.org> (raw)
While there's a common function to parse "memory-region" properties for
DMA pool regions, there's not anything for driver private regions. As a
result, drivers have resorted to parsing "memory-region" properties
themselves repeating the same pattern over and over. To fix this, this
series adds 2 functions to handle those cases:
of_reserved_mem_region_to_resource() and of_reserved_mem_region_count().
I've converted the whole tree, but just including remoteproc here as
it has the most cases. I intend to apply the first 2 patches for 6.15
so the driver conversions can be applied for 6.16.
A git tree with all the drivers converted is here[1].
[1] git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git dt/memory-region
Rob Herring (Arm) (3):
of: reserved_mem: Add functions to parse "memory-region"
of: Simplify of_dma_set_restricted_buffer() to use
of_for_each_phandle()
remoteproc: Use of_reserved_mem_region_* functions for "memory-region"
drivers/of/device.c | 34 ++++------
drivers/of/of_reserved_mem.c | 77 +++++++++++++++++++++++
drivers/remoteproc/imx_dsp_rproc.c | 44 +++++--------
drivers/remoteproc/imx_rproc.c | 65 ++++++++-----------
drivers/remoteproc/qcom_q6v5_adsp.c | 24 +++----
drivers/remoteproc/qcom_q6v5_mss.c | 60 ++++++------------
drivers/remoteproc/qcom_q6v5_pas.c | 69 ++++++++------------
drivers/remoteproc/qcom_q6v5_wcss.c | 25 +++-----
drivers/remoteproc/qcom_wcnss.c | 23 +++----
drivers/remoteproc/rcar_rproc.c | 36 +++++------
drivers/remoteproc/st_remoteproc.c | 39 +++++-------
drivers/remoteproc/stm32_rproc.c | 42 ++++++-------
drivers/remoteproc/ti_k3_dsp_remoteproc.c | 28 ++++-----
drivers/remoteproc/ti_k3_m4_remoteproc.c | 28 ++++-----
drivers/remoteproc/ti_k3_r5_remoteproc.c | 28 ++++-----
drivers/remoteproc/xlnx_r5_remoteproc.c | 49 +++++----------
include/linux/of_reserved_mem.h | 26 ++++++++
17 files changed, 329 insertions(+), 368 deletions(-)
--
2.47.2
next reply other threads:[~2025-03-17 23:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 23:24 Rob Herring (Arm) [this message]
2025-03-17 23:24 ` [PATCH 1/3] of: reserved_mem: Add functions to parse "memory-region" Rob Herring (Arm)
2025-03-18 8:54 ` Daniel Baluta
2025-03-18 11:12 ` Jonathan Cameron
2025-03-17 23:24 ` [PATCH 2/3] of: Simplify of_dma_set_restricted_buffer() to use of_for_each_phandle() Rob Herring (Arm)
2025-03-26 6:44 ` Chen-Yu Tsai
2025-03-26 18:52 ` Rob Herring
2025-03-27 4:32 ` Chen-Yu Tsai
2025-03-17 23:24 ` [PATCH 3/3] remoteproc: Use of_reserved_mem_region_* functions for "memory-region" Rob Herring (Arm)
2025-03-18 8:57 ` Daniel Baluta
2025-03-18 10:48 ` neil.armstrong
2025-03-19 15:23 ` [Linux-stm32] " Arnaud POULIQUEN
2025-03-19 23:04 ` Rob Herring
2025-03-20 9:21 ` Arnaud POULIQUEN
2025-03-20 9:37 ` Arnaud POULIQUEN
2025-03-20 18:02 ` Rob Herring
2025-03-21 8:22 ` Arnaud POULIQUEN
2025-03-21 13:14 ` Rob Herring
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=20250317232426.952188-1-robh@kernel.org \
--to=robh@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mathieu.poirier@linaro.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=patrice.chotard@foss.st.com \
--cc=s.hauer@pengutronix.de \
--cc=saravanak@google.com \
--cc=shawnguo@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.