From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Shun-yi Wang <shun-yi.wang@mediatek.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Project_Global_Chrome_Upstream_Group@mediatek.com,
jason-ch.chen@mediatek.com, yaya.chang@mediatek.com,
teddy.chen@mediatek.com, olivia.wen@mediatek.com
Subject: Re: [PATCH 1/1] remoteproc: mediatek: Support multiple reserved memory regions
Date: Wed, 10 Jul 2024 09:56:32 -0600 [thread overview]
Message-ID: <Zo6vMPaefxCaDe7D@p14s> (raw)
In-Reply-To: <20240703115308.17436-2-shun-yi.wang@mediatek.com>
On Wed, Jul 03, 2024 at 07:53:08PM +0800, Shun-yi Wang wrote:
> From: "shun-yi.wang" <shun-yi.wang@mediatek.com>
>
> SCP supports multiple reserved memory regions, intended for
> specific hardwards.
>
> Signed-off-by: shun-yi.wang <shun-yi.wang@mediatek.com>
> ---
> drivers/remoteproc/mtk_scp.c | 25 +++++++++++++++++--------
> 1 file changed, 17 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/remoteproc/mtk_scp.c b/drivers/remoteproc/mtk_scp.c
> index 9ecd5ea04b5f3..1902826cea0af 100644
> --- a/drivers/remoteproc/mtk_scp.c
> +++ b/drivers/remoteproc/mtk_scp.c
> @@ -1006,22 +1006,31 @@ EXPORT_SYMBOL_GPL(scp_mapping_dm_addr);
>
> static int scp_map_memory_region(struct mtk_scp *scp)
> {
> - int ret;
> + int ret, i, err;
> const struct mtk_scp_sizes_data *scp_sizes;
> + struct device_node *node = scp->dev->of_node;
> + struct of_phandle_iterator it;
> +
> + i = 0;
> + of_for_each_phandle(&it, err, node, "memory-region", NULL, 0) {
> + ret = of_reserved_mem_device_init_by_idx(scp->dev, node, i);
> +
> + if (ret) {
> + dev_err(scp->dev, "failed to assign memory-region: %s\n",
> + it.node->name);
> + of_node_put(it.node);
> + return -ENOMEM;
> + }
With this patch the code is out of sync with the bindings which are still
specifying a maxItems of 1 - please address.
Thanks,
Mathieu
>
> - ret = of_reserved_mem_device_init(scp->dev);
> + i++;
> + }
>
> /* reserved memory is optional. */
> - if (ret == -ENODEV) {
> + if (!i) {
> dev_info(scp->dev, "skipping reserved memory initialization.");
> return 0;
> }
>
> - if (ret) {
> - dev_err(scp->dev, "failed to assign memory-region: %d\n", ret);
> - return -ENOMEM;
> - }
> -
> /* Reserved SCP code size */
> scp_sizes = scp->data->scp_sizes;
> scp->cpu_addr = dma_alloc_coherent(scp->dev, scp_sizes->max_dram_size,
> --
> 2.18.0
>
next prev parent reply other threads:[~2024-07-10 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 11:53 [PATCH 0/1] Support multiple reserved memory regions Shun-yi Wang
2024-07-03 11:53 ` [PATCH 1/1] remoteproc: mediatek: " Shun-yi Wang
2024-07-10 15:56 ` Mathieu Poirier [this message]
2024-07-12 8:21 ` AngeloGioacchino Del Regno
2024-07-10 15:54 ` [PATCH 0/1] " Mathieu Poirier
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=Zo6vMPaefxCaDe7D@p14s \
--to=mathieu.poirier@linaro.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=andersson@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=jason-ch.chen@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=olivia.wen@mediatek.com \
--cc=shun-yi.wang@mediatek.com \
--cc=teddy.chen@mediatek.com \
--cc=yaya.chang@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).