From: Andreas Kemnade <andreas@kemnade.info>
To: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Roger Quadros <rogerq@kernel.org>,
linux-omap@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Stephen Boyd <sboyd@kernel.org>, Tero Kristo <kristo@kernel.org>,
Kevin Hilman <khilman@baylibre.com>,
Michael Turquette <mturquette@baylibre.com>,
Conor Dooley <conor+dt@kernel.org>, Rob Herring <robh@kernel.org>,
linux-clk@vger.kernel.org, Andreas Kemnade <andreas@kemnade.info>
Subject: [PATCH v3 0/2] dt-bindings: clock: ti: convert to yaml
Date: Fri, 18 Oct 2024 10:53:45 +0200 [thread overview]
Message-ID: <20241018085347.95071-1-andreas@kemnade.info> (raw)
Convert some clock schemas to yaml. These are one of the most used non-yaml
compatibles.
All can appear under a ti,clksel or without a ti,clksel.
I plan to convert the clock things from time to time.
So enforcing certain compatibles below ti,clksel is not there yet.
Open question: I set license to GPL-2 only because the .txt bindings the
yaml binding was derived from were
GPL-2. I personally have no problem with dual-licensing the binding.
No idea about the legal side wether that is possible or who must agree.
Changes in v3:
- adding more constraints and types
- strip labels from example
- fix references to divider.txt
Changes in v2:
- added conversion of divider
- require reg now, makes sense after
https://lore.kernel.org/linux-omap/20240213105730.5287-1-tony@atomide.com/
- clean up of examples
- improvement of documentation
v1 is at https://lore.kernel.org/linux-omap/20231127202359.145778-1-andreas@kemnade.info/
Andreas Kemnade (2):
dt-bindings: clock: ti: Convert interface.txt to json-schema
dt-bindings: clock: ti: Convert divider.txt to json-schema
.../bindings/clock/ti/composite.txt | 2 +-
.../devicetree/bindings/clock/ti/divider.txt | 115 -----------
.../bindings/clock/ti/interface.txt | 55 -----
.../bindings/clock/ti/ti,divider-clock.yaml | 193 ++++++++++++++++++
.../bindings/clock/ti/ti,interface-clock.yaml | 71 +++++++
5 files changed, 265 insertions(+), 171 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/clock/ti/divider.txt
delete mode 100644 Documentation/devicetree/bindings/clock/ti/interface.txt
create mode 100644 Documentation/devicetree/bindings/clock/ti/ti,divider-clock.yaml
create mode 100644 Documentation/devicetree/bindings/clock/ti/ti,interface-clock.yaml
--
2.39.5
next reply other threads:[~2024-10-18 8:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 8:53 Andreas Kemnade [this message]
2024-10-18 8:53 ` [PATCH v3 1/2] dt-bindings: clock: ti: Convert interface.txt to json-schema Andreas Kemnade
2024-10-19 5:46 ` Stephen Boyd
2024-10-18 8:53 ` [PATCH v3 2/2] dt-bindings: clock: ti: Convert divider.txt " Andreas Kemnade
2024-10-18 13:41 ` Rob Herring (Arm)
2024-10-19 5: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=20241018085347.95071-1-andreas@kemnade.info \
--to=andreas@kemnade.info \
--cc=aaro.koskinen@iki.fi \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--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=rogerq@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;
as well as URLs for NNTP newsgroup(s).