Hi all, Am 21.03.24 um 22:47 schrieb Josua Mayer: > Add bindings for SolidRun Clearfog boards, using a new SoM based on > CN9130 SoC. > The carrier boards are identical to the older Armada 388 based Clearfog > boards. For consistency the carrier part of compatible strings are > copied, including the established "-a1" suffix. > > Signed-off-by: Josua Mayer <josua@xxxxxxxxxxxxx> > --- > .../devicetree/bindings/arm/marvell/armada-7k-8k.yaml | 12 ++++++++++++ > 1 file changed, 12 insertions(+) > > diff --git a/Documentation/devicetree/bindings/arm/marvell/armada-7k-8k.yaml b/Documentation/devicetree/bindings/arm/marvell/armada-7k-8k.yaml > index 16d2e132d3d1..36bdfd1bedd9 100644 > --- a/Documentation/devicetree/bindings/arm/marvell/armada-7k-8k.yaml > +++ b/Documentation/devicetree/bindings/arm/marvell/armada-7k-8k.yaml > @@ -82,4 +82,16 @@ properties: > - const: marvell,armada-ap807-quad > - const: marvell,armada-ap807 > > + - description: > + SolidRun CN9130 clearfog family single-board computers > + items: vvv > + - enum: > + - solidrun,clearfog-base-a1 > + - solidrun,clearfog-pro-a1 > + - const: solidrun,clearfog-a1 ^^^ After some thought, this no longer makes any sense to me. Even identical carrier board combined with different SoC will have different characteristics. Any reason to repeat armada 388 board compatibles? Otherwise I may choose only solidrun,cn9130-clearfog-base/pro. > + - const: solidrun,cn9130-sr-som > + - const: marvell,cn9130 > + - const: marvell,armada-ap807-quad > + - const: marvell,armada-ap807 > + > additionalProperties: true >
