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 Reason for being RFC. In the comments for the first version, it was said that everything which can be below a ti,clksel should be converted at the same time. But I want to know whether I am on the right track. I plan to convert the clock things from time to time. So enforcing certain compatibles below ti,clksel i 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 v2: - added conversion of divider - require reg now, makes sense after https://lore.kernel.org/linux-omap/20240213105730.5287-1-tony@xxxxxxxxxxx/ - clean up of examples - improvement of documentation v1 is at https://lore.kernel.org/linux-omap/20231127202359.145778-1-andreas@xxxxxxxxxxxx/ Andreas Kemnade (2): dt-bindings: clock: ti: Convert interface.txt to json-schema dt-bindings: clock: ti: Convert divider.txt to json-schema .../devicetree/bindings/clock/ti/divider.txt | 115 ------------ .../bindings/clock/ti/interface.txt | 55 ------ .../bindings/clock/ti/ti,divider-clock.yaml | 175 ++++++++++++++++++ .../bindings/clock/ti/ti,interface-clock.yaml | 70 +++++++ 4 files changed, 245 insertions(+), 170 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
