From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh+dt@kernel.org>, Marc Zyngier <maz@kernel.org>
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/3] Input: gpio-keys - Interrupt-related fixes
Date: Fri, 3 Dec 2021 14:35:05 +0100 [thread overview]
Message-ID: <cover.1638538079.git.geert+renesas@glider.be> (raw)
Hi all,
This patch series contains two interrupt-related fixes for the gpio-keys
DT bindings and driver, and a small clean-up.
The first two patches can be applied independently.
The third patch, which is marked RFC, depends on the second.
Thanks for your comments!
Geert Uytterhoeven (3):
dt-bindings: input: gpio-keys: Fix interrupts in example
Input: gpio-keys - Use input_report_key()
[WIP] [RFC] Input: gpio-keys - Fix ghost events with both-edge irqs
.../devicetree/bindings/input/gpio-keys.yaml | 2 +-
drivers/input/keyboard/gpio_keys.c | 38 ++++++++++++-------
2 files changed, 25 insertions(+), 15 deletions(-)
--
2.25.1
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2021-12-03 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 13:35 Geert Uytterhoeven [this message]
2021-12-03 13:35 ` [PATCH 1/3] dt-bindings: input: gpio-keys: Fix interrupts in example Geert Uytterhoeven
2021-12-06 20:17 ` Rob Herring
2021-12-03 13:35 ` [PATCH 2/3] Input: gpio-keys - Use input_report_key() Geert Uytterhoeven
2021-12-03 13:35 ` [PATCH RFC 3/3] Input: gpio-keys - Fix ghost events with both-edge irqs Geert Uytterhoeven
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=cover.1638538079.git.geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=maz@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).