From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Tinghan Shen <tinghan.shen@mediatek.com>,
Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: linux-remoteproc@vger.kernel.org, devicetree@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
Subject: Re: [PATCH v6 07/12] remoteproc: mediatek: Probe multi-core SCP
Date: Mon, 13 Feb 2023 15:58:15 +0100 [thread overview]
Message-ID: <407e8e4e-fdcc-26ab-0bb3-e03b59f0d25c@collabora.com> (raw)
In-Reply-To: <20230213033758.16681-8-tinghan.shen@mediatek.com>
Il 13/02/23 04:37, Tinghan Shen ha scritto:
> The difference of single-core SCP and multi-core SCP device tree is
> the presence of child device nodes described SCP cores. The SCP
> driver populates the platform device and checks the child nodes
> to identify whether it's a single-core SCP or a multi-core SCP.
>
> The resource structure of the multi-core SCP is a list of remoteproc
> instances which is different to the single-core SCP. The corresponding
> resource releasing action is based on the type of SCP.
>
> Signed-off-by: Tinghan Shen <tinghan.shen@mediatek.com>
> ---
> drivers/remoteproc/mtk_common.h | 7 ++
> drivers/remoteproc/mtk_scp.c | 177 +++++++++++++++++++++++++++++---
> 2 files changed, 169 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/remoteproc/mtk_common.h b/drivers/remoteproc/mtk_common.h
> index 3778894c96f3..635b17676de8 100644
> --- a/drivers/remoteproc/mtk_common.h
> +++ b/drivers/remoteproc/mtk_common.h
> @@ -112,6 +112,10 @@ struct mtk_scp_of_data {
> size_t ipi_buf_offset;
> };
>
> +struct mtk_scp_cluster {
> + struct list_head cores;
You don't need this structure... it's just one element inside, so you can
simply add it to `struct mtk_scp` instead: for readability purposes, you
can call this list `cluster_cores`.
After which
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
next prev parent reply other threads:[~2023-02-13 14:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 3:37 [PATCH v6 00/12] Add support for MT8195 SCP 2nd core Tinghan Shen
2023-02-13 3:37 ` [PATCH v6 01/12] dt-bindings: remoteproc: mediatek: Improve the rpmsg subnode definition Tinghan Shen
2023-02-13 3:37 ` [PATCH v6 02/12] arm64: dts: mediatek: mt8183-kukui: Update the node name of SCP rpmsg subnode Tinghan Shen
2023-02-13 3:37 ` [PATCH v6 03/12] dt-bindings: remoteproc: mediatek: Support MT8195 dual-core SCP Tinghan Shen
2023-02-13 3:37 ` [PATCH v6 04/12] remoteproc: mediatek: Add SCP core 1 register definitions Tinghan Shen
2023-02-13 3:37 ` [PATCH v6 05/12] remoteproc: mediatek: Add MT8195 SCP core 1 operations Tinghan Shen
2023-02-13 14:52 ` AngeloGioacchino Del Regno
2023-02-13 3:37 ` [PATCH v6 06/12] remoteproc: mediatek: Extract remoteproc initialization flow Tinghan Shen
2023-02-13 14:53 ` AngeloGioacchino Del Regno
2023-02-13 3:37 ` [PATCH v6 07/12] remoteproc: mediatek: Probe multi-core SCP Tinghan Shen
2023-02-13 14:58 ` AngeloGioacchino Del Regno [this message]
2023-02-15 3:55 ` TingHan Shen (沈廷翰)
2023-02-13 3:37 ` [PATCH v6 08/12] remoteproc: mediatek: Control SCP core 1 by rproc subdevice Tinghan Shen
2023-02-13 14:58 ` AngeloGioacchino Del Regno
2023-02-13 3:37 ` [PATCH v6 09/12] remoteproc: mediatek: Setup MT8195 SCP core 1 SRAM offset Tinghan Shen
2023-02-13 14:59 ` AngeloGioacchino Del Regno
2023-02-13 3:37 ` [PATCH v6 10/12] remoteproc: mediatek: Handle MT8195 SCP core 1 watchdog timeout Tinghan Shen
2023-02-13 3:37 ` [PATCH v6 11/12] remoteproc: mediatek: Refine ipi handler error message Tinghan Shen
2023-02-13 3:37 ` [PATCH v6 12/12] arm64: dts: mediatek: mt8195: Add SCP 2nd core Tinghan Shen
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=407e8e4e-fdcc-26ab-0bb3-e03b59f0d25c@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--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=mathieu.poirier@linaro.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=tinghan.shen@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