From: Jon Dowland <jmtd@debian.org>
To: Azael Avalos <coproscefalo@gmail.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Matthew Garrett <mjg@redhat.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] toshiba_acpi.c: Add key_entry for a lone FN keypress
Date: Tue, 26 Oct 2010 13:06:19 +0100 [thread overview]
Message-ID: <20101026120619.GB27720@deckard.alcopop.org> (raw)
In-Reply-To: <AANLkTikcnJQnWYP+BTpUAvizU1iwwUo4=Nabe0L6xMXa@mail.gmail.com>
On Mon, Oct 25, 2010 at 12:42:41PM -0600, Azael Avalos wrote:
> It actually generates on key press/release with different key codes,
> 0x17f and 0x100 respectively. So I think that both should be added.
Presently the driver ignores key release events and only deals with key
presses. It also filters out a 0x100 value specifically in the event
handler. Do you mean something like this (untested)?
--- toshiba_acpi.c~ 2010-10-26 12:56:46.000000000 +0100
+++ toshiba_acpi.c 2010-10-26 13:04:42.000000000 +0100
@@ -123,6 +123,7 @@
MODULE_DEVICE_TABLE(acpi, toshiba_device_ids);
static const struct key_entry toshiba_acpi_keymap[] __initconst = {
+ { KE_KEY, 0x100, { KEY_FN } }, /* up */
{ KE_KEY, 0x101, { KEY_MUTE } },
{ KE_KEY, 0x102, { KEY_ZOOMOUT } },
{ KE_KEY, 0x103, { KEY_ZOOMIN } },
@@ -135,6 +136,7 @@
{ KE_KEY, 0x141, { KEY_BRIGHTNESSUP } },
{ KE_KEY, 0x142, { KEY_WLAN } },
{ KE_KEY, 0x143, { KEY_PROG1 } },
+ { KE_KEY, 0x17f, { KEY_FN } }, /* down */
{ KE_KEY, 0xb05, { KEY_PROG2 } },
{ KE_KEY, 0xb06, { KEY_WWW } },
{ KE_KEY, 0xb07, { KEY_MAIL } },
@@ -854,8 +856,6 @@
do {
hci_read1(HCI_SYSTEM_EVENT, &value, &hci_result);
if (hci_result == HCI_SUCCESS) {
- if (value == 0x100)
- continue;
/* act on key press; ignore key release */
if (value & 0x80)
continue;
next prev parent reply other threads:[~2010-10-26 12:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-23 22:12 Jon Dowland
2010-10-25 18:27 ` Dmitry Torokhov
2010-10-25 18:42 ` Azael Avalos
2010-10-26 12:06 ` Jon Dowland [this message]
2010-10-26 12:00 ` Jon Dowland
2010-10-26 15:56 ` Dmitry Torokhov
2010-10-26 23:24 ` Jon Dowland
2010-11-24 16:48 ` Matthew Garrett
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=20101026120619.GB27720@deckard.alcopop.org \
--to=jmtd@debian.org \
--cc=coproscefalo@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=platform-driver-x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome