public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Frank Rowand <frowand.list@gmail.com>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: Add vendor prefix for Espressif
Date: Fri, 24 May 2019 16:14:06 +0200	[thread overview]
Message-ID: <20190524141406.z4spzgn2c3e7tjz6@flea> (raw)
In-Reply-To: <CAL_JsqKLVkM6ygAmLsgF+rxAOxdiqBP2i+J1wLNfDeYrPd2JcA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1849 bytes --]

Hi Rob,

On Thu, May 23, 2019 at 09:57:22AM -0500, Rob Herring wrote:
> On Thu, May 23, 2019 at 3:14 AM Maxime Ripard <maxime.ripard@bootlin.com> wrote:
> >
> > Add Espressif Systems DT vendor prefix. That prefix has been used for quite
> > some time for WiFi chips, but has never been documented.
>
> Just 1 of about 100...

Indeed, it turns out that we have much more undocumented prefixes in
the board compatibles....

How do you want to handle this, should we work gradually to support
all the prefixes, or should I send one patch fixing all of the
warnings on my DTs at once?

> Here's a script to generate a schema for compatible string checks. Not
> yet sure what to do with it or how to integrate it in.
>
> #!/bin/sh
>
> vnd_file="Documentation/devicetree/bindings/vendor-prefixes.yaml"
>
> vendor_pattern="$(sed -n -e 's/.*\^\([-a-zA-Z0-9]*\),.*/
> \1\|\\/p' ${vnd_file})"
>
> cat << EOF
> # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> %YAML 1.2
> ---
> \$id: http://devicetree.org/schemas/compatible-vendor-prefixes.yaml#
> \$schema: http://devicetree.org/meta-schemas/base.yaml#
>
> title: Devicetree Vendor Prefix Registry
>
> maintainers:
>   - Rob Herring <robh@kernel.org>
>
> select: true
>
> properties:
>   compatible:
>     maxItems: 32
>     items:
>       if:
>         allOf:
>           - pattern: ","
>           - not: { pattern: "^usb[0-9a-f]+," }
>       then:
>         pattern: "^(\\
> ${vendor_pattern}
>           ),"
>
> EOF

It turned out pretty useful, but yeah, it's not super easy to merge
anywhere in the kernel tree. Maybe you could put it in the tools
directory, with a wrapper that would run make dtbs_check, plus a nice
grep to only report the vendors missing it could find for the current
configuration?

Maxime

--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2019-05-24 14:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-23  8:14 [PATCH] dt-bindings: Add vendor prefix for Espressif Maxime Ripard
2019-05-23 14:57 ` Rob Herring
2019-05-24 14:14   ` Maxime Ripard [this message]
2019-05-24 20:51 ` Rob Herring

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=20190524141406.z4spzgn2c3e7tjz6@flea \
    --to=maxime.ripard@bootlin.com \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    /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