devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: "Rafał Miłecki" <rafal@milecki.pl>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	"Richard Weinberger" <richard@nod.at>,
	"Vignesh Raghavendra" <vigneshr@ti.com>,
	linux-mtd@lists.infradead.org,
	"Krzysztof Kozlowski" <krzysztof.kozlowski@canonical.com>,
	"Miquel Raynal" <miquel.raynal@bootlin.com>,
	devicetree@vger.kernel.org, "Hauke Mehrtens" <hauke@hauke-m.de>
Subject: Re: [PATCH] dt-bindings: mtd: partitions: convert Broadcom's TRX to the json-schema
Date: Wed, 23 Feb 2022 17:05:53 -0600	[thread overview]
Message-ID: <Yha90XxGrRJZ/ANR@robh.at.kernel.org> (raw)
In-Reply-To: <3be13bc2-f8b1-193b-9a36-92d4336d9d28@milecki.pl>

On Thu, Feb 17, 2022 at 08:43:23AM +0100, Rafał Miłecki wrote:
> Hi Rob,
> 
> On 17.02.2022 04:59, Rob Herring wrote:
> > On Wed, 16 Feb 2022 11:41:26 +0100, Rafał Miłecki wrote:
> > > From: Rafał Miłecki <rafal@milecki.pl>
> > > 
> > > This helps validating DTS files.
> > > 
> > > Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> > > ---
> > >   .../bindings/mtd/partitions/brcm,trx.txt      | 42 ---------------
> > >   .../bindings/mtd/partitions/brcm,trx.yaml     | 51 +++++++++++++++++++
> > >   2 files changed, 51 insertions(+), 42 deletions(-)
> > >   delete mode 100644 Documentation/devicetree/bindings/mtd/partitions/brcm,trx.txt
> > >   create mode 100644 Documentation/devicetree/bindings/mtd/partitions/brcm,trx.yaml
> > > 
> > 
> > My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
> > on your patch (DT_CHECKER_FLAGS is new in v5.13):
> > 
> > yamllint warnings/errors:
> > 
> > dtschema/dtc warnings/errors:
> > /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/mtd/partitions/linksys,ns-partitions.example.dt.yaml: partition@200000: compatible:0: 'brcm,trx' was expected
> > 	From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/mtd/partitions/brcm,trx.yaml
> > /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/mtd/partitions/linksys,ns-partitions.example.dt.yaml: partition@200000: compatible: ['linksys,ns-firmware', 'brcm,trx'] is too long
> > 	From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/mtd/partitions/brcm,trx.yaml
> 
> could you advise the best way to solve that?

You should move linksys,ns-firmware from linksys,ns-partitions.yaml to 
this schema. Then linksys,ns-partitions.yaml just has:

  "^partition@[0-9a-f]+$":
    $ref: "partition.yaml#"
    additionalProperties: true

That's not completely ideal because then undocumented properties are 
allowed. To fix that, you'd need:

  "^partition@[0-9a-f]+$":
    oneOf:
      - $ref: "partition.yaml#"
      - $ref: "brcm,trx.yaml#"
    unevaluatedProperties: false

I'm not 100% sure that will work.

Rob

      reply	other threads:[~2022-02-23 23:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 10:41 [PATCH] dt-bindings: mtd: partitions: convert Broadcom's TRX to the json-schema Rafał Miłecki
2022-02-17  3:59 ` Rob Herring
2022-02-17  7:43   ` Rafał Miłecki
2022-02-23 23:05     ` Rob Herring [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Yha90XxGrRJZ/ANR@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hauke@hauke-m.de \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=rafal@milecki.pl \
    --cc=richard@nod.at \
    --cc=vigneshr@ti.com \
    --cc=zajec5@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).