From: "Pali Rohár" <pali.rohar@gmail.com>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: mjg59@srcf.ucam.org, dvhart@infradead.org, andy@infradead.org,
mario.limonciello@dell.com, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: dell-wmi: Ignore new rfkill and fn-lock events
Date: Thu, 19 Apr 2018 09:46:45 +0200 [thread overview]
Message-ID: <20180419074645.p47cevwpzwwak3sk@pali> (raw)
In-Reply-To: <20180419072449.4514-1-kai.heng.feng@canonical.com>
On Thursday 19 April 2018 15:24:49 Kai-Heng Feng wrote:
> There are two new events generated by dell-wmi, rfkill and fn-lock, from
> Dell Systems.
>
> These events are for notification purpose, so we can ignore them.
>
> Tested on XPS 9370.
>
> Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
> ---
> I ordered them functionally instead of alphabetically, I can re-order
> them to alphabetically if that's more diserable.
Please order them by event code like they were prior your change.
> drivers/platform/x86/dell-wmi.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/platform/x86/dell-wmi.c b/drivers/platform/x86/dell-wmi.c
> index 8d102195a392..51d2845d2ad9 100644
> --- a/drivers/platform/x86/dell-wmi.c
> +++ b/drivers/platform/x86/dell-wmi.c
> @@ -266,6 +266,13 @@ static const struct key_entry dell_wmi_keymap_type_0010[] = {
>
> /* Fn-lock */
> { KE_IGNORE, 0x151, { KEY_RESERVED } },
> + { KE_IGNORE, 0xe035, { KEY_RESERVED } },
> +
> + /* Fn-lock switched to function keys */
> + { KE_IGNORE, 0x0000, { KEY_RESERVED } },
> +
> + /* Fn-lock switched to multimedia keys */
> + { KE_IGNORE, 0x0001, { KEY_RESERVED } },
Are you sure that all those codes are not defined in 0xB2 DMI hotkey
table? Also is Fn-lock key reported by PS/2 AT Keyboard controller so it
is needed to ignored it by WMI?
> /* Change keyboard illumination */
> { KE_IGNORE, 0x152, { KEY_KBDILLUMTOGGLE } },
> @@ -275,6 +282,7 @@ static const struct key_entry dell_wmi_keymap_type_0010[] = {
> * WMI event is supposed to trigger an action).
> */
> { KE_IGNORE, 0x153, { KEY_RFKILL } },
> + { KE_IGNORE, 0xe008, { KEY_RFKILL } },
>
> /* RGB keyboard backlight control */
> { KE_IGNORE, 0x154, { KEY_RESERVED } },
--
Pali Rohár
pali.rohar@gmail.com
next prev parent reply other threads:[~2018-04-19 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 7:24 Kai-Heng Feng
2018-04-19 7:46 ` Pali Rohár [this message]
2018-04-19 8:09 ` Kai Heng Feng
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=20180419074645.p47cevwpzwwak3sk@pali \
--to=pali.rohar@gmail.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@dell.com \
--cc=mjg59@srcf.ucam.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®