From: Tanmay Shah <tanmay.shah@amd.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>,
"Rob Herring (Arm)" <robh@kernel.org>,
Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>,
Daniel Baluta <daniel.baluta@nxp.com>,
Iuliana Prodan <iuliana.prodan@nxp.com>,
"Andrew F. Davis" <afd@ti.com>
Cc: Saravana Kannan <saravanak@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Bjorn Andersson <andersson@kernel.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>,
Chen-Yu Tsai <wens@kernel.org>,
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: Re: [PATCH v2 0/4] of: Common "memory-region" parsing
Date: Thu, 1 May 2025 18:56:54 -0500 [thread overview]
Message-ID: <ab09cbdb-8e30-4720-8ca5-66488922db33@amd.com> (raw)
In-Reply-To: <8c8e9362-c116-4a80-bcb7-a44df68e0bfc@amd.com>
On 5/1/25 10:44 AM, Tanmay Shah wrote:
> Hi Mathieu,
>
> I tested this patchset on top of recent for-next branch. I don't see
> issue on AMD-xlnx ZynqMP platform. With this:
>
> Tested-by: Tanmay Shah <tanmay.shah@amd.com>
>
Hi Mathieu,
Looks like I said it too soon. Firmware loading works with this series,
but RPMsg doesn't work. I am debugging further and will provide inputs
once I find bug on xlnx_r5_remoteproc driver.
Please ignore above TB for now.
Thanks,
Tanmay
> On 4/24/25 9:14 AM, Mathieu Poirier wrote:
>> Arnaud, Daniel, Iuliana, Andrew and Tanmay - please test this patchset
>> on the platforms you are working on.
>>
>> Thanks,
>> Mathieu
>>
>> On Wed, 23 Apr 2025 at 13:42, Rob Herring (Arm) <robh@kernel.org> wrote:
>>>
>>> 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 3 patches for 6.16
>>> so the driver conversions can be applied for 6.17.
>>>
>>> A git tree with all the drivers converted is here[1].
>>>
>>> v2:
>>> - Fix of_dma_set_restricted_buffer() to maintain behavior on warning msg
>>> - Export devm_ioremap_resource_wc()
>>> - Rework handling of resource name to drop unit-address from name as it
>>> was before.
>>> - Link to v1:
>>> https://lore.kernel.org/all/20250317232426.952188-1-robh@kernel.org
>>>
>>> [1] git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git dt/
>>> memory-region
>>>
>>> Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
>>> ---
>>> Rob Herring (Arm) (4):
>>> of: reserved_mem: Add functions to parse "memory-region"
>>> of: Simplify of_dma_set_restricted_buffer() to use
>>> of_for_each_phandle()
>>> devres: Export devm_ioremap_resource_wc()
>>> remoteproc: Use of_reserved_mem_region_* functions for
>>> "memory-region"
>>>
>>> drivers/of/device.c | 31 +++++-------
>>> drivers/of/of_reserved_mem.c | 80 ++++++++++++++++++++
>>> +++++++++++
>>> drivers/remoteproc/imx_dsp_rproc.c | 45 +++++++----------
>>> drivers/remoteproc/imx_rproc.c | 68 ++++++++++
>>> +---------------
>>> 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 | 41 ++++++++--------
>>> drivers/remoteproc/stm32_rproc.c | 44 ++++++++---------
>>> 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 | 51 ++++++++------------
>>> include/linux/of_reserved_mem.h | 26 ++++++++++
>>> lib/devres.c | 1 +
>>> 18 files changed, 339 insertions(+), 369 deletions(-)
>>> ---
>>> base-commit: 0af2f6be1b4281385b618cb86ad946eded089ac8
>>> change-id: 20250423-dt-memory-region-v2-a2b15caacc63
>>>
>>> Best regards,
>>> --
>>> Rob Herring (Arm) <robh@kernel.org>
>>>
>
next prev parent reply other threads:[~2025-05-01 23:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 19:42 [PATCH v2 0/4] of: Common "memory-region" parsing Rob Herring (Arm)
2025-04-23 19:42 ` [PATCH v2 1/4] of: reserved_mem: Add functions to parse "memory-region" Rob Herring (Arm)
2025-04-28 8:07 ` Arnaud POULIQUEN
2025-04-23 19:42 ` [PATCH v2 2/4] of: Simplify of_dma_set_restricted_buffer() to use of_for_each_phandle() Rob Herring (Arm)
2025-04-23 19:42 ` [PATCH v2 3/4] devres: Export devm_ioremap_resource_wc() Rob Herring (Arm)
2025-04-23 19:42 ` [PATCH v2 4/4] remoteproc: Use of_reserved_mem_region_* functions for "memory-region" Rob Herring (Arm)
2025-05-02 15:40 ` Tanmay Shah
2025-05-02 20:33 ` Rob Herring
2025-04-24 14:14 ` [PATCH v2 0/4] of: Common "memory-region" parsing Mathieu Poirier
2025-04-25 23:34 ` Iuliana Prodan
2025-04-28 12:23 ` Rob Herring
2025-04-28 21:40 ` Iuliana Prodan
2025-05-01 15:44 ` Tanmay Shah
2025-05-01 23:56 ` Tanmay Shah [this message]
2025-04-28 8:16 ` Arnaud POULIQUEN
2025-05-07 4:42 ` Peng Fan
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=ab09cbdb-8e30-4720-8ca5-66488922db33@amd.com \
--to=tanmay.shah@amd.com \
--cc=afd@ti.com \
--cc=akpm@linux-foundation.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andersson@kernel.org \
--cc=arnaud.pouliquen@foss.st.com \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=iuliana.prodan@nxp.com \
--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=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=saravanak@google.com \
--cc=shawnguo@kernel.org \
--cc=wens@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox