From: Kieran Bingham <kieran.bingham@ideasonboard.com>
To: linux-renesas-soc@vger.kernel.org, Geert Uytterhoeven <geert@glider.be>
Cc: Kieran Bingham <kieran.bingham@ideasonboard.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
FLATTENED DEVICE TREE BINDINGS),
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH] arm64: dts: renesas: r8a779a0: falcon-cpu: Add SW46 switch support
Date: Wed, 22 Sep 2021 21:30:27 +0100 [thread overview]
Message-ID: <20210922203027.3229474-1-kieran.bingham@ideasonboard.com> (raw)
Add support for SW46-1 and SW46-2 as switches using the gpio-keys
framework.
Signed-off-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
---
SW_LID and SW_DOCK are selected as low-impact switch events for the
default configuration. Would SW_RFKILL_ALL, and SW_MUTE_DEVICE be
preferred as more 'functional' defaults? (I have otherwise avoided these
to hopefully prevent unwanted / undocumented effects occuring on
development hardware running a full interface which may parse these)
I'd expect them to be overridden by any platform using them anyway.
Testing of these switches (and the buttons) shown at:
https://paste.debian.net/1212884/
---
.../boot/dts/renesas/r8a779a0-falcon-cpu.dtsi | 21 ++++++++++++++++++-
1 file changed, 20 insertions(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/renesas/r8a779a0-falcon-cpu.dtsi b/arch/arm64/boot/dts/renesas/r8a779a0-falcon-cpu.dtsi
index d595fbad4589..5d188a7d6e73 100644
--- a/arch/arm64/boot/dts/renesas/r8a779a0-falcon-cpu.dtsi
+++ b/arch/arm64/boot/dts/renesas/r8a779a0-falcon-cpu.dtsi
@@ -52,6 +52,24 @@ keys {
pinctrl-0 = <&keys_pins>;
pinctrl-names = "default";
+ sw-1 {
+ gpios = <&gpio1 28 GPIO_ACTIVE_LOW>;
+ linux,code = <SW_LID>;
+ linux,input-type = <EV_SW>;
+ label = "SW46-1";
+ wakeup-source;
+ debounce-interval = <20>;
+ };
+
+ sw-2 {
+ gpios = <&gpio1 29 GPIO_ACTIVE_LOW>;
+ linux,code = <SW_DOCK>;
+ linux,input-type = <EV_SW>;
+ label = "SW46-2";
+ wakeup-source;
+ debounce-interval = <20>;
+ };
+
key-1 {
gpios = <&gpio6 18 GPIO_ACTIVE_LOW>;
linux,code = <KEY_1>;
@@ -193,7 +211,8 @@ i2c6_pins: i2c6 {
};
keys_pins: keys {
- pins = "GP_6_18", "GP_6_19", "GP_6_20";
+ pins = "GP_1_28", "GP_1_29",
+ "GP_6_18", "GP_6_19", "GP_6_20";
bias-pull-up;
};
--
2.30.2
next reply other threads:[~2021-09-22 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 20:30 Kieran Bingham [this message]
2021-09-23 7:32 ` Geert Uytterhoeven
2021-09-23 12:17 ` Kieran Bingham
2021-09-23 12:47 ` Geert Uytterhoeven
2021-10-25 12:50 ` Kieran Bingham
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=20210922203027.3229474-1-kieran.bingham@ideasonboard.com \
--to=kieran.bingham@ideasonboard.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh+dt@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
all inboxes | Powered by JetHome®