From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.5 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4EA2DC65C20 for ; Mon, 8 Oct 2018 16:54:55 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0D82C2145D for ; Mon, 8 Oct 2018 16:54:54 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="Dqmw3cem" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 0D82C2145D Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726600AbeJIAHb (ORCPT ); Mon, 8 Oct 2018 20:07:31 -0400 Received: from mail.kernel.org ([198.145.29.99]:45660 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726291AbeJIAHa (ORCPT ); Mon, 8 Oct 2018 20:07:30 -0400 Received: from mail-qk1-f178.google.com (mail-qk1-f178.google.com [209.85.222.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 98F7920858; Mon, 8 Oct 2018 16:54:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1539017692; bh=T05h9mmNjIzCxCA8ih41bZoXJcOSt7z8Y0uiPOjn0T4=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=Dqmw3cemvPVW/3tj2PFDVegszgjHVScyO/LKZg8C9jBCJAVmr52QYBOzuGj72nEJl NL6ILpRm4E7J/jNoab1TiP+KVAy4ybkWO6fUxnMpwNXDv44slUqn+TfY9KKv15kfMf rCZc9BLhgTWOU2JLqyVDTkiJ6utSUDp0/a+ihO1g= Received: by mail-qk1-f178.google.com with SMTP id a13-v6so7834161qkc.7; Mon, 08 Oct 2018 09:54:52 -0700 (PDT) X-Gm-Message-State: ABuFfogLrbqLnYuoe01jszL2SPgI9JPSx2d3kJfDZ2clVonyfIyctUH6 sESvzs4/azV67ZWum3ifTeJ40Ah0v9rKZIZhUQ== X-Google-Smtp-Source: ACcGV62vWiL9PqL0hCfNL+kOwEtmWWHMKd+uBSZVRuVOjwsyyQJOaIIGhX+3QCmw6pxp7Rt04CXhem113T0zqHUKAA0= X-Received: by 2002:a37:12d1:: with SMTP id 78-v6mr19519749qks.147.1539017691827; Mon, 08 Oct 2018 09:54:51 -0700 (PDT) MIME-Version: 1.0 References: <20181005165848.3474-1-robh@kernel.org> <20181005165848.3474-30-robh@kernel.org> In-Reply-To: From: Rob Herring Date: Mon, 8 Oct 2018 11:54:40 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 29/36] dt-bindings: arm: Convert Renesas board/soc bindings to json-schema To: Geert Uytterhoeven Cc: "linux-kernel@vger.kernel.org" , devicetree@vger.kernel.org, "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , linuxppc-dev , Grant Likely , Kumar Gala , Frank Rowand , Mark Rutland , Linus Walleij , Olof Johansson , Arnd Bergmann , Mark Brown , Tom Rini , Pantelis Antoniou , Jonathan Cameron , Bjorn Andersson , Simon Horman , Magnus Damm , "open list:MEDIA DRIVERS FOR RENESAS - FCP" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 8, 2018 at 10:13 AM Geert Uytterhoeven wrote: > > Hi Rob, > > On Mon, Oct 8, 2018 at 4:57 PM Rob Herring wrote: > > On Mon, Oct 8, 2018 at 2:47 AM Geert Uytterhoeven wrote: > > > On Fri, Oct 5, 2018 at 6:59 PM Rob Herring wrote: > > > > Convert Renesas SoC bindings to DT schema format using json-schema. > > > > > --- /dev/null > > > > +++ b/Documentation/devicetree/bindings/arm/shmobile.yaml > > > > @@ -0,0 +1,205 @@ > > > > > + - description: Kingfisher (SBEV-RCAR-KF-M03) > > > > + items: > > > > + - const: shimafuji,kingfisher > > > > + - enum: > > > > + - renesas,h3ulcb > > > > + - renesas,m3ulcb > > > > + - enum: > > > > + - renesas,r8a7795 > > > > + - renesas,r8a7796 > > > > > > This looks a bit funny: all other entries have the "const" last, and > > > use it for the > > > SoC number. May be correct, though. > > > To clarify, this is an extension board that can fit both the [HM]3ULCB > > > boards (actually also the new M3NULCB, I think). > > > > This being Kingfisher? > > Correct. > > > I wrote this based on dts files in the tree. There's 2 combinations that I see: > > > > "shimafuji,kingfisher", "renesas,h3ulcb", "renesas,r8a7795" > > "shimafuji,kingfisher", "renesas,m3ulcb", "renesas,r8a7796" > > > > The schema allows 4 combinations (1 * 2 * 2). I have no idea if the > > other combinations are possible. If not, then we could rewrite this as > > 2 entries with 3 const values each. > > I expect there will soon be a third one: > > "shimafuji,kingfisher", "renesas,m3nulcb", "renesas,r8a77965" > > Technically, {h3,m3,m3n}ulcb are the same board (although there may be > minor revision differences), with a different SiP mounted. > But they are called/marketed depending on which SiP is mounted. > > And on top of that, you can plug in a Kingfisher daughterboard. Could be an > overlay ;-) We probably shouldn't have put kingfisher as a top-level compatible then. But we did, so not really much point to discuss that now. As to whether there's a better way to express it in the schema, I'm not sure. I don't think there's a way with json-schema to express a list, but the 1st item is optional. Rob From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Herring Subject: Re: [PATCH 29/36] dt-bindings: arm: Convert Renesas board/soc bindings to json-schema Date: Mon, 8 Oct 2018 11:54:40 -0500 Message-ID: References: <20181005165848.3474-1-robh@kernel.org> <20181005165848.3474-30-robh@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Geert Uytterhoeven Cc: "linux-kernel@vger.kernel.org" , devicetree@vger.kernel.org, "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , linuxppc-dev , Grant Likely , Kumar Gala , Frank Rowand , Mark Rutland , Linus Walleij , Olof Johansson , Arnd Bergmann , Mark Brown , Tom Rini , Pantelis Antoniou , Jonathan Cameron , Bjorn Andersson , Simon Horman , Magnus Damm List-Id: devicetree@vger.kernel.org On Mon, Oct 8, 2018 at 10:13 AM Geert Uytterhoeven wrote: > > Hi Rob, > > On Mon, Oct 8, 2018 at 4:57 PM Rob Herring wrote: > > On Mon, Oct 8, 2018 at 2:47 AM Geert Uytterhoeven wrote: > > > On Fri, Oct 5, 2018 at 6:59 PM Rob Herring wrote: > > > > Convert Renesas SoC bindings to DT schema format using json-schema. > > > > > --- /dev/null > > > > +++ b/Documentation/devicetree/bindings/arm/shmobile.yaml > > > > @@ -0,0 +1,205 @@ > > > > > + - description: Kingfisher (SBEV-RCAR-KF-M03) > > > > + items: > > > > + - const: shimafuji,kingfisher > > > > + - enum: > > > > + - renesas,h3ulcb > > > > + - renesas,m3ulcb > > > > + - enum: > > > > + - renesas,r8a7795 > > > > + - renesas,r8a7796 > > > > > > This looks a bit funny: all other entries have the "const" last, and > > > use it for the > > > SoC number. May be correct, though. > > > To clarify, this is an extension board that can fit both the [HM]3ULCB > > > boards (actually also the new M3NULCB, I think). > > > > This being Kingfisher? > > Correct. > > > I wrote this based on dts files in the tree. There's 2 combinations that I see: > > > > "shimafuji,kingfisher", "renesas,h3ulcb", "renesas,r8a7795" > > "shimafuji,kingfisher", "renesas,m3ulcb", "renesas,r8a7796" > > > > The schema allows 4 combinations (1 * 2 * 2). I have no idea if the > > other combinations are possible. If not, then we could rewrite this as > > 2 entries with 3 const values each. > > I expect there will soon be a third one: > > "shimafuji,kingfisher", "renesas,m3nulcb", "renesas,r8a77965" > > Technically, {h3,m3,m3n}ulcb are the same board (although there may be > minor revision differences), with a different SiP mounted. > But they are called/marketed depending on which SiP is mounted. > > And on top of that, you can plug in a Kingfisher daughterboard. Could be an > overlay ;-) We probably shouldn't have put kingfisher as a top-level compatible then. But we did, so not really much point to discuss that now. As to whether there's a better way to express it in the schema, I'm not sure. I don't think there's a way with json-schema to express a list, but the 1st item is optional. Rob From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.kernel.org ([198.145.29.99]:45660 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726291AbeJIAHa (ORCPT ); Mon, 8 Oct 2018 20:07:30 -0400 MIME-Version: 1.0 References: <20181005165848.3474-1-robh@kernel.org> <20181005165848.3474-30-robh@kernel.org> In-Reply-To: From: Rob Herring Date: Mon, 8 Oct 2018 11:54:40 -0500 Message-ID: Subject: Re: [PATCH 29/36] dt-bindings: arm: Convert Renesas board/soc bindings to json-schema To: Geert Uytterhoeven Cc: "linux-kernel@vger.kernel.org" , devicetree@vger.kernel.org, "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , linuxppc-dev , Grant Likely , Kumar Gala , Frank Rowand , Mark Rutland , Linus Walleij , Olof Johansson , Arnd Bergmann , Mark Brown , Tom Rini , Pantelis Antoniou , Jonathan Cameron , Bjorn Andersson , Simon Horman , Magnus Damm , "open list:MEDIA DRIVERS FOR RENESAS - FCP" Content-Type: text/plain; charset="UTF-8" Sender: linux-renesas-soc-owner@vger.kernel.org List-ID: On Mon, Oct 8, 2018 at 10:13 AM Geert Uytterhoeven wrote: > > Hi Rob, > > On Mon, Oct 8, 2018 at 4:57 PM Rob Herring wrote: > > On Mon, Oct 8, 2018 at 2:47 AM Geert Uytterhoeven wrote: > > > On Fri, Oct 5, 2018 at 6:59 PM Rob Herring wrote: > > > > Convert Renesas SoC bindings to DT schema format using json-schema. > > > > > --- /dev/null > > > > +++ b/Documentation/devicetree/bindings/arm/shmobile.yaml > > > > @@ -0,0 +1,205 @@ > > > > > + - description: Kingfisher (SBEV-RCAR-KF-M03) > > > > + items: > > > > + - const: shimafuji,kingfisher > > > > + - enum: > > > > + - renesas,h3ulcb > > > > + - renesas,m3ulcb > > > > + - enum: > > > > + - renesas,r8a7795 > > > > + - renesas,r8a7796 > > > > > > This looks a bit funny: all other entries have the "const" last, and > > > use it for the > > > SoC number. May be correct, though. > > > To clarify, this is an extension board that can fit both the [HM]3ULCB > > > boards (actually also the new M3NULCB, I think). > > > > This being Kingfisher? > > Correct. > > > I wrote this based on dts files in the tree. There's 2 combinations that I see: > > > > "shimafuji,kingfisher", "renesas,h3ulcb", "renesas,r8a7795" > > "shimafuji,kingfisher", "renesas,m3ulcb", "renesas,r8a7796" > > > > The schema allows 4 combinations (1 * 2 * 2). I have no idea if the > > other combinations are possible. If not, then we could rewrite this as > > 2 entries with 3 const values each. > > I expect there will soon be a third one: > > "shimafuji,kingfisher", "renesas,m3nulcb", "renesas,r8a77965" > > Technically, {h3,m3,m3n}ulcb are the same board (although there may be > minor revision differences), with a different SiP mounted. > But they are called/marketed depending on which SiP is mounted. > > And on top of that, you can plug in a Kingfisher daughterboard. Could be an > overlay ;-) We probably shouldn't have put kingfisher as a top-level compatible then. But we did, so not really much point to discuss that now. As to whether there's a better way to express it in the schema, I'm not sure. I don't think there's a way with json-schema to express a list, but the 1st item is optional. Rob From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0A1A8C65C20 for ; Mon, 8 Oct 2018 16:57:18 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 6FBBA20858 for ; Mon, 8 Oct 2018 16:57:17 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="Dqmw3cem" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6FBBA20858 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from lists.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 42TRNq3pyyzF3F3 for ; Tue, 9 Oct 2018 03:57:15 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; dmarc=pass (p=none dis=none) header.from=kernel.org Authentication-Results: lists.ozlabs.org; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.b="Dqmw3cem"; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=pass (mailfrom) smtp.mailfrom=kernel.org (client-ip=198.145.29.99; helo=mail.kernel.org; envelope-from=robh@kernel.org; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=pass (p=none dis=none) header.from=kernel.org Authentication-Results: lists.ozlabs.org; dkim=pass (1024-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.b="Dqmw3cem"; dkim-atps=neutral Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 42TRL66hpCzF3CZ for ; Tue, 9 Oct 2018 03:54:54 +1100 (AEDT) Received: from mail-qk1-f173.google.com (mail-qk1-f173.google.com [209.85.222.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id A3E6D21479 for ; Mon, 8 Oct 2018 16:54:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1539017692; bh=T05h9mmNjIzCxCA8ih41bZoXJcOSt7z8Y0uiPOjn0T4=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=Dqmw3cemvPVW/3tj2PFDVegszgjHVScyO/LKZg8C9jBCJAVmr52QYBOzuGj72nEJl NL6ILpRm4E7J/jNoab1TiP+KVAy4ybkWO6fUxnMpwNXDv44slUqn+TfY9KKv15kfMf rCZc9BLhgTWOU2JLqyVDTkiJ6utSUDp0/a+ihO1g= Received: by mail-qk1-f173.google.com with SMTP id 12-v6so5598335qkj.10 for ; Mon, 08 Oct 2018 09:54:52 -0700 (PDT) X-Gm-Message-State: ABuFfog2z4wbh260MAISqr516z0JKAIdnIvhpGGbow2/oWQ9u5p5DntJ TqqsSJEBsNgCWnGWtKINEf03m9V5QB6c1YLV2A== X-Google-Smtp-Source: ACcGV62vWiL9PqL0hCfNL+kOwEtmWWHMKd+uBSZVRuVOjwsyyQJOaIIGhX+3QCmw6pxp7Rt04CXhem113T0zqHUKAA0= X-Received: by 2002:a37:12d1:: with SMTP id 78-v6mr19519749qks.147.1539017691827; Mon, 08 Oct 2018 09:54:51 -0700 (PDT) MIME-Version: 1.0 References: <20181005165848.3474-1-robh@kernel.org> <20181005165848.3474-30-robh@kernel.org> In-Reply-To: From: Rob Herring Date: Mon, 8 Oct 2018 11:54:40 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 29/36] dt-bindings: arm: Convert Renesas board/soc bindings to json-schema To: Geert Uytterhoeven Content-Type: text/plain; charset="UTF-8" X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Mark Rutland , devicetree@vger.kernel.org, Kumar Gala , Grant Likely , Arnd Bergmann , Tom Rini , Simon Horman , Frank Rowand , Linus Walleij , Pantelis Antoniou , "linux-kernel@vger.kernel.org" , Bjorn Andersson , "open list:MEDIA DRIVERS FOR RENESAS - FCP" , Mark Brown , Jonathan Cameron , Olof Johansson , linuxppc-dev , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On Mon, Oct 8, 2018 at 10:13 AM Geert Uytterhoeven wrote: > > Hi Rob, > > On Mon, Oct 8, 2018 at 4:57 PM Rob Herring wrote: > > On Mon, Oct 8, 2018 at 2:47 AM Geert Uytterhoeven wrote: > > > On Fri, Oct 5, 2018 at 6:59 PM Rob Herring wrote: > > > > Convert Renesas SoC bindings to DT schema format using json-schema. > > > > > --- /dev/null > > > > +++ b/Documentation/devicetree/bindings/arm/shmobile.yaml > > > > @@ -0,0 +1,205 @@ > > > > > + - description: Kingfisher (SBEV-RCAR-KF-M03) > > > > + items: > > > > + - const: shimafuji,kingfisher > > > > + - enum: > > > > + - renesas,h3ulcb > > > > + - renesas,m3ulcb > > > > + - enum: > > > > + - renesas,r8a7795 > > > > + - renesas,r8a7796 > > > > > > This looks a bit funny: all other entries have the "const" last, and > > > use it for the > > > SoC number. May be correct, though. > > > To clarify, this is an extension board that can fit both the [HM]3ULCB > > > boards (actually also the new M3NULCB, I think). > > > > This being Kingfisher? > > Correct. > > > I wrote this based on dts files in the tree. There's 2 combinations that I see: > > > > "shimafuji,kingfisher", "renesas,h3ulcb", "renesas,r8a7795" > > "shimafuji,kingfisher", "renesas,m3ulcb", "renesas,r8a7796" > > > > The schema allows 4 combinations (1 * 2 * 2). I have no idea if the > > other combinations are possible. If not, then we could rewrite this as > > 2 entries with 3 const values each. > > I expect there will soon be a third one: > > "shimafuji,kingfisher", "renesas,m3nulcb", "renesas,r8a77965" > > Technically, {h3,m3,m3n}ulcb are the same board (although there may be > minor revision differences), with a different SiP mounted. > But they are called/marketed depending on which SiP is mounted. > > And on top of that, you can plug in a Kingfisher daughterboard. Could be an > overlay ;-) We probably shouldn't have put kingfisher as a top-level compatible then. But we did, so not really much point to discuss that now. As to whether there's a better way to express it in the schema, I'm not sure. I don't think there's a way with json-schema to express a list, but the 1st item is optional. Rob From mboxrd@z Thu Jan 1 00:00:00 1970 From: robh@kernel.org (Rob Herring) Date: Mon, 8 Oct 2018 11:54:40 -0500 Subject: [PATCH 29/36] dt-bindings: arm: Convert Renesas board/soc bindings to json-schema In-Reply-To: References: <20181005165848.3474-1-robh@kernel.org> <20181005165848.3474-30-robh@kernel.org> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, Oct 8, 2018 at 10:13 AM Geert Uytterhoeven wrote: > > Hi Rob, > > On Mon, Oct 8, 2018 at 4:57 PM Rob Herring wrote: > > On Mon, Oct 8, 2018 at 2:47 AM Geert Uytterhoeven wrote: > > > On Fri, Oct 5, 2018 at 6:59 PM Rob Herring wrote: > > > > Convert Renesas SoC bindings to DT schema format using json-schema. > > > > > --- /dev/null > > > > +++ b/Documentation/devicetree/bindings/arm/shmobile.yaml > > > > @@ -0,0 +1,205 @@ > > > > > + - description: Kingfisher (SBEV-RCAR-KF-M03) > > > > + items: > > > > + - const: shimafuji,kingfisher > > > > + - enum: > > > > + - renesas,h3ulcb > > > > + - renesas,m3ulcb > > > > + - enum: > > > > + - renesas,r8a7795 > > > > + - renesas,r8a7796 > > > > > > This looks a bit funny: all other entries have the "const" last, and > > > use it for the > > > SoC number. May be correct, though. > > > To clarify, this is an extension board that can fit both the [HM]3ULCB > > > boards (actually also the new M3NULCB, I think). > > > > This being Kingfisher? > > Correct. > > > I wrote this based on dts files in the tree. There's 2 combinations that I see: > > > > "shimafuji,kingfisher", "renesas,h3ulcb", "renesas,r8a7795" > > "shimafuji,kingfisher", "renesas,m3ulcb", "renesas,r8a7796" > > > > The schema allows 4 combinations (1 * 2 * 2). I have no idea if the > > other combinations are possible. If not, then we could rewrite this as > > 2 entries with 3 const values each. > > I expect there will soon be a third one: > > "shimafuji,kingfisher", "renesas,m3nulcb", "renesas,r8a77965" > > Technically, {h3,m3,m3n}ulcb are the same board (although there may be > minor revision differences), with a different SiP mounted. > But they are called/marketed depending on which SiP is mounted. > > And on top of that, you can plug in a Kingfisher daughterboard. Could be an > overlay ;-) We probably shouldn't have put kingfisher as a top-level compatible then. But we did, so not really much point to discuss that now. As to whether there's a better way to express it in the schema, I'm not sure. I don't think there's a way with json-schema to express a list, but the 1st item is optional. Rob