[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <02953ce1-0a43-5918-d139-35afd5f15b5b@linaro.org>
Date: Thu, 14 Apr 2022 08:33:50 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Arınç ÜNAL <arinc.unal@...nc9.com>,
Sergio Paracuellos <sergio.paracuellos@...il.com>,
Luiz Angelo Daros de Luca <luizluca@...il.com>,
Linus Walleij <linus.walleij@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
Matthias Brugger <matthias.bgg@...il.com>
Cc: erkin.bozoglu@...ont.com, linux-gpio@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-mips@...r.kernel.org
Subject: Re: [PATCH 11/14] dt-bindings: pinctrl: add binding for Ralink MT7620
pinctrl
On 14/04/2022 03:52, Arınç ÜNAL wrote:
>>
>>> + is not supported. There is no pinconf support.
>>> +
>>> +properties:
>>> + compatible:
>>> + const: ralink,mt7620-pinctrl
>>> +
>>> +patternProperties:
>>> + '-pins$':
>>> + type: object
>>> + patternProperties:
>>> + '^(.*-)?pinmux$':
>>
>> Why do you have two levels here? pins->pinmux->actual pin configuration?
>
> Yes, pins->pinmux->pin-configuration is currently how it's done.
It is currently done? Aren't you bringing here new bindings and new
driver support?
Best regards,
Krzysztof
Powered by blists - more mailing lists