From: Tony Lindgren <tony@atomide.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org,
Arthur Demchenkov <spinal.by@gmail.com>,
Merlijn Wajer <merlijn@wizzup.org>, Pavel Machek <pavel@ucw.cz>,
Sebastian Reichel <sre@kernel.org>, ruleh <ruleh@gmx.de>
Subject: [PATCHv3 0/3] Lost key-up interrupt handling for omap4-keypad
Date: Wed, 18 Mar 2020 15:57:24 -0700 [thread overview]
Message-ID: <20200318225727.29327-1-tony@atomide.com> (raw)
Hi all,
This series updates omap4-keypad to disable unused long interrupts, and
implements the missing parts for the lost key-up interrupt quirk as
described in the silicon errata pdf.
Regards,
Tony
Changes since v2:
- Drop bogus level change, that already comes from device tree
- Scan keyboard in two phases and simplify using a bitmask
- Use mod_delayed_work and cancel_delayed_work_sync for the quirk
Tony Lindgren (3):
Input: omap4-keypad - disable unused long interrupts
Input: omap4-keypad - Scan keys in two phases and simplify with
bitmask
Input: omap4-keypad - check state again for lost key-up interrupts
drivers/input/keyboard/omap4-keypad.c | 124 ++++++++++++++++++++------
1 file changed, 95 insertions(+), 29 deletions(-)
--
2.25.1
next reply other threads:[~2020-03-18 22:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 22:57 Tony Lindgren [this message]
2020-03-18 22:57 ` [PATCH 1/3] Input: omap4-keypad - disable unused long interrupts Tony Lindgren
2020-03-18 22:57 ` [PATCH 2/3] Input: omap4-keypad - Scan keys in two phases and simplify with bitmask Tony Lindgren
2020-03-18 22:57 ` [PATCH 3/3] Input: omap4-keypad - check state again for lost key-up interrupts Tony Lindgren
2020-09-08 8:52 ` [PATCHv3 0/3] Lost key-up interrupt handling for omap4-keypad Pavel Machek
2020-09-09 6:00 ` Tony Lindgren
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=20200318225727.29327-1-tony@atomide.com \
--to=tony@atomide.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=pavel@ucw.cz \
--cc=ruleh@gmx.de \
--cc=spinal.by@gmail.com \
--cc=sre@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).