On Wed, Sep 13, 2023 at 05:16:05PM +0200, Romain Perier wrote: > Add YAML bindings for Mstar SSD202D RTC. > > Signed-off-by: Romain Perier <romain.perier@xxxxxxxxx> > --- > .../bindings/rtc/mstar,ssd202d-rtc.yaml | 35 +++++++++++++++++++ > 1 file changed, 35 insertions(+) > create mode 100644 Documentation/devicetree/bindings/rtc/mstar,ssd202d-rtc.yaml > > diff --git a/Documentation/devicetree/bindings/rtc/mstar,ssd202d-rtc.yaml b/Documentation/devicetree/bindings/rtc/mstar,ssd202d-rtc.yaml > new file mode 100644 > index 000000000000..4c1f22ef5a2c > --- /dev/null > +++ b/Documentation/devicetree/bindings/rtc/mstar,ssd202d-rtc.yaml > @@ -0,0 +1,35 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/rtc/mstar,ssd202d-rtc.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Mstar SSD202D Real Time Clock > + > +maintainers: > + - Daniel Palmer <daniel@xxxxxxxx> > + - Romain Perier <romain.perier@xxxxxxxxx> > + > +allOf: > + - $ref: rtc.yaml# > + > +properties: > + compatible: > + enum: > + - mstar,ssd202d-rtc > + reg: > + maxItems: 1 > + > +required: > + - compatible > + - reg So, this seems fine to me in isolation, but isn't this now the sort of thing that can be documented in trivial-rtc.yaml? Its only got compatible & reg, which seems to fit the bill for that. Apologies if I am missing something, Conor. > + > +unevaluatedProperties: false > + > +examples: > + - | > + rtc@6800 { > + compatible = "mstar,ssd202d-rtc"; > + reg = <0x6800 0x200>; > + }; > +... > -- > 2.39.2 >
Attachment:
signature.asc
Description: PGP signature
