From: Matthias Brugger <matthias.bgg@gmail.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>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.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 v9 11/11] arm64: dts: mediatek: mt8195: Add SCP 2nd core
Date: Fri, 31 Mar 2023 12:59:57 +0200 [thread overview]
Message-ID: <848971ea-b142-d088-df6f-74ee2d807950@gmail.com> (raw)
In-Reply-To: <20230328022733.29910-12-tinghan.shen@mediatek.com>
On 28/03/2023 04:27, Tinghan Shen wrote:
> Rewrite the MT8195 SCP device node as a cluster and
> add the SCP 2nd core in it.
>
> Since the SCP device node is changed to multi-core structure,
> enable SCP cluster to enable probing SCP core 0.
>
> Signed-off-by: Tinghan Shen <tinghan.shen@mediatek.com>
> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
As this is a bigger change I'd prefer to take it through my tree once the driver
and dt-bindings changes are merged. Given the fact, maybe it would make sense to
take 2/11 through my tree as well.
Regards,
Matthias
> ---
> .../boot/dts/mediatek/mt8195-cherry.dtsi | 6 +++-
> arch/arm64/boot/dts/mediatek/mt8195.dtsi | 32 ++++++++++++++-----
> 2 files changed, 29 insertions(+), 9 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi b/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi
> index 56749cfe7c33..31415d71b6a4 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi
> @@ -933,7 +933,11 @@
> interrupts-extended = <&pio 222 IRQ_TYPE_LEVEL_HIGH>;
> };
>
> -&scp {
> +&scp_cluster {
> + status = "okay";
> +};
> +
> +&scp_c0 {
> status = "okay";
>
> firmware-name = "mediatek/mt8195/scp.img";
> diff --git a/arch/arm64/boot/dts/mediatek/mt8195.dtsi b/arch/arm64/boot/dts/mediatek/mt8195.dtsi
> index 8fc527570791..5fe5fb32261e 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8195.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8195.dtsi
> @@ -826,14 +826,30 @@
> clocks = <&infracfg_ao CLK_INFRA_AO_GCE2>;
> };
>
> - scp: scp@10500000 {
> - compatible = "mediatek,mt8195-scp";
> - reg = <0 0x10500000 0 0x100000>,
> - <0 0x10720000 0 0xe0000>,
> - <0 0x10700000 0 0x8000>;
> - reg-names = "sram", "cfg", "l1tcm";
> - interrupts = <GIC_SPI 462 IRQ_TYPE_LEVEL_HIGH 0>;
> + scp_cluster: scp@10500000 {
> + compatible = "mediatek,mt8195-scp-dual";
> + reg = <0 0x10720000 0 0xe0000>, <0 0x10700000 0 0x8000>;
> + reg-names = "cfg", "l1tcm";
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges = <0 0 0x10500000 0x100000>;
> status = "disabled";
> +
> + scp_c0: scp@0 {
> + compatible = "mediatek,scp-core";
> + reg = <0x0 0xa0000>;
> + reg-names = "sram";
> + interrupts = <GIC_SPI 462 IRQ_TYPE_LEVEL_HIGH 0>;
> + status = "disabled";
> + };
> +
> + scp_c1: scp@a0000 {
> + compatible = "mediatek,scp-core";
> + reg = <0xa0000 0x20000>;
> + reg-names = "sram";
> + interrupts = <GIC_SPI 463 IRQ_TYPE_LEVEL_HIGH 0>;
> + status = "disabled";
> + };
> };
>
> scp_adsp: clock-controller@10720000 {
> @@ -2309,7 +2325,7 @@
> <&iommu_vdo M4U_PORT_L19_VENC_REF_LUMA>,
> <&iommu_vdo M4U_PORT_L19_VENC_REF_CHROMA>;
> interrupts = <GIC_SPI 341 IRQ_TYPE_LEVEL_HIGH 0>;
> - mediatek,scp = <&scp>;
> + mediatek,scp = <&scp_c0>;
> clocks = <&vencsys CLK_VENC_VENC>;
> clock-names = "venc_sel";
> assigned-clocks = <&topckgen CLK_TOP_VENC>;
WARNING: multiple messages have this Message-ID (diff)
From: Matthias Brugger <matthias.bgg@gmail.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>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.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 v9 11/11] arm64: dts: mediatek: mt8195: Add SCP 2nd core
Date: Fri, 31 Mar 2023 12:59:57 +0200 [thread overview]
Message-ID: <848971ea-b142-d088-df6f-74ee2d807950@gmail.com> (raw)
In-Reply-To: <20230328022733.29910-12-tinghan.shen@mediatek.com>
On 28/03/2023 04:27, Tinghan Shen wrote:
> Rewrite the MT8195 SCP device node as a cluster and
> add the SCP 2nd core in it.
>
> Since the SCP device node is changed to multi-core structure,
> enable SCP cluster to enable probing SCP core 0.
>
> Signed-off-by: Tinghan Shen <tinghan.shen@mediatek.com>
> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
As this is a bigger change I'd prefer to take it through my tree once the driver
and dt-bindings changes are merged. Given the fact, maybe it would make sense to
take 2/11 through my tree as well.
Regards,
Matthias
> ---
> .../boot/dts/mediatek/mt8195-cherry.dtsi | 6 +++-
> arch/arm64/boot/dts/mediatek/mt8195.dtsi | 32 ++++++++++++++-----
> 2 files changed, 29 insertions(+), 9 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi b/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi
> index 56749cfe7c33..31415d71b6a4 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi
> @@ -933,7 +933,11 @@
> interrupts-extended = <&pio 222 IRQ_TYPE_LEVEL_HIGH>;
> };
>
> -&scp {
> +&scp_cluster {
> + status = "okay";
> +};
> +
> +&scp_c0 {
> status = "okay";
>
> firmware-name = "mediatek/mt8195/scp.img";
> diff --git a/arch/arm64/boot/dts/mediatek/mt8195.dtsi b/arch/arm64/boot/dts/mediatek/mt8195.dtsi
> index 8fc527570791..5fe5fb32261e 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8195.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8195.dtsi
> @@ -826,14 +826,30 @@
> clocks = <&infracfg_ao CLK_INFRA_AO_GCE2>;
> };
>
> - scp: scp@10500000 {
> - compatible = "mediatek,mt8195-scp";
> - reg = <0 0x10500000 0 0x100000>,
> - <0 0x10720000 0 0xe0000>,
> - <0 0x10700000 0 0x8000>;
> - reg-names = "sram", "cfg", "l1tcm";
> - interrupts = <GIC_SPI 462 IRQ_TYPE_LEVEL_HIGH 0>;
> + scp_cluster: scp@10500000 {
> + compatible = "mediatek,mt8195-scp-dual";
> + reg = <0 0x10720000 0 0xe0000>, <0 0x10700000 0 0x8000>;
> + reg-names = "cfg", "l1tcm";
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges = <0 0 0x10500000 0x100000>;
> status = "disabled";
> +
> + scp_c0: scp@0 {
> + compatible = "mediatek,scp-core";
> + reg = <0x0 0xa0000>;
> + reg-names = "sram";
> + interrupts = <GIC_SPI 462 IRQ_TYPE_LEVEL_HIGH 0>;
> + status = "disabled";
> + };
> +
> + scp_c1: scp@a0000 {
> + compatible = "mediatek,scp-core";
> + reg = <0xa0000 0x20000>;
> + reg-names = "sram";
> + interrupts = <GIC_SPI 463 IRQ_TYPE_LEVEL_HIGH 0>;
> + status = "disabled";
> + };
> };
>
> scp_adsp: clock-controller@10720000 {
> @@ -2309,7 +2325,7 @@
> <&iommu_vdo M4U_PORT_L19_VENC_REF_LUMA>,
> <&iommu_vdo M4U_PORT_L19_VENC_REF_CHROMA>;
> interrupts = <GIC_SPI 341 IRQ_TYPE_LEVEL_HIGH 0>;
> - mediatek,scp = <&scp>;
> + mediatek,scp = <&scp_c0>;
> clocks = <&vencsys CLK_VENC_VENC>;
> clock-names = "venc_sel";
> assigned-clocks = <&topckgen CLK_TOP_VENC>;
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-03-31 11:00 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 2:27 [PATCH v9 00/11] Add support for MT8195 SCP 2nd core Tinghan Shen
2023-03-28 2:27 ` Tinghan Shen
2023-03-28 2:27 ` [PATCH v9 01/11] dt-bindings: remoteproc: mediatek: Improve the rpmsg subnode definition Tinghan Shen
2023-03-28 2:27 ` Tinghan Shen
2023-03-28 2:27 ` [PATCH v9 02/11] arm64: dts: mediatek: Update the node name of SCP rpmsg subnode Tinghan Shen
2023-03-28 2:27 ` Tinghan Shen
2023-03-31 10:57 ` Matthias Brugger
2023-03-31 10:57 ` Matthias Brugger
2023-03-28 2:27 ` [PATCH v9 03/11] dt-bindings: remoteproc: mediatek: Support MT8195 dual-core SCP Tinghan Shen
2023-03-28 2:27 ` Tinghan Shen
2023-03-28 2:27 ` [PATCH v9 04/11] remoteproc: mediatek: Add MT8195 SCP core 1 operations Tinghan Shen
2023-03-28 2:27 ` Tinghan Shen
2023-03-28 2:27 ` [PATCH v9 05/11] remoteproc: mediatek: Extract remoteproc initialization flow Tinghan Shen
2023-03-28 2:27 ` Tinghan Shen
2023-03-31 17:44 ` Mathieu Poirier
2023-03-31 17:44 ` Mathieu Poirier
2023-04-19 3:38 ` TingHan Shen (沈廷翰)
2023-04-19 3:38 ` TingHan Shen (沈廷翰)
2023-04-19 15:09 ` Mathieu Poirier
2023-04-19 15:09 ` Mathieu Poirier
2023-03-28 2:27 ` [PATCH v9 06/11] remoteproc: mediatek: Probe multi-core SCP Tinghan Shen
2023-03-28 2:27 ` Tinghan Shen
2023-03-31 17:53 ` Mathieu Poirier
2023-03-31 17:53 ` Mathieu Poirier
2023-03-28 2:27 ` [PATCH v9 07/11] remoteproc: mediatek: Control SCP core 1 by rproc subdevice Tinghan Shen
2023-03-28 2:27 ` Tinghan Shen
2023-03-28 2:27 ` [PATCH v9 08/11] remoteproc: mediatek: Setup MT8195 SCP core 1 SRAM offset Tinghan Shen
2023-03-28 2:27 ` Tinghan Shen
2023-03-28 2:27 ` [PATCH v9 09/11] remoteproc: mediatek: Handle MT8195 SCP core 1 watchdog timeout Tinghan Shen
2023-03-28 2:27 ` Tinghan Shen
2023-03-28 2:27 ` [PATCH v9 10/11] remoteproc: mediatek: Refine ipi handler error message Tinghan Shen
2023-03-28 2:27 ` Tinghan Shen
2023-03-28 2:27 ` [PATCH v9 11/11] arm64: dts: mediatek: mt8195: Add SCP 2nd core Tinghan Shen
2023-03-28 2:27 ` Tinghan Shen
2023-03-31 10:59 ` Matthias Brugger [this message]
2023-03-31 10:59 ` Matthias Brugger
2023-04-03 17:25 ` Mathieu Poirier
2023-04-03 17:25 ` 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=848971ea-b142-d088-df6f-74ee2d807950@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=andersson@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--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=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 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.