public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Changhuang Liang <changhuang.liang@starfivetech.com>
Cc: 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: Wed, 19 Apr 2023 19:29:48 +0100	[thread overview]
Message-ID: <20230419-labored-camper-644d51a7ca96@spud> (raw)
In-Reply-To: <20230419035646.43702-2-changhuang.liang@starfivetech.com>


[-- Attachment #1.1: Type: text/plain, Size: 3498 bytes --]

Hey Changhuang, DT/PHY folks,

On Tue, Apr 18, 2023 at 08:56:41PM -0700, Changhuang Liang wrote:
> Add AON PMU for StarFive JH7110 SoC, it can be used to turn on/off DPHY
> rx/tx power switch, and it don't need the properties of reg and
> interrupts.

Putting this here since the DT guys are more likely to see it this way..
Given how the implementation of the code driving this new
power-controller and the code driving the existing one are rather
different (you've basically re-written the entire driver in this series),
should the dphy driver implement its own power-controller?

I know originally Changuang had tried something along those lines:
https://lore.kernel.org/linux-riscv/5dc4ddc2-9d15-ebb2-38bc-8a544ca67e0d@starfivetech.com/

I see that that was shut down pretty much, partly due to the
non-standard property, hence this series adding the dphy power domain to
the existing driver.

If it was done by looking up the pmu with a
of_find_compatible_node(NULL, "power-controller", "starfive,jh7110-aon-pmu")
type thing, would that make sense? Although, maybe that is not a
question for you, and this series may actually have been better entirely
bundled with the dphy series so the whole thing can be reviewed as a
unit. I've added 

IOW, don't change this patch, or the dts patch, but move all of the
code back into the phy driver..

Sorry for not asking this sooner Changhuang,
Conor.

(hopefully this didn't get sent twice, mutt complained of a bad email
addr during sending the first time)

> 
> Signed-off-by: Changhuang Liang <changhuang.liang@starfivetech.com>
> ---
>  .../bindings/power/starfive,jh7110-pmu.yaml       | 15 +++++++++++++--
>  include/dt-bindings/power/starfive,jh7110-pmu.h   |  3 +++
>  2 files changed, 16 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/power/starfive,jh7110-pmu.yaml b/Documentation/devicetree/bindings/power/starfive,jh7110-pmu.yaml
> index 98eb8b4110e7..c50507c38e14 100644
> --- a/Documentation/devicetree/bindings/power/starfive,jh7110-pmu.yaml
> +++ b/Documentation/devicetree/bindings/power/starfive,jh7110-pmu.yaml
> @@ -8,6 +8,7 @@ title: StarFive JH7110 Power Management Unit
>  
>  maintainers:
>    - Walker Chen <walker.chen@starfivetech.com>
> +  - Changhuang Liang <changhuang.liang@starfivetech.com>
>  
>  description: |
>    StarFive JH7110 SoC includes support for multiple power domains which can be
> @@ -17,6 +18,7 @@ properties:
>    compatible:
>      enum:
>        - starfive,jh7110-pmu
> +      - starfive,jh7110-aon-pmu
>  
>    reg:
>      maxItems: 1
> @@ -29,10 +31,19 @@ properties:
>  
>  required:
>    - compatible
> -  - reg
> -  - interrupts
>    - "#power-domain-cells"
>  
> +allOf:
> +  - if:
> +      properties:
> +        compatible:
> +          contains:
> +            const: starfive,jh7110-pmu
> +    then:
> +      required:
> +        - reg
> +        - interrupts
> +
>  additionalProperties: false
>  
>  examples:
> diff --git a/include/dt-bindings/power/starfive,jh7110-pmu.h b/include/dt-bindings/power/starfive,jh7110-pmu.h
> index 132bfe401fc8..0bfd6700c144 100644
> --- a/include/dt-bindings/power/starfive,jh7110-pmu.h
> +++ b/include/dt-bindings/power/starfive,jh7110-pmu.h
> @@ -14,4 +14,7 @@
>  #define JH7110_PD_ISP		5
>  #define JH7110_PD_VENC		6
>  
> +#define JH7110_PD_DPHY_TX	0
> +#define JH7110_PD_DPHY_RX	1
> +
>  #endif
> -- 
> 2.25.1
> 

[-- 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

  reply	other threads:[~2023-04-19 18:30 UTC|newest]

Thread overview: 52+ 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 ` [RESEND v2 1/6] dt-bindings: power: " Changhuang Liang
2023-04-19 18:29   ` Conor Dooley [this message]
2023-04-20  7:00     ` Changhuang Liang
2023-04-24 16:52       ` Conor Dooley
2023-04-25  3:41         ` Changhuang Liang
2023-04-25  6:59           ` Conor Dooley
2023-04-25  7:57             ` Changhuang Liang
2023-04-25  8:19               ` Krzysztof Kozlowski
2023-04-25  9:18                 ` Changhuang Liang
2023-04-25  9:35                   ` Conor Dooley
2023-04-25 12:26                     ` Changhuang Liang
2023-04-25 16:56                       ` Conor Dooley
2023-04-26  2:11                         ` Changhuang Liang
2023-05-04  1:34                         ` Changhuang Liang
2023-05-04  6:13                           ` Krzysztof Kozlowski
2023-05-04  6:53                             ` Changhuang Liang
2023-05-04  7:04                               ` Krzysztof Kozlowski
2023-05-04  7:20                                 ` Changhuang Liang
2023-05-04  7:26                                   ` Krzysztof Kozlowski
2023-05-04  8:43                                     ` Changhuang Liang
2023-05-04  9:36                                       ` Krzysztof Kozlowski
2023-05-04  9:48                                         ` Changhuang Liang
2023-05-04  9:57                                           ` Conor Dooley
2023-05-05  1:29                                             ` Changhuang Liang
2023-05-05 12:38                                               ` Conor Dooley
2023-05-06  1:45                                                 ` Changhuang Liang
2023-05-06  6:31                                                   ` Krzysztof Kozlowski
2023-05-06  7:00                                                     ` Changhuang Liang
2023-05-06 10:17                                                   ` Conor Dooley
2023-05-06 12:26                                                     ` Changhuang Liang
2023-05-06 12:29                                                       ` Conor Dooley
2023-05-07  4:00                                                         ` Changhuang Liang
2023-04-19 19:46   ` Krzysztof Kozlowski
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 ` [RESEND v2 3/6] soc: starfive: Modify ioremap to regmap Changhuang Liang
2023-04-19 17:29   ` Conor Dooley
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 17:47   ` Conor Dooley
2023-04-21  3:27     ` Changhuang Liang
2023-04-21  6:57       ` Conor Dooley
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-05-06 13:58   ` Shengyu Qu
2023-05-06 14:05     ` Conor Dooley
2023-05-06 14:07       ` Shengyu Qu
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  6:23 ` [RESEND v2 0/6] Add JH7110 AON PMU support Conor Dooley
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=20230419-labored-camper-644d51a7ca96@spud \
    --to=conor@kernel.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=changhuang.liang@starfivetech.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hal.feng@starfivetech.com \
    --cc=kernel@esmil.dk \
    --cc=krzysztof.kozlowski+dt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox