From: akpm@linux-foundation.org
To: jkosina@suse.cz, mm-commits@vger.kernel.org
Subject: - input-fix-hp-2133-not-sending-release-event-for-video-switch.patch removed from -mm tree
Date: Wed, 02 Jul 2008 00:47:47 -0700 [thread overview]
Message-ID: <200807020747.m627llKJ005677@imap1.linux-foundation.org> (raw)
The patch titled
input: fix HP 2133 not sending release event for video switch
has been removed from the -mm tree. Its filename was
input-fix-hp-2133-not-sending-release-event-for-video-switch.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: input: fix HP 2133 not sending release event for video switch
From: Jiri Kosina <jkosina@suse.cz>
Video switch key on HP 2133 doesn't send release event, so we have to
create workaround similar to what we do for Dell Latitude, i.e. perform
DMI match for the system and generate 'false' release event ourselves, so
that userspace doesn't think that the key is stuck forever.
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/input/keyboard/atkbd.c | 26 ++++++++++++++++++++++++++
1 file changed, 26 insertions(+)
diff -puN drivers/input/keyboard/atkbd.c~input-fix-hp-2133-not-sending-release-event-for-video-switch drivers/input/keyboard/atkbd.c
--- a/drivers/input/keyboard/atkbd.c~input-fix-hp-2133-not-sending-release-event-for-video-switch
+++ a/drivers/input/keyboard/atkbd.c
@@ -851,6 +851,23 @@ static void atkbd_latitude_keymap_fixup(
}
/*
+ * Perform fixup for HP system that doesn't generate release
+ * for its video switch
+ */
+static void atkbd_hp_keymap_fixup(struct atkbd *atkbd)
+{
+ const unsigned int forced_release_keys[] = {
+ 0x94,
+ };
+ int i;
+
+ if (atkbd->set == 2)
+ for (i = 0; i < ARRAY_SIZE(forced_release_keys); i++)
+ __set_bit(forced_release_keys[i],
+ atkbd->force_release_mask);
+}
+
+/*
* atkbd_set_keycode_table() initializes keyboard's keycode table
* according to the selected scancode set
*/
@@ -1452,6 +1469,15 @@ static struct dmi_system_id atkbd_dmi_qu
.callback = atkbd_setup_fixup,
.driver_data = atkbd_latitude_keymap_fixup,
},
+ {
+ .ident = "HP 2133",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "Hewlett-Packard"),
+ DMI_MATCH(DMI_PRODUCT_NAME, "HP 2133"),
+ },
+ .callback = atkbd_setup_fixup,
+ .driver_data = atkbd_hp_keymap_fixup,
+ },
{ }
};
_
Patches currently in -mm which might be from jkosina@suse.cz are
linux-next.patch
elantech-touchpad-driver.patch
input-touchscreen-driver-add-support-ad7877-touchscreen-driver.patch
ds1302-push-down-the-bkl-into-the-driver-ioctl-code.patch
reply other threads:[~2008-07-02 7:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200807020747.m627llKJ005677@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@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.