linux-kernel - Re: [PATCH REBASE] dt-bindings: pinctrl: use pinctrl.yaml

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <c2afe6fe-d4d2-c9c3-eb36-90969a0b657d@gmail.com>
Date:   Tue, 7 Dec 2021 09:47:38 +0100
From:   Rafał Miłecki <zajec5@...il.com>
To:     Rob Herring <robh+dt@...nel.org>
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>,
        patches@...nsource.cirrus.com
Subject: Re: [PATCH REBASE] dt-bindings: pinctrl: use pinctrl.yaml

On 06.12.2021 23:50, Rob Herring wrote:
> 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:

Oops, sorry, I think I didn't test MFD bindings *after* modifying
pinctrl bindings.


> /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

I'm not sure how to deal with this one. If you take a look at
cirrus,madera.yaml it seems to be some complex MFD that is a sound
device with pin controller and regulator.

I'm not sure: is using pinctrl@ node for that hardware is a correct
choice?