devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: matthias.bgg@kernel.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org
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: Re: [PATCH v1 1/4] arm64: dts: mt8195: Update vdosys compatible
Date: Thu, 2 Mar 2023 12:26:25 +0100	[thread overview]
Message-ID: <1f65671b-7c68-b007-60c8-6c4841febce0@gmail.com> (raw)
In-Reply-To: <20230209160357.19307-1-matthias.bgg@kernel.org>

Patch 1 and 2 applied.

Matthias

On 09/02/2023 17:03, matthias.bgg@kernel.org wrote:
> From: Matthias Brugger <matthias.bgg@gmail.com>
> 
> In an effort to fix the vdosys implementation, the compatible has
> changes. Fix the device tree to adhere the binding definition.
> 
> Signed-off-by: Matthias Brugger <matthias.bgg@gmail.com>
> ---
> 
>   arch/arm64/boot/dts/mediatek/mt8195.dtsi | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm64/boot/dts/mediatek/mt8195.dtsi b/arch/arm64/boot/dts/mediatek/mt8195.dtsi
> index 00891bfa564e9..8f1264d5290bf 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8195.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8195.dtsi
> @@ -2369,7 +2369,7 @@ vencsys_core1: clock-controller@1b000000 {
>   		};
>   
>   		vdosys0: syscon@1c01a000 {
> -			compatible = "mediatek,mt8195-mmsys", "syscon";
> +			compatible = "mediatek,mt8195-vdosys0", "mediatek,mt8195-mmsys", "syscon";
>   			reg = <0 0x1c01a000 0 0x1000>;
>   			mboxes = <&gce0 0 CMDQ_THR_PRIO_4>;
>   			#clock-cells = <1>;
> @@ -2555,7 +2555,7 @@ larb1: larb@1c019000 {
>   		};
>   
>   		vdosys1: syscon@1c100000 {
> -			compatible = "mediatek,mt8195-mmsys", "syscon";
> +			compatible = "mediatek,mt8195-vdosys1", "syscon";
>   			reg = <0 0x1c100000 0 0x1000>;
>   			#clock-cells = <1>;
>   		};

      parent reply	other threads:[~2023-03-02 11:26 UTC|newest]

Thread overview: 15+ 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 ` [PATCH v1 2/4] arm64: dts: mt8167: Align mmsys node name with dtschema matthias.bgg
2023-02-10  2:42   ` Chen-Yu Tsai
2023-02-10 11:59   ` AngeloGioacchino Del Regno
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 11:59   ` AngeloGioacchino Del Regno
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-10  2:44   ` Chen-Yu Tsai
2023-02-10 11:59   ` AngeloGioacchino Del Regno
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 11:59 ` AngeloGioacchino Del Regno
2023-03-02 11:26 ` Matthias Brugger [this message]

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=1f65671b-7c68-b007-60c8-6c4841febce0@gmail.com \
    --to=matthias.bgg@gmail.com \
    --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@kernel.org \
    --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).