From: <Mario.Limonciello@dell.com>
To: <hdegoede@redhat.com>, <dvhart@infradead.org>,
<andy@infradead.org>, <pali@kernel.org>, <mjg59@srcf.ucam.org>
Cc: <platform-driver-x86@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] platform/x86: dell-wmi: Ignore keyboard attached / detached events
Date: Wed, 13 May 2020 17:29:11 +0000 [thread overview]
Message-ID: <5242ea25f5c94a06beda838dba8c06ef@AUSX13MPC105.AMER.DELL.COM> (raw)
In-Reply-To: <20200513130544.90243-1-hdegoede@redhat.com>
> -----Original Message-----
> From: Hans de Goede <hdegoede@redhat.com>
> Sent: Wednesday, May 13, 2020 8:06 AM
> To: Darren Hart; Andy Shevchenko; Pali Rohár; Matthew Garrett
> Cc: Hans de Goede; Limonciello, Mario; platform-driver-x86@vger.kernel.org;
> linux-kernel@vger.kernel.org
> Subject: [PATCH] platform/x86: dell-wmi: Ignore keyboard attached / detached
> events
>
>
> [EXTERNAL EMAIL]
>
> Ignore events with a type of 0x0011 and a code of 0xfff2 / 0xfff3,
> this silences the following messages being logged when the keyboard is
> detached / attached on a Dell Venue 11 Pro 7130:
>
> [ 63.621953] dell_wmi: Unknown key with type 0x0011 and code 0xfff2 pressed
> [ 70.240558] dell_wmi: Unknown key with type 0x0011 and code 0xfff3 pressed
>
> Note SW_TABLET_MODE is already reported through the intel_vbtn driver on
> this and other Dell devices, so dell_wmi should not report this too,
> to avoid duplicate events.
If they didn't also come through on intel-vbtn I would have proposed that we
should have a separate tablet mode switch coming from dell-wmi too.
As a general note the reason for these is that the WMI architecture on Windows
differs in that applications typically directly receive the events and do things
with them.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> ---
> drivers/platform/x86/dell-wmi.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/platform/x86/dell-wmi.c b/drivers/platform/x86/dell-wmi.c
> index 86e8dd6a8b33..c25a4286d766 100644
> --- a/drivers/platform/x86/dell-wmi.c
> +++ b/drivers/platform/x86/dell-wmi.c
> @@ -310,6 +310,16 @@ static const struct key_entry dell_wmi_keymap_type_0011[]
> = {
> /* Battery inserted */
> { KE_IGNORE, 0xfff1, { KEY_RESERVED } },
>
> + /*
> + * Detachable keyboard detached / undocked
> + * Note SW_TABLET_MODE is already reported through the intel_vbtn
> + * driver for this, so we ignore it.
> + */
> + { KE_IGNORE, 0xfff2, { KEY_RESERVED } },
> +
> + /* Detachable keyboard attached / docked */
> + { KE_IGNORE, 0xfff3, { KEY_RESERVED } },
> +
> /* Keyboard backlight level changed */
> { KE_IGNORE, KBD_LED_OFF_TOKEN, { KEY_RESERVED } },
> { KE_IGNORE, KBD_LED_ON_TOKEN, { KEY_RESERVED } },
> --
> 2.26.0
Reviewed-by: Mario Limonciello <Mario.limonciello@dell.com>
next prev parent reply other threads:[~2020-05-13 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 13:05 Hans de Goede
2020-05-13 17:29 ` Mario.Limonciello [this message]
2020-05-19 17:51 ` Pali Rohár
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=5242ea25f5c94a06beda838dba8c06ef@AUSX13MPC105.AMER.DELL.COM \
--to=mario.limonciello@dell.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=pali@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®