[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqL=4iUJjQXjGc7eacbYW5YE-VRC4yGhu8pLVd-zUKvhHQ@mail.gmail.com>
Date: Mon, 6 Dec 2021 16:50:34 -0600
From: Rob Herring <robh+dt@...nel.org>
To: Rafał Miłecki <zajec5@...il.com>
Cc: Linus Walleij <linus.walleij@...aro.org>,
linux-gpio@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
Rafał Miłecki <rafal@...ecki.pl>
Subject: Re: [PATCH REBASE] dt-bindings: pinctrl: use pinctrl.yaml
On Thu, Dec 2, 2021 at 12:32 AM Rafał Miłecki <zajec5@...il.com> wrote:
>
> From: Rafał Miłecki <rafal@...ecki.pl>
>
> Also fix some examples to avoid warnings like:
> brcm,ns-pinmux.example.dt.yaml: pin-controller@...0c1c0: $nodename:0: 'pin-controller@...0c1c0' does not match '^pinctrl|pinmux@[0-9a-f]+$'
I think you missed some. linux-next now has these warnings:
builds/robherring/linux-dt/Documentation/devicetree/bindings/mfd/brcm,cru.example.dt.yaml:
pin-controller@1c0: $nodename:0: 'pin-controller@...' does not match
'^(pinctrl|pinmux)(@[0-9a-f]+)?$'
>From schema: /builds/robherring/linux-dt/Documentation/devicetree/bindings/pinctrl/brcm,ns-pinmux.yaml
/builds/robherring/linux-dt/Documentation/devicetree/bindings/mfd/cirrus,madera.example.dt.yaml:
codec@1a: $nodename:0: 'codec@1a' does not match
'^(pinctrl|pinmux)(@[0-9a-f]+)?$'
>From schema: /builds/robherring/linux-dt/Documentation/devicetree/bindings/mfd/cirrus,madera.yaml
/builds/robherring/linux-dt/Documentation/devicetree/bindings/mfd/cirrus,lochnagar.example.dt.yaml:
lochnagar-pinctrl: $nodename:0: 'lochnagar-pinctrl' does not match
'^(pinctrl|pinmux)(@[0-9a-f]+)?$'
>From schema: /builds/robherring/linux-dt/Documentation/devicetree/bindings/pinctrl/cirrus,lochnagar.yaml
Powered by blists - more mailing lists