[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7ik5zbqqveaysyruxpipvzuugabzomu2egr74yfl7avg75qyjk@j2rgeu72s7sy>
Date: Wed, 12 Jul 2023 18:50:05 +0300
From: Serge Semin <fancer.lancer@...il.com>
To: Andy Shevchenko <andy@...nel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Hoan Tran <hoan@...amperecomputing.com>,
Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <brgl@...ev.pl>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>, linux-gpio@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: gpio: snps,dw-apb: allow gpio-line-names
On Wed, Jul 12, 2023 at 06:28:40PM +0300, Andy Shevchenko wrote:
> On Wed, Jul 12, 2023 at 12:53:00PM +0300, Serge Semin wrote:
> > On Wed, Jul 12, 2023 at 09:45:53AM +0200, Krzysztof Kozlowski wrote:
> > > Allow the GPIO controller subnode to define GPIO names.
>
> Are we going to do this for each GPIO controller bindings? Can it be done once
> for all please?
AFAIU the DT-binding schemas which have "unevaluatedProperties: false"
property specified won't have such problem since any DT property with
"*-names" is already evaluated by the dt-validate core. Meanwhile in
this case the schema has "additionalProperties: false" property which
prohibits any none-explicitly defined property in the node.
Regarding the "gpio-line-names" DT-property constraints. Alas it can't
be done generically because at least a number of items is device
specific.
-Serge(y)
>
> --
> With Best Regards,
> Andy Shevchenko
>
>
Powered by blists - more mailing lists