From: Sukrut Bellary <sbellary@baylibre.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Tero Kristo <kristo@kernel.org>,
Kevin Hilman <khilman@baylibre.com>,
Andreas Kemnade <andreas@kemnade.info>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] dt-bindings: clock: ti: Convert to yaml
Date: Wed, 9 Apr 2025 01:23:17 -0700 [thread overview]
Message-ID: <Z/YudZ0c2SBA+NMD@dev-linux> (raw)
In-Reply-To: <20250404-tangible-reindeer-of-penetration-ae9ca3@shite>
On Fri, Apr 04, 2025 at 12:46:28PM +0200, Krzysztof Kozlowski wrote:
> On Thu, Apr 03, 2025 at 06:44:58PM GMT, Sukrut Bellary wrote:
> > +maintainers:
> > + - Tero Kristo <kristo@kernel.org>
> > + - Sukrut Bellary <sbellary@baylibre.com>
> > +
> > +description: |
>
> Do not need '|' unless you need to preserve formatting.
Thanks for the review.
I will fix this.
> > + Every clock on TI SoC belongs to one clockdomain. For specific clocks, the
> > + parent clockdomain has to be controlled when the clock is enabled/disabled.
> > + This binding doesn't define a new clock binding type, it is used to group
> > + the existing clock nodes under hardware hierarchy.
> > +
> > +properties:
> > + compatible:
> > + const: ti,clockdomain
> > +
> > + clocks:
> > + description:
> > + Clocks within this domain
>
> Missing constraints.
I will add it.
> > +
> > +required:
> > + - compatible
> > + - clocks
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > + l3init_clkdm: l3init_clkdm {
>
> Follow DTS coding style. Also drop unused label.
>
> Node names should be generic. See also an explanation and list of
> examples (not exhaustive) in DT specification:
> https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation
Sure, will fix this.
> > + compatible = "ti,clockdomain";
> > + clocks = <&dpll_usb_ck>;
> > + };
> > --
> > 2.34.1
> >
next prev parent reply other threads:[~2025-04-09 8:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 1:44 [PATCH 0/4] dt-bindings: clock: ti: convert to yaml Sukrut Bellary
2025-04-04 1:44 ` [PATCH 1/4] dt-bindings: clock: ti: Convert " Sukrut Bellary
2025-04-04 10:44 ` Krzysztof Kozlowski
2025-04-05 19:55 ` Andreas Kemnade
2025-04-09 8:11 ` Sukrut Bellary
2025-04-09 7:46 ` Sukrut Bellary
2025-04-04 15:19 ` Rob Herring
2025-04-09 8:21 ` Sukrut Bellary
2025-04-04 1:44 ` [PATCH 2/4] " Sukrut Bellary
2025-04-04 5:51 ` kernel test robot
2025-04-04 10:46 ` Krzysztof Kozlowski
2025-04-09 8:23 ` Sukrut Bellary [this message]
2025-04-04 14:56 ` Rob Herring (Arm)
2025-04-09 8:35 ` Sukrut Bellary
2025-04-09 9:10 ` Andreas Kemnade
2025-04-10 17:49 ` Sukrut Bellary
2025-04-04 1:44 ` [PATCH 3/4] dt-bindings: clock: ti: Convert fixed-factor-clock " Sukrut Bellary
2025-04-04 19:40 ` Rob Herring
2025-04-09 8:38 ` Sukrut Bellary
2025-04-04 1:45 ` [PATCH 4/4] dt-bindings: clock: ti: add ti,autoidle.yaml reference Sukrut Bellary
2025-04-04 19:42 ` Rob Herring
2025-04-09 8:40 ` Sukrut Bellary
2025-04-05 19:49 ` Andreas Kemnade
2025-04-09 8:43 ` Sukrut Bellary
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=Z/YudZ0c2SBA+NMD@dev-linux \
--to=sbellary@baylibre.com \
--cc=andreas@kemnade.info \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@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).