[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250409111002.5b88a127@akair>
Date: Wed, 9 Apr 2025 11:10:02 +0200
From: Andreas Kemnade <andreas@...nade.info>
To: Sukrut Bellary <sbellary@...libre.com>
Cc: Michael Turquette <mturquette@...libre.com>, Stephen Boyd
<sboyd@...nel.org>, Rob Herring <robh@...nel.org>, Krzysztof Kozlowski
<krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, Tero Kristo
<kristo@...nel.org>, Kevin Hilman <khilman@...libre.com>,
linux-clk@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/4] dt-bindings: clock: ti: Convert to yaml
Am Thu, 3 Apr 2025 18:44:58 -0700
schrieb Sukrut Bellary <sbellary@...libre.com>:
> This binding doesn't define a new clock binding type,
> it is used to group the existing clock nodes under the hardware hierarchy.
>
> As this is not a provider clock, remove #clock-cells and
> clock-output-names properties.
> Though few clockdomain nodes in the dts use these properties,
> we are not fixing dts here.
> Clean up the example to meet the current standards.
>
> Add the creator of the original binding as a maintainer.
>
> Signed-off-by: Sukrut Bellary <sbellary@...libre.com>
> ---
> .../bindings/clock/ti/clockdomain.txt | 25 ------------
> .../bindings/clock/ti/ti,clockdomain.yaml | 38 +++++++++++++++++++
I am wondering whether this should just be part of a converted version
of Documentation/devicetree/bindings/arm/omap/prcm.txt. I doubt there
is any other usage for this compatible.
Regards,
Andreas
Powered by blists - more mailing lists