[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220603101601.542054-1-krzysztof.kozlowski@linaro.org>
Date: Fri, 3 Jun 2022 12:15:59 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
linux-input@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: Stefan Hansson <newbie13xd@...il.com>,
Andreas Kemnade <andreas@...nade.info>,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Subject: [RFC PATCH 0/2] dt-bindings: input: gpio-keys: rework matching children
Hi,
Currently the gpio-keys schema allows any property to be present, even
undocumented. Narrow the pattern for children to require specific key naming like:
gpio-keys {
compatible = "gpio-keys";
// "up" is wrong
key-up {
label = "GPIO Key UP";
linux,code = <103>;
gpios = <&gpio1 0 1>;
};
};
This will cause many, many DTS warnings, which I can fix. But before I start
such big work, let's agree whether the approach is correct.
Best regards,
Krzysztof
Krzysztof Kozlowski (2):
dt-bindings: input: gpio-keys: enforce node names to match all
properties
dt-bindings: input: gpio-keys: document label and autorepeat
properties
.../devicetree/bindings/input/gpio-keys.yaml | 177 +++++++++---------
1 file changed, 91 insertions(+), 86 deletions(-)
--
2.34.1
Powered by blists - more mailing lists