[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210110190529.46135-1-tony@atomide.com>
Date: Sun, 10 Jan 2021 21:05:24 +0200
From: Tony Lindgren <tony@...mide.com>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-omap@...r.kernel.org,
Arthur Demchenkov <spinal.by@...il.com>,
Carl Philipp Klemm <philipp@...s.xyz>,
Merlijn Wajer <merlijn@...zup.org>,
Pavel Machek <pavel@....cz>,
Sebastian Reichel <sre@...nel.org>, ruleh <ruleh@....de>
Subject: [PATCHv5 0/5] Lost key-up interrupt handling for omap4-keypad
Hi,
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.
These are based on Linux next with the following pending patch applied:
"Input: omap4-keypad - switch to use managed resources"
Regards,
Tony
Changes since v4:
- Rebase on Dmitry's devm patch
- Fix up kernel test robot warnings and mismerge of pm_ops when
I rebased from v5.10 to Linux next
- Split up the patches further as suggested by Dmitry
Changes since v3:
- Use PM runtime to check the last pressed key is not stuck
- Simplify probe with devm
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 (5):
Input: omap4-keypad - disable unused long interrupts
Input: omap4-keypad - scan keys in two phases and simplify with
bitmask
Input: omap4-keypad - move rest of key scanning to a separate function
Input: omap4-keypad - use PM runtime autosuspend
Input: omap4-keypad - implement errata check for lost key-up events
drivers/input/keyboard/omap4-keypad.c | 172 ++++++++++++++++++++------
1 file changed, 132 insertions(+), 40 deletions(-)
--
2.30.0
Powered by blists - more mailing lists