All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Chunyan Zhang <zhang.lyra@gmail.com>
Cc: Stephen Boyd <sboyd@kernel.org>,
	linux-clk <linux-clk@vger.kernel.org>,
	DTML <devicetree@vger.kernel.org>,
	Baolin Wang <baolin.wang7@gmail.com>,
	Orson Zhai <orsonzhai@gmail.com>,
	Chunyan Zhang <chunyan.zhang@unisoc.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/4] dt-bindings: clk: sprd: Add bindings for ums512 clock controller
Date: Mon, 20 Sep 2021 07:42:30 -0500	[thread overview]
Message-ID: <CAL_JsqKmznCOk+qHFccnG1b5xuoNHY2vmqyv=WAjB9d=0AW70Q@mail.gmail.com> (raw)
In-Reply-To: <CAAfSe-vYMUb8wGUJG7Fzehjkj8gAq1QOdgCdsTvcNyMuVeEW8g@mail.gmail.com>

On Fri, Sep 17, 2021 at 3:41 AM Chunyan Zhang <zhang.lyra@gmail.com> wrote:
>
> On Thu, 16 Sept 2021 at 22:29, Rob Herring <robh@kernel.org> wrote:
> >
> > On Thu, Sep 16, 2021 at 04:47:12PM +0800, Chunyan Zhang wrote:
> > > From: Chunyan Zhang <chunyan.zhang@unisoc.com>
> > >
> > > Add a new bindings to describe ums512 clock compatible strings.
> > >
> > > Signed-off-by: Chunyan Zhang <chunyan.zhang@unisoc.com>
> > > ---
> > >  .../bindings/clock/sprd,ums512-clk.yaml       | 106 ++++++++++++++++++
> > >  1 file changed, 106 insertions(+)
> > >  create mode 100644 Documentation/devicetree/bindings/clock/sprd,ums512-clk.yaml
> > >
> > > diff --git a/Documentation/devicetree/bindings/clock/sprd,ums512-clk.yaml b/Documentation/devicetree/bindings/clock/sprd,ums512-clk.yaml
> > > new file mode 100644
> > > index 000000000000..be3c37180279
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/clock/sprd,ums512-clk.yaml
> > > @@ -0,0 +1,106 @@
> > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > > +# Copyright 2019-2021 Unisoc Inc.
> > > +%YAML 1.2
> > > +---
> > > +$id: "http://devicetree.org/schemas/clock/sprd,ums512-clk.yaml#"
> > > +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> > > +
> > > +title: UMS512 Clock Control Unit Device Tree Bindings
> > > +
> > > +maintainers:
> > > +  - Orson Zhai <orsonzhai@gmail.com>
> > > +  - Baolin Wang <baolin.wang7@gmail.com>
> > > +  - Chunyan Zhang <zhang.lyra@gmail.com>
> > > +
> > > +properties:
> > > +  "#clock-cells":
> > > +    const: 1
> > > +
> > > +  compatible:
> > > +    enum:
> > > +      - sprd,ums512-apahb-gate
> > > +      - sprd,ums512-ap-clk
> > > +      - sprd,ums512-aonapb-clk
> > > +      - sprd,ums512-pmu-gate
> > > +      - sprd,ums512-g0-pll
> > > +      - sprd,ums512-g2-pll
> > > +      - sprd,ums512-g3-pll
> > > +      - sprd,ums512-gc-pll
> > > +      - sprd,ums512-aon-gate
> > > +      - sprd,ums512-audcpapb-gate
> > > +      - sprd,ums512-audcpahb-gate
> > > +      - sprd,ums512-gpu-clk
> > > +      - sprd,ums512-mm-clk
> > > +      - sprd,ums512-mm-gate-clk
> > > +      - sprd,ums512-apapb-gate
> > > +
> > > +  clocks:
> > > +    minItems: 1
> > > +    maxItems: 4
> > > +    description: |
> > > +      The input parent clock(s) phandle for this clock, only list fixed
> > > +      clocks which are declared in devicetree.
> > > +
> > > +  clock-names:
> > > +    minItems: 1
> > > +    maxItems: 4
> > > +    items:
> > > +      - const: ext-26m
> > > +      - const: ext-32k
> > > +      - const: ext-4m
> > > +      - const: rco-100m
> > > +
> > > +  reg:
> > > +    maxItems: 1
> > > +
> > > +required:
> > > +  - compatible
> > > +  - '#clock-cells'
> > > +
> > > +if:
> > > +  properties:
> > > +    compatible:
> > > +      enum:
> > > +        - sprd,ums512-ap-clk
> > > +        - sprd,ums512-aonapb-clk
> > > +        - sprd,ums512-mm-clk
> > > +then:
> > > +  required:
> > > +    - reg
> > > +
> > > +else:
> > > +  description: |
> > > +    Other UMS512 clock nodes should be the child of a syscon node in
> > > +    which compatible string should be:
> > > +            "sprd,ums512-glbregs", "syscon", "simple-mfd"
> > > +
> > > +    The 'reg' property for the clock node is also required if there is a sub
> > > +    range of registers for the clocks.
> >
> > In which cases is this not true?
>
> Seems not needed, I will remove 'reg' property for this kind of cases.

Wrong direction. Please keep 'reg'. My question is why can't you
always have it? That is the preference.

Rob

  reply	other threads:[~2021-09-20 12:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16  8:47 [PATCH v2 0/4] Add Unisoc's UMS512 clock support Chunyan Zhang
2021-09-16  8:47 ` [PATCH v2 1/4] dt-bindings: mfd: sprd: Add bindings for ums512 global registers Chunyan Zhang
2021-09-16 12:21   ` Rob Herring
2021-09-16 13:03     ` Rob Herring
2021-09-16 13:08   ` Rob Herring
2021-09-16  8:47 ` [PATCH v2 2/4] dt-bindings: clk: sprd: Add bindings for ums512 clock controller Chunyan Zhang
2021-09-16 12:21   ` Rob Herring
2021-09-16 14:29   ` Rob Herring
2021-09-17  8:40     ` Chunyan Zhang
2021-09-20 12:42       ` Rob Herring [this message]
2021-09-22  3:32         ` Chunyan Zhang
2021-09-22 20:35           ` Rob Herring
2021-09-16  8:47 ` [PATCH v2 3/4] clk: sprd: Add dt-bindings include file for UMS512 Chunyan Zhang
2021-09-16  8:47 ` [PATCH v2 4/4] clk: sprd: Add Unisoc's UMS512 clock driver Chunyan Zhang

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='CAL_JsqKmznCOk+qHFccnG1b5xuoNHY2vmqyv=WAjB9d=0AW70Q@mail.gmail.com' \
    --to=robh@kernel.org \
    --cc=baolin.wang7@gmail.com \
    --cc=chunyan.zhang@unisoc.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=orsonzhai@gmail.com \
    --cc=sboyd@kernel.org \
    --cc=zhang.lyra@gmail.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.