On Tue, May 19, 2026 at 03:29:29PM +0530, Teja Sai Charan B wrote: > From: Teja Sai Charan Bellamkonda > > Convert the rtc-cmos devicetree bindings to dt schema. > > Signed-off-by: Teja Sai Charan Bellamkonda > --- > .../devicetree/bindings/rtc/rtc-cmos.txt | 27 --------- > .../devicetree/bindings/rtc/rtc-cmos.yaml | 55 +++++++++++++++++++ > 2 files changed, 55 insertions(+), 27 deletions(-) > delete mode 100644 Documentation/devicetree/bindings/rtc/rtc-cmos.txt > create mode 100644 Documentation/devicetree/bindings/rtc/rtc-cmos.yaml > > diff --git a/Documentation/devicetree/bindings/rtc/rtc-cmos.txt b/Documentation/devicetree/bindings/rtc/rtc-cmos.txt > deleted file mode 100644 > index 7d7b5f6bda65..000000000000 > --- a/Documentation/devicetree/bindings/rtc/rtc-cmos.txt > +++ /dev/null > @@ -1,27 +0,0 @@ > - Motorola mc146818 compatible RTC > -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > - > -Required properties: > - - compatible : "motorola,mc146818" > - - reg : should contain registers location and length. > - > -Optional properties: > - - interrupts : should contain interrupt. > - - ctrl-reg : Contains the initial value of the control register also > - called "Register B". > - - freq-reg : Contains the initial value of the frequency register also > - called "Register A". > - > -"Register A" and "B" are usually initialized by the firmware (BIOS for > -instance). If this is not done, it can be performed by the driver. > - > -ISA Example: > - > - rtc@70 { > - compatible = "motorola,mc146818"; > - interrupts = <8 3>; > - interrupt-parent = <&ioapic1>; > - ctrl-reg = <2>; > - freq-reg = <0x26>; > - reg = <1 0x70 2>; > - }; > diff --git a/Documentation/devicetree/bindings/rtc/rtc-cmos.yaml b/Documentation/devicetree/bindings/rtc/rtc-cmos.yaml > new file mode 100644 > index 000000000000..e368264ac483 > --- /dev/null > +++ b/Documentation/devicetree/bindings/rtc/rtc-cmos.yaml > @@ -0,0 +1,55 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/rtc/rtc-cmos.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Motorola mc146818 compatible RTC > + > +maintainers: > + - Alexandre Belloni > + > +properties: > + compatible: > + const: motorola,mc146818 It's not a problem with the conversion per se, but as sashiko pointed out, there's an intel device with a soc-specific compatible. Could you document that here, with a fallback to this motorola one please? pw-bot: changes-requested Thanks, Conor. > + > + reg: > + maxItems: 1 > + > + interrupts: > + maxItems: 1 > + > + ctrl-reg: > + $ref: /schemas/types.yaml#/definitions/uint32 > + description: > + Initial value of the control register > + (also known as Register B). > + > + freq-reg: > + $ref: /schemas/types.yaml#/definitions/uint32 > + description: > + Initial value of the frequency register > + (also known as Register A). > + > +required: > + - compatible > + - reg > + > +additionalProperties: false > + > +examples: > + - | > + bus { > + #address-cells = <2>; > + #size-cells = <1>; > + > + rtc@70 { > + compatible = "motorola,mc146818"; > + reg = <1 0x70 2>; Please be consistent here about using only hex, even if the text file didn't do that. > + > + interrupts = <8 3>; > + > + ctrl-reg = <2>; > + freq-reg = <0x26>; > + }; > + }; > -- > 2.43.0 >