From: Azael Avalos <coproscefalo@gmail.com>
To: Darren Hart <dvhart@infradead.org>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Azael Avalos <coproscefalo@gmail.com>
Subject: [PATCH v2 0/3] toshiba_acpi: Hotkey handling and keymap updates
Date: Fri, 20 Mar 2015 16:55:15 -0600 [thread overview]
Message-ID: <1426892118-27678-1-git-send-email-coproscefalo@gmail.com> (raw)
These patches add support to a new function that queries the supported Hotkey
Event Type, making the use of the DMI matching unnecessary and also fixes
the "Special Functions" mode on some laptops.
Changes since v1:
- Renamed HCI_HOTKEY_EVENT_TYPE to HCI_SYSTEM_INFO definition to
better reflect what the call does, and also the HCI_HOTKEY_EVENT_*
types
- Fixed a typo in the error description
- Added a comment block explaining a bit why we also use the "Special
Functions" as a check for keymap selection
Azael Avalos (3):
toshiba_acpi: Add Hotkey Event Type function and definitions
toshiba_acpi: Use the Hotkey Event Type function for keymap choosing
toshiba_acpi: Fix the enabling of the Special Functions
drivers/platform/x86/toshiba_acpi.c | 118 ++++++++++++++++++++++++------------
1 file changed, 80 insertions(+), 38 deletions(-)
--
2.2.2
next reply other threads:[~2015-03-20 22:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 22:55 Azael Avalos [this message]
2015-03-20 22:55 ` [PATCH v2 1/3] toshiba_acpi: Add Hotkey Event Type function and definitions Azael Avalos
2015-03-20 22:55 ` [PATCH v2 2/3] toshiba_acpi: Use the Hotkey Event Type function for keymap choosing Azael Avalos
2015-03-20 22:55 ` [PATCH v2 3/3] toshiba_acpi: Fix the enabling of the Special Functions Azael Avalos
2015-03-25 18:02 ` [PATCH v2 0/3] toshiba_acpi: Hotkey handling and keymap updates Darren Hart
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=1426892118-27678-1-git-send-email-coproscefalo@gmail.com \
--to=coproscefalo@gmail.com \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®