[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <286bbd0f-1632-6071-7d08-e56ed16c234c@linaro.org>
Date: Wed, 14 Dec 2022 14:10:14 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Arınç ÜNAL <arinc.unal@...nc9.com>,
Linus Walleij <linus.walleij@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Matthias Brugger <matthias.bgg@...il.com>,
Sergio Paracuellos <sergio.paracuellos@...il.com>,
Luiz Angelo Daros de Luca <luizluca@...il.com>
Cc: 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 2/6] dt-bindings: pinctrl: mt7620: add proper function
muxing binding
On 14/12/2022 14:03, Arınç ÜNAL wrote:
> On 14.12.2022 14:55, Krzysztof Kozlowski wrote:
>>>
>>> + allOf:
>>> + - if:
>>> + properties:
>>> + function:
>>> + const: antenna
>>> + then:
>>> + properties:
>>> + groups:
>>> + enum: [i2s]
>>
>> I have doubts such setup is maintainable and readable. I would suggest
>> to leave just few - maybe for gpio, jtag, refclk, utif.
>
> These bindings are not going to change once all properly defined and I'm
> here as a maintainer so I don't see an issue with maintaining the binding.
>
> It's the whole pin configuration of an SoC squashed under a single
> document. I guess this is the fate of the pinctrl bindings. The bindings
> for mt7622 is not so different:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/pinctrl/mediatek%2Cmt7622-pinctrl.yaml#n63
It's much smaller number of if:then: than yours but if you want to
manage it then sure:
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Best regards,
Krzysztof
Powered by blists - more mailing lists