From: "Rob Herring (Arm)" <robh@kernel.org>
To: Bhargav Joshi <j.bhargav.u@gmail.com>
Cc: Brian Masney <bmasney@redhat.com>,
simona.toaca@nxp.com, Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
daniel.baluta@gmail.com, goledhruva@gmail.com, m-chawdhry@ti.com,
Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, Stephen Boyd <sboyd@kernel.org>,
Tero Kristo <kristo@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3] dt-bindings: clock: ti,clockdomain: Convert to DT schema
Date: Tue, 21 Jul 2026 08:22:47 -0500 [thread overview]
Message-ID: <178464016699.3250705.12302467353770093561.robh@kernel.org> (raw)
In-Reply-To: <20260717-ti-clockdomain-v3-1-3c263af4e9fb@gmail.com>
On Fri, 17 Jul 2026 03:15:42 +0530, Bhargav Joshi wrote:
> Convert TI clockdomain to yaml DT schema. Drop '#clock-cells' from the
> required list as this binding doesn't define a new clock binding type,
> it is used to group existing clock nodes under hardware hierarchy. Most
> existing dts omit '#clock-cells'.
>
> Update the reference to the old legacy text binding in the description
> of bindings/clock/ti/ti,gate-clock.yaml to point to the new YAML file.
>
> Signed-off-by: Bhargav Joshi <j.bhargav.u@gmail.com>
> ---
> Changes in v3:
> - set limits for clock-output-names and clocks properties
> - Link to v2: https://lore.kernel.org/r/20260622-ti-clockdomain-v2-1-434dbe0789e2@gmail.com
>
> Changes in v2:
> - updating the stale reference to the legacy .txt file inside
> bindings/clock/ti/ti,gate-clock.yaml to fix make refcheckdocs error
> - Link to v1: https://lore.kernel.org/r/20260621-ti-clockdomain-v1-1-e99a56af98ea@gmail.com
> ---
> .../devicetree/bindings/clock/ti/clockdomain.txt | 25 ------------
> .../bindings/clock/ti/ti,clockdomain.yaml | 44 ++++++++++++++++++++++
> .../bindings/clock/ti/ti,gate-clock.yaml | 2 +-
> 3 files changed, 45 insertions(+), 26 deletions(-)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
prev parent reply other threads:[~2026-07-21 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 21:45 Bhargav Joshi
2026-07-21 13:22 ` Rob Herring (Arm) [this message]
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=178464016699.3250705.12302467353770093561.robh@kernel.org \
--to=robh@kernel.org \
--cc=bmasney@redhat.com \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=goledhruva@gmail.com \
--cc=j.bhargav.u@gmail.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-chawdhry@ti.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=simona.toaca@nxp.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
all inboxes | Powered by JetHome®