From: Andreas Kemnade <andreas@kemnade.info>
To: Stephen Boyd <sboyd@kernel.org>,
linux-clk@vger.kernel.org, Andreas Kemnade <andreas@kemnade.info>,
Tony Lindgren <tony@atomide.com>, Tero Kristo <kristo@kernel.org>,
linux-kernel@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-omap@vger.kernel.org, Rob Herring <robh@kernel.org>
Subject: [PATCH v2 0/2] dt-bindings: clocks: ti: Next round of conversion
Date: Sun, 5 Jan 2025 18:08:52 +0100 [thread overview]
Message-ID: <20250105170854.408875-1-andreas@kemnade.info> (raw)
Convert more TI clock bindings to json-schema.
Changes in v2:
- comment about design pattern
- fix example to use an existing compatible
- some formatting
Andreas Kemnade (2):
dt-bindings: clock: ti: Convert gate.txt to json-schema
dt-bindings: clock: ti: Convert composite.txt to json-schema
.../bindings/clock/ti/composite.txt | 55 --------
.../devicetree/bindings/clock/ti/gate.txt | 105 ---------------
.../bindings/clock/ti/ti,composite-clock.yaml | 82 ++++++++++++
.../bindings/clock/ti/ti,gate-clock.yaml | 125 ++++++++++++++++++
4 files changed, 207 insertions(+), 160 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/clock/ti/composite.txt
delete mode 100644 Documentation/devicetree/bindings/clock/ti/gate.txt
create mode 100644 Documentation/devicetree/bindings/clock/ti/ti,composite-clock.yaml
create mode 100644 Documentation/devicetree/bindings/clock/ti/ti,gate-clock.yaml
--
2.39.5
next reply other threads:[~2025-01-05 17:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-05 17:08 Andreas Kemnade [this message]
2025-01-05 17:08 ` [PATCH v2 1/2] dt-bindings: clock: ti: Convert gate.txt to json-schema Andreas Kemnade
2025-01-06 21:17 ` Rob Herring (Arm)
2025-01-06 23:45 ` Stephen Boyd
2025-01-05 17:08 ` [PATCH v2 2/2] dt-bindings: clock: ti: Convert composite.txt " Andreas Kemnade
2025-01-06 21:17 ` Rob Herring (Arm)
2025-01-06 23:46 ` Stephen Boyd
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=20250105170854.408875-1-andreas@kemnade.info \
--to=andreas@kemnade.info \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=tony@atomide.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