On Sun, Nov 27, 2022 at 09:24:44PM +0800, Jisheng Zhang wrote: > Several SoMs and boards are available that feature the Bouffalolab > bl808 SoC. Document the compatible strings. > > Signed-off-by: Jisheng Zhang <jszhang@xxxxxxxxxx> > --- > .../bindings/riscv/bouffalolab.yaml | 34 +++++++++++++++++++ > 1 file changed, 34 insertions(+) > create mode 100644 Documentation/devicetree/bindings/riscv/bouffalolab.yaml > > diff --git a/Documentation/devicetree/bindings/riscv/bouffalolab.yaml b/Documentation/devicetree/bindings/riscv/bouffalolab.yaml > new file mode 100644 > index 000000000000..91ca9dbdc798 > --- /dev/null > +++ b/Documentation/devicetree/bindings/riscv/bouffalolab.yaml > @@ -0,0 +1,34 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/riscv/bouffalolab.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Bouffalo Lab Technology SoC-based boards > + > +maintainers: > + - Jisheng Zhang <jszhang@xxxxxxxxxx> > + > +description: > + Bouffalo Lab Technology SoC-based boards > + > +properties: > + $nodename: > + const: '/' > + compatible: > + oneOf: > + - description: Sipeed M1s SoM: ^ Drop these :s in the descriptions to placate Rob's bot :) > + items: > + - const: sipeed,m1s > + - const: bouffalolab,bl808 > + > + - description: Carrier boards for the Sipeed M1s SoM: > + items: > + - enum: > + - sipeed,m1s-dock Do we need the enum when there's only one? I assume you're future proofing against adding more carriers? Otherwise than those two bits: Reviewed-by: Conor Dooley <conor.dooley@xxxxxxxxxxxxx> > + - const: sipeed,m1s > + - const: bouffalolab,bl808 > + > +additionalProperties: true > + > +... > -- > 2.38.1 >
