On Tue, May 05, 2020 at 04:02:21PM +0200, Bartosz Golaszewski wrote: > From: Bartosz Golaszewski <bgolaszewski@xxxxxxxxxxxx> > > This adds a binding document for the PERICFG controller present on > MediaTek SoCs. For now the only variant supported is 'mt8516-pericfg'. > > Signed-off-by: Bartosz Golaszewski <bgolaszewski@xxxxxxxxxxxx> > --- > .../arm/mediatek/mediatek,pericfg.yaml | 34 +++++++++++++++++++ > 1 file changed, 34 insertions(+) > create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,pericfg.yaml > > diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,pericfg.yaml b/Documentation/devicetree/bindings/arm/mediatek/mediatek,pericfg.yaml > new file mode 100644 > index 000000000000..74b2a6173ffb > --- /dev/null > +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,pericfg.yaml > @@ -0,0 +1,34 @@ > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: "http://devicetree.org/schemas/arm/mediatek/mediatek,pericfg.yaml#"; > +$schema: "http://devicetree.org/meta-schemas/core.yaml#"; > + > +title: MediaTek Peripheral Configuration Controller > + > +maintainers: > + - Bartosz Golaszewski <bgolaszewski@xxxxxxxxxxxx> > + > +properties: > + compatible: > + oneOf: Don't need oneOf. > + - items: > + - enum: > + - mediatek,pericfg PERICFG is exactly the same register set and functions on all Mediatek SoCs? Needs to be more specific. > + - const: syscon > + > + reg: > + maxItems: 1 > + > +required: > + - compatible > + - reg > + > +additionalProperties: false > + > +examples: > + - | > + pericfg: pericfg@10003050 { > + compatible = "mediatek,mt8516-pericfg", "syscon"; > + reg = <0 0x10003050 0 0x1000>; Default for examples is 1 cell for addr and size. > + }; > -- > 2.25.0 >
