[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231128171647.GA3343123-robh@kernel.org>
Date: Tue, 28 Nov 2023 11:16:47 -0600
From: Rob Herring <robh@...nel.org>
To: Andreas Kemnade <andreas@...nade.info>
Cc: mturquette@...libre.com, sboyd@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
kristo@...nel.org, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-omap@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: clock: ti: Convert interface.txt to
json-schema
On Mon, Nov 27, 2023 at 09:23:59PM +0100, Andreas Kemnade wrote:
> Convert the OMAP interface clock device tree binding to json-schema
> and fix up reg property which is optional and taken from parent if
> not specified.
> Specify the creator of the original binding as a maintainer.
Great! This and other TI clocks are at the top of the list[1] of
occurrences of undocumented (by schemas) compatibles:
3763 ['ti,omap3-interface-clock']
3249 ['ti,divider-clock']
1764 ['ti,mux-clock']
1680 ['ti,gate-clock']
1522 ['ti,wait-gate-clock']
1459 ['ti,composite-clock']
1343 ['ti,composite-mux-clock']
1341 ['ti,clkctrl']
1296 ['fsl,imx6q-ssi', 'fsl,imx51-ssi']
1196 ['ti,composite-gate-clock']
1032 ['ti,clockdomain']
Of course, that's largely due to OMAP being early clock adopter and
trying to do fine-grained clocks in DT.
Rob
[1] https://gitlab.com/robherring/linux-dt/-/jobs/5620809910#L5618
Powered by blists - more mailing lists