devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "TingHan Shen (沈廷翰)" <TingHan.Shen@mediatek.com>
To: "mathieu.poirier@linaro.org" <mathieu.poirier@linaro.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"linux-remoteproc@vger.kernel.org"
	<linux-remoteproc@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-mediatek@lists.infradead.org" 
	<linux-mediatek@lists.infradead.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	Project_Global_Chrome_Upstream_Group 
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"krzysztof.kozlowski+dt@linaro.org" 
	<krzysztof.kozlowski+dt@linaro.org>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"andersson@kernel.org" <andersson@kernel.org>,
	"angelogioacchino.delregno@collabora.com" 
	<angelogioacchino.delregno@collabora.com>
Subject: Re: [PATCH v15 07/13] remoteproc: mediatek: Probe SCP cluster on multi-core SCP
Date: Wed, 26 Jul 2023 02:55:11 +0000	[thread overview]
Message-ID: <206d7ce79c23f9ccbfcf228d42d7ee26472f4f44.camel@mediatek.com> (raw)
In-Reply-To: <ZMApsFKHbj2WPLE8@p14s>

Hi Mathieu,

On Tue, 2023-07-25 at 13:59 -0600, Mathieu Poirier wrote:
> On Fri, Jul 21, 2023 at 10:41:26AM +0800, Tinghan Shen wrote:
> > 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.
> > 
> > Add the remoteproc instances of multi-core SCP to the SCP cluster list.
> > When the SCP driver is removed, it cleanup resources by walking
> > through the cluster list.
> > 
> > Signed-off-by: Tinghan Shen <tinghan.shen@mediatek.com>
> > Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> > ---
> >  drivers/remoteproc/mtk_scp.c | 118 +++++++++++++++++++++++++++++++++--
> >  1 file changed, 113 insertions(+), 5 deletions(-)
> > 
> > diff --git a/drivers/remoteproc/mtk_scp.c b/drivers/remoteproc/mtk_scp.c
> > index d67dcabdab9e..34095a461e15 100644
> > --- a/drivers/remoteproc/mtk_scp.c
> > +++ b/drivers/remoteproc/mtk_scp.c
> > @@ -855,7 +855,8 @@ static void scp_remove_rpmsg_subdev(struct mtk_scp *scp)
> >  }
> >  
> >  static struct mtk_scp *scp_rproc_init(struct platform_device *pdev,
> > -				      struct mtk_scp_of_cluster *scp_cluster)
> > +				      struct mtk_scp_of_cluster *scp_cluster,
> > +				      const struct mtk_scp_of_data *of_data)
> >  {
> >  	struct device *dev = &pdev->dev;
> >  	struct device_node *np = dev->of_node;
> > @@ -878,7 +879,7 @@ static struct mtk_scp *scp_rproc_init(struct platform_device *pdev,
> >  	scp = rproc->priv;
> >  	scp->rproc = rproc;
> >  	scp->dev = dev;
> > -	scp->data = of_device_get_match_data(dev);
> > +	scp->data = of_data;
> >  	scp->cluster = scp_cluster;
> >  	platform_set_drvdata(pdev, scp);
> >  
> > @@ -951,15 +952,15 @@ static void scp_free(struct mtk_scp *scp)
> >  	mutex_destroy(&scp->send_lock);
> >  }
> >  
> > -static int scp_cluster_init(struct platform_device *pdev,
> > -			    struct mtk_scp_of_cluster *scp_cluster)
> > +static int scp_add_single_core(struct platform_device *pdev,
> > +			       struct mtk_scp_of_cluster *scp_cluster)
> >  {
> >  	struct device *dev = &pdev->dev;
> >  	struct list_head *scp_list = &scp_cluster->mtk_scp_list;
> >  	struct mtk_scp *scp;
> >  	int ret;
> >  
> > -	scp = scp_rproc_init(pdev, scp_cluster);
> > +	scp = scp_rproc_init(pdev, scp_cluster, of_device_get_match_data(dev));
> >  	if (IS_ERR(scp))
> >  		return PTR_ERR(scp);
> >  
> > @@ -975,6 +976,102 @@ static int scp_cluster_init(struct platform_device *pdev,
> >  	return 0;
> >  }
> >  
> > +static int scp_add_multi_core(struct platform_device *pdev,
> > +			      struct mtk_scp_of_cluster *scp_cluster)
> > +{
> > +	struct device *dev = &pdev->dev;
> > +	struct device_node *np = dev_of_node(dev);
> > +	struct platform_device *cpdev;
> > +	struct device_node *child;
> > +	struct list_head *scp_list = &scp_cluster->mtk_scp_list;
> > +	const struct mtk_scp_of_data **cluster_of_data;
> > +	struct mtk_scp *scp, *temp;
> > +	int core_id = 0;
> > +	int ret;
> > +
> > +	cluster_of_data = (const struct mtk_scp_of_data **)of_device_get_match_data(dev);
> > +
> > +	for_each_available_child_of_node(np, child) {
> > +		if (!cluster_of_data[core_id]) {
> > +			ret = -EINVAL;
> > +			dev_err(dev, "Not support core %d\n", core_id);
> > +			of_node_put(child);
> > +			goto init_fail;
> > +		}
> > +
> > +		cpdev = of_find_device_by_node(child);
> > +		if (!cpdev) {
> > +			ret = -ENODEV;
> > +			dev_err(dev, "Not found platform device for core %d\n", core_id);
> > +			of_node_put(child);
> > +			goto init_fail;
> > +		}
> > +
> > +		scp = scp_rproc_init(cpdev, scp_cluster, cluster_of_data[core_id]);
> > +		put_device(&cpdev->dev);
> > +		if (IS_ERR(scp)) {
> > +			ret = PTR_ERR(scp);
> > +			dev_err(dev, "Failed to initialize core %d rproc\n", core_id);
> > +			of_node_put(child);
> > +			goto init_fail;
> > +		}
> > +
> > +		ret = rproc_add(scp->rproc);
> > +		if (ret) {
> > +			dev_err(dev, "Failed to add rproc of core %d\n", core_id);
> > +			of_node_put(child);
> > +			scp_free(scp);
> > +			goto init_fail;
> > +		}
> > +
> > +		list_add_tail(&scp->elem, scp_list);
> > +		core_id++;
> > +	}
> > +
> > +	platform_set_drvdata(pdev, list_first_entry(scp_list, struct mtk_scp, elem));
> 
> (sigh)
> 
> Why is list_first_entry() used here rather than just @scp?  What is the purpose
> of using the list API?

I thought it would be more consistent to use the head node when removing the scp drvier.
I'll do what you suggest.


Best regards,
TingHan

> 
> > +
> > +	return 0;
> > +
> > +init_fail:
> > +	list_for_each_entry_safe_reverse(scp, temp, scp_list, elem) {
> > +		list_del(&scp->elem);
> > +		rproc_del(scp->rproc);
> > +		scp_free(scp);
> > +	}
> > +
> > +	return ret;
> > +}
> > +
> > +static int scp_is_single_core(struct platform_device *pdev)
> > +{
> > +	struct device *dev = &pdev->dev;
> > +	struct device_node *np = dev_of_node(dev);
> > +	struct device_node *child;
> > +
> > +	child = of_get_next_available_child(np, NULL);
> > +	if (!child)
> > +		return dev_err_probe(dev, -ENODEV, "No child node\n");
> > +
> > +	of_node_put(child);
> > +	return of_node_name_eq(child, "cros-ec-rpmsg");
> > +}
> > +
> > +static int scp_cluster_init(struct platform_device *pdev, struct mtk_scp_of_cluster *scp_cluster)
> > +{
> > +	int ret;
> > +
> > +	ret = scp_is_single_core(pdev);
> > +	if (ret < 0)
> > +		return ret;
> > +
> > +	if (ret)
> > +		ret = scp_add_single_core(pdev, scp_cluster);
> > +	else
> > +		ret = scp_add_multi_core(pdev, scp_cluster);
> > +
> > +	return ret;
> > +}
> > +
> >  static int scp_probe(struct platform_device *pdev)
> >  {
> >  	struct device *dev = &pdev->dev;
> > @@ -1007,6 +1104,10 @@ static int scp_probe(struct platform_device *pdev)
> >  
> >  	INIT_LIST_HEAD(&scp_cluster->mtk_scp_list);
> >  
> > +	ret = devm_of_platform_populate(dev);
> > +	if (ret)
> > +		return dev_err_probe(dev, ret, "Failed to populate platform devices\n");
> > +
> >  	ret = scp_cluster_init(pdev, scp_cluster);
> >  	if (ret)
> >  		return ret;
> > @@ -1101,12 +1202,19 @@ static const struct mtk_scp_of_data mt8195_of_data_c1 = {
> >  	.host_to_scp_int_bit = MT8195_CORE1_HOST_IPC_INT_BIT,
> >  };
> >  
> > +static const struct mtk_scp_of_data *mt8195_of_data_cores[] = {
> > +	&mt8195_of_data,
> > +	&mt8195_of_data_c1,
> > +	NULL
> > +};
> > +
> >  static const struct of_device_id mtk_scp_of_match[] = {
> >  	{ .compatible = "mediatek,mt8183-scp", .data = &mt8183_of_data },
> >  	{ .compatible = "mediatek,mt8186-scp", .data = &mt8186_of_data },
> >  	{ .compatible = "mediatek,mt8188-scp", .data = &mt8188_of_data },
> >  	{ .compatible = "mediatek,mt8192-scp", .data = &mt8192_of_data },
> >  	{ .compatible = "mediatek,mt8195-scp", .data = &mt8195_of_data },
> > +	{ .compatible = "mediatek,mt8195-scp-dual", .data = &mt8195_of_data_cores },
> >  	{},
> >  };
> >  MODULE_DEVICE_TABLE(of, mtk_scp_of_match);
> > -- 
> > 2.18.0



  reply	other threads:[~2023-07-26  2:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21  2:41 [PATCH v15 00/13] Add support for MT8195 SCP 2nd core Tinghan Shen
2023-07-21  2:41 ` [PATCH v15 01/13] dt-bindings: remoteproc: mediatek: Improve the rpmsg subnode definition Tinghan Shen
2023-07-21  2:41 ` [PATCH v15 02/13] arm64: dts: mediatek: Update the node name of SCP rpmsg subnode Tinghan Shen
2023-07-21  2:41 ` [PATCH v15 03/13] dt-bindings: remoteproc: mediatek: Support MT8195 dual-core SCP Tinghan Shen
2023-07-21  2:41 ` [PATCH v15 04/13] remoteproc: mediatek: Add MT8195 SCP core 1 operations Tinghan Shen
2023-07-21  2:41 ` [PATCH v15 05/13] remoteproc: mediatek: Extract SCP common registers Tinghan Shen
2023-07-25 19:56   ` Mathieu Poirier
2023-07-21  2:41 ` [PATCH v15 06/13] remoteproc: mediatek: Probe SCP cluster on single-core SCP Tinghan Shen
2023-07-21  2:41 ` [PATCH v15 07/13] remoteproc: mediatek: Probe SCP cluster on multi-core SCP Tinghan Shen
2023-07-25 19:59   ` Mathieu Poirier
2023-07-26  2:55     ` TingHan Shen (沈廷翰) [this message]
2023-07-21  2:41 ` [PATCH v15 08/13] remoteproc: mediatek: Remove dependency of MT8195 SCP L2TCM power control on dual-core SCP Tinghan Shen
2023-07-25 20:05   ` Mathieu Poirier
2023-07-21  2:41 ` [PATCH v15 09/13] remoteproc: mediatek: Setup MT8195 SCP core 1 SRAM offset Tinghan Shen
2023-07-21  2:41 ` [PATCH v15 10/13] remoteproc: mediatek: Handle MT8195 SCP core 1 watchdog timeout Tinghan Shen
2023-07-21  2:41 ` [PATCH v15 11/13] remoteproc: mediatek: Report watchdog crash to all cores Tinghan Shen
2023-07-21  2:41 ` [PATCH v15 12/13] remoteproc: mediatek: Refine ipi handler error message Tinghan Shen
2023-07-21  2:41 ` [PATCH v15 13/13] arm64: dts: mediatek: mt8195: Add SCP 2nd core Tinghan Shen
2023-07-25 20:34 ` [PATCH v15 00/13] Add support for MT8195 " 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=206d7ce79c23f9ccbfcf228d42d7ee26472f4f44.camel@mediatek.com \
    --to=tinghan.shen@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=andersson@kernel.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=conor+dt@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 \
    /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).