[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2f49aa26-23f7-833c-b01d-9dfb2603603c@linaro.org>
Date: Tue, 24 May 2022 13:28:24 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Andreas Kemnade <andreas@...nade.info>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Jeff LaBundy <jeff@...undy.com>, linux-input@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: input: use generic node names
On 24/05/2022 13:11, Andreas Kemnade wrote:
> Hi,
>
> On Tue, 24 May 2022 11:31:36 +0200
> Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org> wrote:
>
>> diff --git a/Documentation/devicetree/bindings/input/gpio-keys.yaml b/Documentation/devicetree/bindings/input/gpio-keys.yaml
>> index 7fe1966ea28a..93f601c58984 100644
>> --- a/Documentation/devicetree/bindings/input/gpio-keys.yaml
>> +++ b/Documentation/devicetree/bindings/input/gpio-keys.yaml
>> @@ -127,13 +127,13 @@ examples:
>> compatible = "gpio-keys";
>> autorepeat;
>>
>> - up {
>> + key-up {
>> label = "GPIO Key UP";
>> linux,code = <103>;
>> gpios = <&gpio1 0 1>;
>> };
>>
>> - down {
>> + key-down {
>> label = "GPIO Key DOWN";
>> linux,code = <108>;
>> interrupts = <1 IRQ_TYPE_EDGE_FALLING>;
> hmm, what about changing
> patternProperties:
> ".*":
>
> to enforce this format instead of allowing anything?
It will cause a lot, a lot of warnings, so first these would need to be
fixed in every DTS. That's also doable, might help if these gpio-keys
bindings need any other object like property.
Best regards,
Krzysztof
Powered by blists - more mailing lists