From: Arkadiusz (Arkq) Bokowy <arkadiusz.bokowy@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: [PATCH] atkbd: Samsung NP530U3C laptop forced key release
Date: Tue, 11 Mar 2014 19:54:48 +0100 [thread overview]
Message-ID: <20140311195448.0b722ea5@sambook> (raw)
atkbd: Samsung NP530U3C laptop forced key release
For Samsung NP530U3C laptop (observed on firmware P09ABH) not all Fn keys
generates release event, which leaves key in a pressed state. This patch
adds those keys into the "forced release" workaround. Fixed keys: WLAN,
Settings, Fn Lock.
Patch generated for kernel version 3.13.6
Signed-off-by: Arkadiusz Bokowy <arkadiusz.bokowy@gmail.com>
---
--- linux-3.13.6/drivers/input/keyboard/atkbd.c.orig 2014-03-07 07:07:02.000000000 +0100
+++ linux-3.13.6/drivers/input/keyboard/atkbd.c 2014-03-11 18:48:47.593211190 +0100
@@ -943,6 +943,13 @@ static unsigned int atkbd_samsung_forced
};
/*
+ * Samsung NP530U3C key release for WLAN, Settings and Fn Lock
+ */
+static unsigned int atkbd_samsung_np530_forced_release_keys[] = {
+ 0xa8, 0xa9, 0xce, 0xd5, -1U
+};
+
+/*
* Amilo Pi 3525 key release for Fn+Volume keys not working
*/
static unsigned int atkbd_amilo_pi3525_forced_release_keys[] = {
@@ -1732,6 +1739,15 @@ static const struct dmi_system_id atkbd_
.driver_data = atkbd_samsung_forced_release_keys,
},
{
+ /* Samsung NP530U3C */
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "SAMSUNG ELECTRONICS CO., LTD."),
+ DMI_MATCH(DMI_PRODUCT_NAME, "530U3C"),
+ },
+ .callback = atkbd_setup_forced_release,
+ .driver_data = atkbd_samsung_np530_forced_release_keys,
+ },
+ {
/* Fujitsu Amilo PA 1510 */
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "FUJITSU SIEMENS"),
next reply other threads:[~2014-03-11 18:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 18:54 Arkadiusz Bokowy [this message]
2014-03-28 7:48 ` [PATCH] atkbd: Samsung NP530U3C laptop forced key release Dmitry Torokhov
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=20140311195448.0b722ea5@sambook \
--to=arkadiusz.bokowy@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.