From: Matthias Brugger <matthias.bgg@gmail.com>
To: matthias.bgg@kernel.org, Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org
Cc: Mark Rutland <mark.rutland@arm.com>,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] ARM: dts: mediatek: rename scpsys nodes to power-controller
Date: Mon, 17 Feb 2020 11:10:51 +0100 [thread overview]
Message-ID: <66df71d2-9295-b0ee-1a43-c13d49ebeaa9@gmail.com> (raw)
In-Reply-To: <20200212144145.25407-1-matthias.bgg@kernel.org>
On 12/02/2020 15:41, matthias.bgg@kernel.org wrote:
> From: Matthias Brugger <matthias.bgg@gmail.com>
>
> The nodes with name scpsys actually implement a power-controller.
> Rename the nodes to match the bindings description.
>
> Signed-off-by: Matthias Brugger <matthias.bgg@gmail.com>
For the record, both applied to v5.6-next/dts[32,64]
> ---
>
> arch/arm/boot/dts/mt2701.dtsi | 2 +-
> arch/arm/boot/dts/mt7623.dtsi | 2 +-
> arch/arm/boot/dts/mt7629.dtsi | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm/boot/dts/mt2701.dtsi b/arch/arm/boot/dts/mt2701.dtsi
> index 51e1305c6471..2093b38d6e6d 100644
> --- a/arch/arm/boot/dts/mt2701.dtsi
> +++ b/arch/arm/boot/dts/mt2701.dtsi
> @@ -148,7 +148,7 @@ syscfg_pctl_a: syscfg@10005000 {
> reg = <0 0x10005000 0 0x1000>;
> };
>
> - scpsys: scpsys@10006000 {
> + scpsys: power-controller@10006000 {
> compatible = "mediatek,mt2701-scpsys", "syscon";
> #power-domain-cells = <1>;
> reg = <0 0x10006000 0 0x1000>;
> diff --git a/arch/arm/boot/dts/mt7623.dtsi b/arch/arm/boot/dts/mt7623.dtsi
> index a79f0b6c3429..f76b4a3c34b9 100644
> --- a/arch/arm/boot/dts/mt7623.dtsi
> +++ b/arch/arm/boot/dts/mt7623.dtsi
> @@ -268,7 +268,7 @@ syscfg_pctl_a: syscfg@10005000 {
> reg = <0 0x10005000 0 0x1000>;
> };
>
> - scpsys: scpsys@10006000 {
> + scpsys: power-controller@10006000 {
> compatible = "mediatek,mt7623-scpsys",
> "mediatek,mt2701-scpsys",
> "syscon";
> diff --git a/arch/arm/boot/dts/mt7629.dtsi b/arch/arm/boot/dts/mt7629.dtsi
> index 867b88103b9d..60787632e4a1 100644
> --- a/arch/arm/boot/dts/mt7629.dtsi
> +++ b/arch/arm/boot/dts/mt7629.dtsi
> @@ -90,7 +90,7 @@ pericfg: syscon@10002000 {
> #clock-cells = <1>;
> };
>
> - scpsys: scpsys@10006000 {
> + scpsys: power-controller@10006000 {
> compatible = "mediatek,mt7629-scpsys",
> "mediatek,mt7622-scpsys";
> #power-domain-cells = <1>;
>
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
prev parent reply other threads:[~2020-02-17 10:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 14:41 [PATCH 1/2] ARM: dts: mediatek: rename scpsys nodes to power-controller matthias.bgg
2020-02-12 14:41 ` [PATCH 2/2] arm64: " matthias.bgg
2020-02-17 10:10 ` 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=66df71d2-9295-b0ee-1a43-c13d49ebeaa9@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--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).