From: Conor Dooley <conor@kernel.org>
To: Changhuang Liang <changhuang.liang@starfivetech.com>
Cc: Conor Dooley <conor.dooley@microchip.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Emil Renner Berthing <kernel@esmil.dk>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Walker Chen <walker.chen@starfivetech.com>,
Hal Feng <hal.feng@starfivetech.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, vkoul@kernel.org,
linux-phy@lists.infradead.org
Subject: Re: [RESEND v2 1/6] dt-bindings: power: Add JH7110 AON PMU support
Date: Sat, 6 May 2023 11:17:03 +0100 [thread overview]
Message-ID: <20230506-dating-twiddling-b364de21ed2b@spud> (raw)
In-Reply-To: <ba6a1a47-d3b1-ee16-4785-f5c61d593127@starfivetech.com>
[-- Attachment #1.1: Type: text/plain, Size: 1736 bytes --]
On Sat, May 06, 2023 at 09:45:07AM +0800, Changhuang Liang wrote:
>
>
> On 2023/5/5 20:38, Conor Dooley wrote:
> > On Fri, May 05, 2023 at 09:29:15AM +0800, Changhuang Liang wrote:
> >
> >> But if keep this "starfive,jh7110-aon-syscon" compatible. Which .yaml match to
> >> it? Use this series dt-bindings or syscon series dt-bindings.
> >
> > There is no syscon series anymore, it's part of the PLL series now:
> > https://lore.kernel.org/linux-clk/20230414024157.53203-1-xingyu.wu@starfivetech.com/
> >
> > I don't really care what you, Walker & Xingyu decide to do, but add the
> > binding in one series in a complete form. It's far less confusing to
> > have only have one version of the binding on the go at once.
> >
>
> Due to the current aon pmu needs to be adjusted, it affects the syscon in PLL series.
> So It's inevitable to change syscon in PLL series.
>
> My current idea is PLL series don't add the aon_syscon node. I will add it in my
> aon pmu series in next version
That's fine. Rob was happy with the clock related parts, which was the
original source of confusion there.
> like this:
>
> aon_syscon: syscon@17010000 {
> compatible = "starfive,jh7110-aon-pmu", "syscon";
The syscon does a bunch of things of which one is a pmu. I don't see a
reason to name this other than "starfive,jh100-aon-syscon".
> reg = <0x0 0x17010000 0x0 0x1000>;
> #power-domain-cells = <1>;
> };
>
> In my opinion, the first we add "starfive,jh7110-aon-syscon" because "syscon" can
> not appear alone in the compatible. If we have "starfive,jh7110-aon-pmu", this
> "starfive,jh7110-aon-syscon" is not a must-be need.
>
> Do you agree with doing so.
>
> Thanks,
> Changhuang
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 112 bytes --]
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org>
To: Changhuang Liang <changhuang.liang@starfivetech.com>
Cc: Conor Dooley <conor.dooley@microchip.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Emil Renner Berthing <kernel@esmil.dk>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Walker Chen <walker.chen@starfivetech.com>,
Hal Feng <hal.feng@starfivetech.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, vkoul@kernel.org,
linux-phy@lists.infradead.org
Subject: Re: [RESEND v2 1/6] dt-bindings: power: Add JH7110 AON PMU support
Date: Sat, 6 May 2023 11:17:03 +0100 [thread overview]
Message-ID: <20230506-dating-twiddling-b364de21ed2b@spud> (raw)
In-Reply-To: <ba6a1a47-d3b1-ee16-4785-f5c61d593127@starfivetech.com>
[-- Attachment #1.1: Type: text/plain, Size: 1736 bytes --]
On Sat, May 06, 2023 at 09:45:07AM +0800, Changhuang Liang wrote:
>
>
> On 2023/5/5 20:38, Conor Dooley wrote:
> > On Fri, May 05, 2023 at 09:29:15AM +0800, Changhuang Liang wrote:
> >
> >> But if keep this "starfive,jh7110-aon-syscon" compatible. Which .yaml match to
> >> it? Use this series dt-bindings or syscon series dt-bindings.
> >
> > There is no syscon series anymore, it's part of the PLL series now:
> > https://lore.kernel.org/linux-clk/20230414024157.53203-1-xingyu.wu@starfivetech.com/
> >
> > I don't really care what you, Walker & Xingyu decide to do, but add the
> > binding in one series in a complete form. It's far less confusing to
> > have only have one version of the binding on the go at once.
> >
>
> Due to the current aon pmu needs to be adjusted, it affects the syscon in PLL series.
> So It's inevitable to change syscon in PLL series.
>
> My current idea is PLL series don't add the aon_syscon node. I will add it in my
> aon pmu series in next version
That's fine. Rob was happy with the clock related parts, which was the
original source of confusion there.
> like this:
>
> aon_syscon: syscon@17010000 {
> compatible = "starfive,jh7110-aon-pmu", "syscon";
The syscon does a bunch of things of which one is a pmu. I don't see a
reason to name this other than "starfive,jh100-aon-syscon".
> reg = <0x0 0x17010000 0x0 0x1000>;
> #power-domain-cells = <1>;
> };
>
> In my opinion, the first we add "starfive,jh7110-aon-syscon" because "syscon" can
> not appear alone in the compatible. If we have "starfive,jh7110-aon-pmu", this
> "starfive,jh7110-aon-syscon" is not a must-be need.
>
> Do you agree with doing so.
>
> Thanks,
> Changhuang
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org>
To: Changhuang Liang <changhuang.liang@starfivetech.com>
Cc: Conor Dooley <conor.dooley@microchip.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Emil Renner Berthing <kernel@esmil.dk>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Walker Chen <walker.chen@starfivetech.com>,
Hal Feng <hal.feng@starfivetech.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, vkoul@kernel.org,
linux-phy@lists.infradead.org
Subject: Re: [RESEND v2 1/6] dt-bindings: power: Add JH7110 AON PMU support
Date: Sat, 6 May 2023 11:17:03 +0100 [thread overview]
Message-ID: <20230506-dating-twiddling-b364de21ed2b@spud> (raw)
In-Reply-To: <ba6a1a47-d3b1-ee16-4785-f5c61d593127@starfivetech.com>
[-- Attachment #1: Type: text/plain, Size: 1736 bytes --]
On Sat, May 06, 2023 at 09:45:07AM +0800, Changhuang Liang wrote:
>
>
> On 2023/5/5 20:38, Conor Dooley wrote:
> > On Fri, May 05, 2023 at 09:29:15AM +0800, Changhuang Liang wrote:
> >
> >> But if keep this "starfive,jh7110-aon-syscon" compatible. Which .yaml match to
> >> it? Use this series dt-bindings or syscon series dt-bindings.
> >
> > There is no syscon series anymore, it's part of the PLL series now:
> > https://lore.kernel.org/linux-clk/20230414024157.53203-1-xingyu.wu@starfivetech.com/
> >
> > I don't really care what you, Walker & Xingyu decide to do, but add the
> > binding in one series in a complete form. It's far less confusing to
> > have only have one version of the binding on the go at once.
> >
>
> Due to the current aon pmu needs to be adjusted, it affects the syscon in PLL series.
> So It's inevitable to change syscon in PLL series.
>
> My current idea is PLL series don't add the aon_syscon node. I will add it in my
> aon pmu series in next version
That's fine. Rob was happy with the clock related parts, which was the
original source of confusion there.
> like this:
>
> aon_syscon: syscon@17010000 {
> compatible = "starfive,jh7110-aon-pmu", "syscon";
The syscon does a bunch of things of which one is a pmu. I don't see a
reason to name this other than "starfive,jh100-aon-syscon".
> reg = <0x0 0x17010000 0x0 0x1000>;
> #power-domain-cells = <1>;
> };
>
> In my opinion, the first we add "starfive,jh7110-aon-syscon" because "syscon" can
> not appear alone in the compatible. If we have "starfive,jh7110-aon-pmu", this
> "starfive,jh7110-aon-syscon" is not a must-be need.
>
> Do you agree with doing so.
>
> Thanks,
> Changhuang
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-05-06 10:17 UTC|newest]
Thread overview: 135+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 3:56 [RESEND v2 0/6] Add JH7110 AON PMU support Changhuang Liang
2023-04-19 3:56 ` Changhuang Liang
2023-04-19 3:56 ` [RESEND v2 1/6] dt-bindings: power: " Changhuang Liang
2023-04-19 3:56 ` Changhuang Liang
2023-04-19 18:29 ` Conor Dooley
2023-04-19 18:29 ` Conor Dooley
2023-04-19 18:29 ` Conor Dooley
2023-04-20 7:00 ` Changhuang Liang
2023-04-20 7:00 ` Changhuang Liang
2023-04-20 7:00 ` Changhuang Liang
2023-04-24 16:52 ` Conor Dooley
2023-04-24 16:52 ` Conor Dooley
2023-04-24 16:52 ` Conor Dooley
2023-04-25 3:41 ` Changhuang Liang
2023-04-25 3:41 ` Changhuang Liang
2023-04-25 3:41 ` Changhuang Liang
2023-04-25 6:59 ` Conor Dooley
2023-04-25 6:59 ` Conor Dooley
2023-04-25 6:59 ` Conor Dooley
2023-04-25 7:57 ` Changhuang Liang
2023-04-25 7:57 ` Changhuang Liang
2023-04-25 7:57 ` Changhuang Liang
2023-04-25 8:19 ` Krzysztof Kozlowski
2023-04-25 8:19 ` Krzysztof Kozlowski
2023-04-25 8:19 ` Krzysztof Kozlowski
2023-04-25 9:18 ` Changhuang Liang
2023-04-25 9:18 ` Changhuang Liang
2023-04-25 9:18 ` Changhuang Liang
2023-04-25 9:35 ` Conor Dooley
2023-04-25 9:35 ` Conor Dooley
2023-04-25 9:35 ` Conor Dooley
2023-04-25 12:26 ` Changhuang Liang
2023-04-25 12:26 ` Changhuang Liang
2023-04-25 12:26 ` Changhuang Liang
2023-04-25 16:56 ` Conor Dooley
2023-04-25 16:56 ` Conor Dooley
2023-04-25 16:56 ` Conor Dooley
2023-04-26 2:11 ` Changhuang Liang
2023-04-26 2:11 ` Changhuang Liang
2023-04-26 2:11 ` Changhuang Liang
2023-05-04 1:34 ` Changhuang Liang
2023-05-04 1:34 ` Changhuang Liang
2023-05-04 1:34 ` Changhuang Liang
2023-05-04 6:13 ` Krzysztof Kozlowski
2023-05-04 6:13 ` Krzysztof Kozlowski
2023-05-04 6:13 ` Krzysztof Kozlowski
2023-05-04 6:53 ` Changhuang Liang
2023-05-04 6:53 ` Changhuang Liang
2023-05-04 6:53 ` Changhuang Liang
2023-05-04 7:04 ` Krzysztof Kozlowski
2023-05-04 7:04 ` Krzysztof Kozlowski
2023-05-04 7:04 ` Krzysztof Kozlowski
2023-05-04 7:20 ` Changhuang Liang
2023-05-04 7:20 ` Changhuang Liang
2023-05-04 7:20 ` Changhuang Liang
2023-05-04 7:26 ` Krzysztof Kozlowski
2023-05-04 7:26 ` Krzysztof Kozlowski
2023-05-04 7:26 ` Krzysztof Kozlowski
2023-05-04 8:43 ` Changhuang Liang
2023-05-04 8:43 ` Changhuang Liang
2023-05-04 8:43 ` Changhuang Liang
2023-05-04 9:36 ` Krzysztof Kozlowski
2023-05-04 9:36 ` Krzysztof Kozlowski
2023-05-04 9:36 ` Krzysztof Kozlowski
2023-05-04 9:48 ` Changhuang Liang
2023-05-04 9:48 ` Changhuang Liang
2023-05-04 9:48 ` Changhuang Liang
2023-05-04 9:57 ` Conor Dooley
2023-05-04 9:57 ` Conor Dooley
2023-05-04 9:57 ` Conor Dooley
2023-05-05 1:29 ` Changhuang Liang
2023-05-05 1:29 ` Changhuang Liang
2023-05-05 1:29 ` Changhuang Liang
2023-05-05 12:38 ` Conor Dooley
2023-05-05 12:38 ` Conor Dooley
2023-05-05 12:38 ` Conor Dooley
2023-05-06 1:45 ` Changhuang Liang
2023-05-06 1:45 ` Changhuang Liang
2023-05-06 1:45 ` Changhuang Liang
2023-05-06 6:31 ` Krzysztof Kozlowski
2023-05-06 6:31 ` Krzysztof Kozlowski
2023-05-06 6:31 ` Krzysztof Kozlowski
2023-05-06 7:00 ` Changhuang Liang
2023-05-06 7:00 ` Changhuang Liang
2023-05-06 7:00 ` Changhuang Liang
2023-05-06 10:17 ` Conor Dooley [this message]
2023-05-06 10:17 ` Conor Dooley
2023-05-06 10:17 ` Conor Dooley
2023-05-06 12:26 ` Changhuang Liang
2023-05-06 12:26 ` Changhuang Liang
2023-05-06 12:26 ` Changhuang Liang
2023-05-06 12:29 ` Conor Dooley
2023-05-06 12:29 ` Conor Dooley
2023-05-06 12:29 ` Conor Dooley
2023-05-07 4:00 ` Changhuang Liang
2023-05-07 4:00 ` Changhuang Liang
2023-05-07 4:00 ` Changhuang Liang
2023-04-19 19:46 ` Krzysztof Kozlowski
2023-04-19 19:46 ` Krzysztof Kozlowski
2023-04-20 7:40 ` Changhuang Liang
2023-04-20 7:40 ` Changhuang Liang
2023-04-19 3:56 ` [RESEND v2 2/6] soc: starfive: Replace SOC_STARFIVE with ARCH_STARFIVE Changhuang Liang
2023-04-19 3:56 ` Changhuang Liang
2023-04-19 3:56 ` [RESEND v2 3/6] soc: starfive: Modify ioremap to regmap Changhuang Liang
2023-04-19 3:56 ` Changhuang Liang
2023-04-19 17:29 ` Conor Dooley
2023-04-19 17:29 ` Conor Dooley
2023-04-20 6:03 ` Changhuang Liang
2023-04-20 6:03 ` Changhuang Liang
2023-04-19 3:56 ` [RESEND v2 4/6] soc: starfive: Extract JH7110 pmu private operations Changhuang Liang
2023-04-19 3:56 ` Changhuang Liang
2023-04-19 17:47 ` Conor Dooley
2023-04-19 17:47 ` Conor Dooley
2023-04-21 3:27 ` Changhuang Liang
2023-04-21 3:27 ` Changhuang Liang
2023-04-21 6:57 ` Conor Dooley
2023-04-21 6:57 ` Conor Dooley
2023-04-21 7:47 ` Changhuang Liang
2023-04-21 7:47 ` Changhuang Liang
2023-04-19 3:56 ` [RESEND v2 5/6] soc: starfive: Add JH7110 AON PMU support Changhuang Liang
2023-04-19 3:56 ` Changhuang Liang
2023-05-06 13:58 ` Shengyu Qu
2023-05-06 13:58 ` Shengyu Qu
2023-05-06 14:05 ` Conor Dooley
2023-05-06 14:05 ` Conor Dooley
2023-05-06 14:07 ` Shengyu Qu
2023-05-06 14:07 ` Shengyu Qu
2023-05-06 14:12 ` Conor Dooley
2023-05-06 14:12 ` Conor Dooley
2023-04-19 3:56 ` [RESEND v2 6/6] riscv: dts: starfive: jh7110: Add AON PMU node Changhuang Liang
2023-04-19 3:56 ` Changhuang Liang
2023-04-19 6:23 ` [RESEND v2 0/6] Add JH7110 AON PMU support Conor Dooley
2023-04-19 6:23 ` Conor Dooley
2023-04-19 6:57 ` Changhuang Liang
2023-04-19 6:57 ` Changhuang Liang
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=20230506-dating-twiddling-b364de21ed2b@spud \
--to=conor@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=changhuang.liang@starfivetech.com \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=hal.feng@starfivetech.com \
--cc=kernel@esmil.dk \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=vkoul@kernel.org \
--cc=walker.chen@starfivetech.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.