From: Darren Hart <dvhart@infradead.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "Kai-Heng Feng" <kai.heng.feng@canonical.com>,
"Matthew Garrett" <mjg59@srcf.ucam.org>,
"Pali Rohár" <pali.rohar@gmail.com>,
"Andy Shevchenko" <andy@infradead.org>,
"Platform Driver" <platform-driver-x86@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND] [PATCH] platform/x86: dell-wmi: Ignore new rfkill and fn-lock events
Date: Fri, 1 Jun 2018 09:47:06 -0700 [thread overview]
Message-ID: <20180601164706.GA3599@localhost.localdomain> (raw)
In-Reply-To: <CAHp75VfpgejvwBZhy5UEzOFH8mMUQ+gXO_WTSa3D0Kip1ve8=g@mail.gmail.com>
On Fri, Jun 01, 2018 at 11:20:39AM +0300, Andy Shevchenko wrote:
> On Fri, Jun 1, 2018 at 6:23 AM, Kai-Heng Feng
> <kai.heng.feng@canonical.com> wrote:
> > There are two new events generated by dell-wmi, rfkill and fn-lock, from
> > Dell Systems.
> >
> > When Fn-lock hotkey gets pressed to switch to function mode:
> > [85951.591542] dell_wmi: Unknown key with type 0x0010 and code 0xe035
> > pressed
> > [85951.591546] dell_wmi: Unknown key with type 0x0010 and code 0x0000
> > pressed
> >
> > When Fn-lock hotkey gets pressed to switch to multimedia mode:
> > [85956.667686] dell_wmi: Unknown key with type 0x0010 and code 0xe035
> > pressed
> > [85956.667690] dell_wmi: Unknown key with type 0x0010 and code 0x0001
> > pressed
> >
> > When radio hotkey gets pressed:
> > [85974.430220] dell_wmi: Unknown key with type 0x0010 and code 0xe008
> > pressed
> >
> > These events are for notification purpose, so we can ignore them.
> >
> > This patch is tested on XPS 9370.
> >
>
> Pushed to my review and testing queue, thanks!
>
> P.S. There are some patches under Darren's queue, but for some reason
> didn't processed yet.
Thanks for getting this one Andy. I'm traveling, but am working through these
currently. I'll assume you are handling this one.
--
Darren Hart
VMware Open Source Technology Center
next prev parent reply other threads:[~2018-06-01 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 3:23 [RESEND] [PATCH] platform/x86: dell-wmi: Ignore new rfkill and fn-lock events Kai-Heng Feng
2018-06-01 8:20 ` Andy Shevchenko
2018-06-01 16:47 ` Darren Hart [this message]
2018-06-02 14:09 ` Andy Shevchenko
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=20180601164706.GA3599@localhost.localdomain \
--to=dvhart@infradead.org \
--cc=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=pali.rohar@gmail.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