From: matthias.bgg@kernel.org To: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, matthias.bgg@gmail.com Cc: devicetree@vger.kernel.org, linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, angelogioacchino.delregno@collabora.com Subject: [PATCH v1 3/4] arm64: dts: mt8195: Align vppsys node to dtschema Date: Thu, 9 Feb 2023 17:03:56 +0100 [thread overview] Message-ID: <20230209160357.19307-3-matthias.bgg@kernel.org> (raw) In-Reply-To: <20230209160357.19307-1-matthias.bgg@kernel.org> From: Matthias Brugger <matthias.bgg@gmail.com> As the node is a syscon, this has to be reflected in the compatible and the node name. Signed-off-by: Matthias Brugger <matthias.bgg@gmail.com> --- arch/arm64/boot/dts/mediatek/mt8195.dtsi | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/arch/arm64/boot/dts/mediatek/mt8195.dtsi b/arch/arm64/boot/dts/mediatek/mt8195.dtsi index 8f1264d5290bf..5261367031426 100644 --- a/arch/arm64/boot/dts/mediatek/mt8195.dtsi +++ b/arch/arm64/boot/dts/mediatek/mt8195.dtsi @@ -1795,8 +1795,8 @@ mfgcfg: clock-controller@13fbf000 { #clock-cells = <1>; }; - vppsys0: clock-controller@14000000 { - compatible = "mediatek,mt8195-vppsys0"; + vppsys0: syscon@14000000 { + compatible = "mediatek,mt8195-vppsys0", "syscon"; reg = <0 0x14000000 0 0x1000>; #clock-cells = <1>; }; @@ -1900,8 +1900,8 @@ larb8: larb@14e05000 { power-domains = <&spm MT8195_POWER_DOMAIN_WPESYS>; }; - vppsys1: clock-controller@14f00000 { - compatible = "mediatek,mt8195-vppsys1"; + vppsys1: syscon@14f00000 { + compatible = "mediatek,mt8195-vppsys1", "syscon"; reg = <0 0x14f00000 0 0x1000>; #clock-cells = <1>; }; -- 2.39.0
WARNING: multiple messages have this Message-ID (diff)
From: matthias.bgg@kernel.org To: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, matthias.bgg@gmail.com Cc: devicetree@vger.kernel.org, linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, angelogioacchino.delregno@collabora.com Subject: [PATCH v1 3/4] arm64: dts: mt8195: Align vppsys node to dtschema Date: Thu, 9 Feb 2023 17:03:56 +0100 [thread overview] Message-ID: <20230209160357.19307-3-matthias.bgg@kernel.org> (raw) In-Reply-To: <20230209160357.19307-1-matthias.bgg@kernel.org> From: Matthias Brugger <matthias.bgg@gmail.com> As the node is a syscon, this has to be reflected in the compatible and the node name. Signed-off-by: Matthias Brugger <matthias.bgg@gmail.com> --- arch/arm64/boot/dts/mediatek/mt8195.dtsi | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/arch/arm64/boot/dts/mediatek/mt8195.dtsi b/arch/arm64/boot/dts/mediatek/mt8195.dtsi index 8f1264d5290bf..5261367031426 100644 --- a/arch/arm64/boot/dts/mediatek/mt8195.dtsi +++ b/arch/arm64/boot/dts/mediatek/mt8195.dtsi @@ -1795,8 +1795,8 @@ mfgcfg: clock-controller@13fbf000 { #clock-cells = <1>; }; - vppsys0: clock-controller@14000000 { - compatible = "mediatek,mt8195-vppsys0"; + vppsys0: syscon@14000000 { + compatible = "mediatek,mt8195-vppsys0", "syscon"; reg = <0 0x14000000 0 0x1000>; #clock-cells = <1>; }; @@ -1900,8 +1900,8 @@ larb8: larb@14e05000 { power-domains = <&spm MT8195_POWER_DOMAIN_WPESYS>; }; - vppsys1: clock-controller@14f00000 { - compatible = "mediatek,mt8195-vppsys1"; + vppsys1: syscon@14f00000 { + compatible = "mediatek,mt8195-vppsys1", "syscon"; reg = <0 0x14f00000 0 0x1000>; #clock-cells = <1>; }; -- 2.39.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:[~2023-02-09 16:04 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-09 16:03 [PATCH v1 1/4] arm64: dts: mt8195: Update vdosys compatible matthias.bgg 2023-02-09 16:03 ` matthias.bgg 2023-02-09 16:03 ` [PATCH v1 2/4] arm64: dts: mt8167: Align mmsys node name with dtschema matthias.bgg 2023-02-09 16:03 ` matthias.bgg 2023-02-10 2:42 ` Chen-Yu Tsai 2023-02-10 2:42 ` Chen-Yu Tsai 2023-02-10 11:59 ` AngeloGioacchino Del Regno 2023-02-10 11:59 ` AngeloGioacchino Del Regno 2023-02-09 16:03 ` matthias.bgg [this message] 2023-02-09 16:03 ` [PATCH v1 3/4] arm64: dts: mt8195: Align vppsys node to dtschema matthias.bgg 2023-02-10 2:42 ` Chen-Yu Tsai 2023-02-10 2:42 ` Chen-Yu Tsai 2023-02-10 11:59 ` AngeloGioacchino Del Regno 2023-02-10 11:59 ` AngeloGioacchino Del Regno 2023-03-02 11:07 ` Matthias Brugger 2023-03-02 11:07 ` Matthias Brugger 2023-02-09 16:03 ` [PATCH v1 4/4] Revert "arm64: dts: mt8173: add mmsel clocks for 4K support" matthias.bgg 2023-02-09 16:03 ` matthias.bgg 2023-02-10 2:44 ` Chen-Yu Tsai 2023-02-10 2:44 ` Chen-Yu Tsai 2023-02-10 11:59 ` AngeloGioacchino Del Regno 2023-02-10 11:59 ` AngeloGioacchino Del Regno 2023-03-02 11:03 ` Matthias Brugger 2023-03-02 11:03 ` Matthias Brugger 2023-02-10 2:41 ` [PATCH v1 1/4] arm64: dts: mt8195: Update vdosys compatible Chen-Yu Tsai 2023-02-10 2:41 ` Chen-Yu Tsai 2023-02-10 11:59 ` AngeloGioacchino Del Regno 2023-02-10 11:59 ` AngeloGioacchino Del Regno 2023-03-02 11:26 ` Matthias Brugger 2023-03-02 11:26 ` Matthias Brugger
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=20230209160357.19307-3-matthias.bgg@kernel.org \ --to=matthias.bgg@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=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: 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.