[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <8c454b54-98a7-492d-b861-83d125306f86@rwthex-w2-a.rwth-ad.de>
Date: Fri, 3 Nov 2017 20:03:26 +0100
From: Stefan Brüns <stefan.bruens@...h-aachen.de>
To: <platform-driver-x86@...r.kernel.org>
CC: Stefan Brüns <stefan.bruens@...h-aachen.de>,
"Dmitry Torokhov" <dmitry.torokhov@...il.com>,
<linux-kernel@...r.kernel.org>, <linux-input@...r.kernel.org>
Subject: [PATCH 1/4] Input: sparse-keymap - send sync event for KE_SW/KW_VSW
Sync events are sent by sparse_keymap_report_entry for normal KEY_*
events, and are generated by several drivers after generating
SW_* events, so sparse_keymap_report_entry should do the same.
Without the sync, events are accumulated in the kernel.
Currently, no driver uses sparse-keymap for SW_* events, but
it is required for the intel-vbtn platform driver to generate
SW_TABLET_MODE events.
Signed-off-by: Stefan Brüns <stefan.bruens@...h-aachen.de>
---
drivers/input/sparse-keymap.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/input/sparse-keymap.c b/drivers/input/sparse-keymap.c
index bb0349fa64bc..fd03e55768c9 100644
--- a/drivers/input/sparse-keymap.c
+++ b/drivers/input/sparse-keymap.c
@@ -255,6 +255,7 @@ void sparse_keymap_report_entry(struct input_dev *dev, const struct key_entry *k
case KE_VSW:
input_report_switch(dev, ke->sw.code, value);
+ input_sync(dev);
break;
}
}
--
2.14.3
Powered by blists - more mailing lists