From: Stephen Boyd <sboyd@kernel.org>
To: Andreas Kemnade <andreas@kemnade.info>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh@kernel.org>, Tero Kristo <kristo@kernel.org>,
Tony Lindgren <tony@atomide.com>,
akemnade@kernel.org, devicetree@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: clock: ti: Convert gate.txt to json-schema
Date: Mon, 30 Dec 2024 16:26:57 -0800 [thread overview]
Message-ID: <bd1f8992ac2cc60b3192ea93402ed186.sboyd@kernel.org> (raw)
In-Reply-To: <20241229135351.5014-2-akemnade@kernel.org>
Quoting akemnade@kernel.org (2024-12-29 05:53:50)
> From: Andreas Kemnade <andreas@kemnade.info>
>
> Convert the OMAP gate clock device tree binding to json-schema.
> Specify the creator of the original binding as a maintainer.
> Choose GPL-only license because original binding was also GPL.
> Clean up the examples during conversion to meet modern standards and
> remove examples with no additional value.
> Due to usage in code and existing devicetree binding, add the
> ti,set-rate-parent property.
Can we somehow mark these bindings as "undesirable"? We don't want new
bindings to be written that use one node per clock. At the least we
should put that into the description.
next prev parent reply other threads:[~2024-12-31 0:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-29 13:53 [PATCH 0/2] dt-bindings: clocks: ti: Next round of conversion akemnade
2024-12-29 13:53 ` [PATCH 1/2] dt-bindings: clock: ti: Convert gate.txt to json-schema akemnade
2024-12-31 0:26 ` Stephen Boyd [this message]
2025-01-01 21:07 ` Andreas Kemnade
2024-12-29 13:53 ` [PATCH 2/2] dt-bindings: clock: ti: Convert composite.txt " akemnade
2024-12-29 15:30 ` Rob Herring (Arm)
2024-12-30 19:46 ` Rob Herring
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=bd1f8992ac2cc60b3192ea93402ed186.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=akemnade@kernel.org \
--cc=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=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).