From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org
Subject: [PATCH] dt-bindings: input: gpio-keys: allow generic 'interrupt-parent' for subnodes
Date: Fri, 27 Sep 2024 10:15:04 +0200 [thread overview]
Message-ID: <20240927081757.7022-2-wsa+renesas@sang-engineering.com> (raw)
Allow interrupt-parent in the main node, so it can be inherited to all
subnodes. This is more compact and less error-prone.
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
---
It would fix dtbs_check for arch/arm/boot/dts/renesas/r8a7779-marzen.dts
and would simplify arch/arm/boot/dts/renesas/r7s72100-rskrza1.dts.
Plus, it is the behaviour I would expect.
Documentation/devicetree/bindings/input/gpio-keys.yaml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/input/gpio-keys.yaml b/Documentation/devicetree/bindings/input/gpio-keys.yaml
index cc78c2152921..8fc331e01f7e 100644
--- a/Documentation/devicetree/bindings/input/gpio-keys.yaml
+++ b/Documentation/devicetree/bindings/input/gpio-keys.yaml
@@ -15,6 +15,9 @@ properties:
- gpio-keys
- gpio-keys-polled
+ interrupt-parent:
+ description: Common interrupt parent for the following subnodes
+
autorepeat: true
label:
--
2.45.2
next reply other threads:[~2024-09-27 8:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 8:15 Wolfram Sang [this message]
2024-09-27 8:30 ` [PATCH] dt-bindings: input: gpio-keys: allow generic 'interrupt-parent' for subnodes Krzysztof Kozlowski
2024-09-27 8:42 ` Wolfram Sang
2024-09-27 9:09 ` Geert Uytterhoeven
2024-09-27 21:27 ` Dmitry Torokhov
2024-09-28 7:26 ` Krzysztof Kozlowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240927081757.7022-2-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).