From: "Nícolas F. R. A. Prado" <nfraprado@collabora.com> To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>, Matthias Brugger <matthias.bgg@gmail.com> Cc: "Rob Herring" <robh@kernel.org>, "Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>, "Conor Dooley" <conor+dt@kernel.org>, "Allen-KH Cheng" <allen-kh.cheng@mediatek.com>, "Tinghan Shen" <tinghan.shen@mediatek.com>, "Jason-JH.Lin" <jason-jh.lin@mediatek.com>, "Nancy.Lin" <nancy.lin@mediatek.com>, kernel@collabora.com, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, "Nícolas F. R. A. Prado" <nfraprado@collabora.com> Subject: [PATCH 3/4] arm64: dts: mediatek: mt8195: Add missing gce-client-reg to mutex Date: Thu, 29 Feb 2024 14:44:30 -0500 [thread overview] Message-ID: <20240229-gce-client-reg-add-missing-mt8192-95-v1-3-b12c233a8a33@collabora.com> (raw) In-Reply-To: <20240229-gce-client-reg-add-missing-mt8192-95-v1-0-b12c233a8a33@collabora.com> Add the missing mediatek,gce-client-reg property to the mutex node to allow it to use the GCE. This prevents the "can't parse gce-client-reg property" error from being printed and should result in better performance. Fixes: b852ee68fd72 ("arm64: dts: mt8195: Add display node for vdosys0") Suggested-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com> --- arch/arm64/boot/dts/mediatek/mt8195.dtsi | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/boot/dts/mediatek/mt8195.dtsi b/arch/arm64/boot/dts/mediatek/mt8195.dtsi index f2912e1a0e49..fd074103979c 100644 --- a/arch/arm64/boot/dts/mediatek/mt8195.dtsi +++ b/arch/arm64/boot/dts/mediatek/mt8195.dtsi @@ -3264,6 +3264,7 @@ mutex: mutex@1c016000 { interrupts = <GIC_SPI 658 IRQ_TYPE_LEVEL_HIGH 0>; power-domains = <&spm MT8195_POWER_DOMAIN_VDOSYS0>; clocks = <&vdosys0 CLK_VDO0_DISP_MUTEX0>; + mediatek,gce-client-reg = <&gce0 SUBSYS_1c01XXXX 0x6000 0x1000>; mediatek,gce-events = <CMDQ_EVENT_VDO0_DISP_STREAM_DONE_0>; }; -- 2.44.0
WARNING: multiple messages have this Message-ID (diff)
From: "Nícolas F. R. A. Prado" <nfraprado@collabora.com> To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>, Matthias Brugger <matthias.bgg@gmail.com> Cc: "Rob Herring" <robh@kernel.org>, "Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>, "Conor Dooley" <conor+dt@kernel.org>, "Allen-KH Cheng" <allen-kh.cheng@mediatek.com>, "Tinghan Shen" <tinghan.shen@mediatek.com>, "Jason-JH.Lin" <jason-jh.lin@mediatek.com>, "Nancy.Lin" <nancy.lin@mediatek.com>, kernel@collabora.com, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, "Nícolas F. R. A. Prado" <nfraprado@collabora.com> Subject: [PATCH 3/4] arm64: dts: mediatek: mt8195: Add missing gce-client-reg to mutex Date: Thu, 29 Feb 2024 14:44:30 -0500 [thread overview] Message-ID: <20240229-gce-client-reg-add-missing-mt8192-95-v1-3-b12c233a8a33@collabora.com> (raw) In-Reply-To: <20240229-gce-client-reg-add-missing-mt8192-95-v1-0-b12c233a8a33@collabora.com> Add the missing mediatek,gce-client-reg property to the mutex node to allow it to use the GCE. This prevents the "can't parse gce-client-reg property" error from being printed and should result in better performance. Fixes: b852ee68fd72 ("arm64: dts: mt8195: Add display node for vdosys0") Suggested-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com> --- arch/arm64/boot/dts/mediatek/mt8195.dtsi | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/boot/dts/mediatek/mt8195.dtsi b/arch/arm64/boot/dts/mediatek/mt8195.dtsi index f2912e1a0e49..fd074103979c 100644 --- a/arch/arm64/boot/dts/mediatek/mt8195.dtsi +++ b/arch/arm64/boot/dts/mediatek/mt8195.dtsi @@ -3264,6 +3264,7 @@ mutex: mutex@1c016000 { interrupts = <GIC_SPI 658 IRQ_TYPE_LEVEL_HIGH 0>; power-domains = <&spm MT8195_POWER_DOMAIN_VDOSYS0>; clocks = <&vdosys0 CLK_VDO0_DISP_MUTEX0>; + mediatek,gce-client-reg = <&gce0 SUBSYS_1c01XXXX 0x6000 0x1000>; mediatek,gce-events = <CMDQ_EVENT_VDO0_DISP_STREAM_DONE_0>; }; -- 2.44.0 _______________________________________________ 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:[~2024-02-29 19:44 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-29 19:44 [PATCH 0/4] arm64: dts: mediatek: Add missing gce-client-reg properties to mt8192 and mt8195 Nícolas F. R. A. Prado 2024-02-29 19:44 ` Nícolas F. R. A. Prado 2024-02-29 19:44 ` [PATCH 1/4] arm64: dts: mediatek: mt8192: Add missing gce-client-reg to mutex Nícolas F. R. A. Prado 2024-02-29 19:44 ` Nícolas F. R. A. Prado 2024-03-01 8:48 ` AngeloGioacchino Del Regno 2024-03-01 8:48 ` AngeloGioacchino Del Regno 2024-02-29 19:44 ` [PATCH 2/4] arm64: dts: mediatek: mt8195: Add missing gce-client-reg to vpp/vdosys Nícolas F. R. A. Prado 2024-02-29 19:44 ` Nícolas F. R. A. Prado 2024-03-01 8:50 ` AngeloGioacchino Del Regno 2024-03-01 8:50 ` AngeloGioacchino Del Regno 2024-03-01 14:39 ` Nícolas F. R. A. Prado 2024-03-01 14:39 ` Nícolas F. R. A. Prado 2024-03-04 10:16 ` AngeloGioacchino Del Regno 2024-03-04 10:16 ` AngeloGioacchino Del Regno 2024-02-29 19:44 ` Nícolas F. R. A. Prado [this message] 2024-02-29 19:44 ` [PATCH 3/4] arm64: dts: mediatek: mt8195: Add missing gce-client-reg to mutex Nícolas F. R. A. Prado 2024-02-29 19:44 ` [PATCH 4/4] arm64: dts: mediatek: mt8195: Add missing gce-client-reg to mutex1 Nícolas F. R. A. Prado 2024-02-29 19:44 ` Nícolas F. R. A. Prado 2024-04-03 10:30 ` [PATCH 0/4] arm64: dts: mediatek: Add missing gce-client-reg properties to mt8192 and mt8195 AngeloGioacchino Del Regno 2024-04-03 10:30 ` AngeloGioacchino Del Regno
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=20240229-gce-client-reg-add-missing-mt8192-95-v1-3-b12c233a8a33@collabora.com \ --to=nfraprado@collabora.com \ --cc=allen-kh.cheng@mediatek.com \ --cc=angelogioacchino.delregno@collabora.com \ --cc=conor+dt@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=jason-jh.lin@mediatek.com \ --cc=kernel@collabora.com \ --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=matthias.bgg@gmail.com \ --cc=nancy.lin@mediatek.com \ --cc=robh@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: linkBe 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.