From: Darren Hart <dvhart@infradead.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: "Pali Rohár" <pali.rohar@gmail.com>,
"Andy Lutomirski" <luto@kernel.org>,
platform-driver-x86@vger.kernel.org,
"Mario Limonciello" <mario_limonciello@dell.com>,
"Matthew Garrett" <mjg59@srcf.ucam.org>,
"Linux ACPI" <linux-acpi@vger.kernel.org>,
"Jon Eyolfson" <jon@eyl.io>
Subject: Re: [PATCH v4] dell-wmi: Support new hotkeys on the XPS 13 9350 (Skylake)
Date: Thu, 21 Jan 2016 13:57:42 -0800 [thread overview]
Message-ID: <20160121215742.GH1979@malice.jf.intel.com> (raw)
In-Reply-To: <CALCETrUqH7FLPyHasx020vyjZNtTdVSk+0LJKcGjXyj+iwE8Dw@mail.gmail.com>
On Wed, Jan 20, 2016 at 12:46:23PM -0800, Andy Lutomirski wrote:
> On Wed, Jan 20, 2016 at 11:40 AM, Pali Rohár <pali.rohar@gmail.com> wrote:
> > On Tuesday 19 January 2016 15:07:47 Andy Lutomirski wrote:
> >> The XPS 13 9350 sends WMI keypress events that aren't enumerated in
> >> the DMI table. Add a table listing them. To avoid breaking things
> >> that worked before, these un-enumerated hotkeys won't be used if the
> >> DMI table maps them to something else.
> >>
> >> FWIW, it appears that the DMI table may be a legacy thing and we
> >> might want to rethink how we handle events in general. As an
> >> example, a whole lot of things map to KEY_PROG3 via the DMI table.
> >>
> >> So far, this doesn't send keypress events for any of the new
> >> events. Depnding on whether we figure out exactly what needs to
> >> happen to get the wireless button working in time for Linux 4.5,
> >> we might want to temporarily handle it in dell-wmi.
> >>
> >> Signed-off-by: Andy Lutomirski <luto@kernel.org>
> >
> > Looks good,
> >
> > Reviewed-by: Pali Rohár <pali.rohar@gmail.com>
>
> Darren, if/when you apply this, can you fix up the last paragraph of
> the commit message?
>
> This doesn't send keypress events for any of the new
> events, as no models appear to require it.
>
> I wrote the old text before intel-hid landed.
Planning on queueing for 4.6 as soon as this window closes, likely tomorrow. I
want this to have some time in -next. Thanks!
>
> --Andy
>
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2016-01-21 21:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 23:07 [PATCH v4] dell-wmi: Support new hotkeys on the XPS 13 9350 (Skylake) Andy Lutomirski
2016-01-20 19:40 ` Pali Rohár
2016-01-20 20:46 ` Andy Lutomirski
2016-01-21 21:57 ` Darren Hart [this message]
2016-01-30 17:04 ` Darren Hart
2016-01-30 17:17 ` Andy Lutomirski
2016-01-30 17:45 ` Darren Hart
2016-01-30 17:56 ` Darren Hart
2016-01-30 17:58 ` Andy Lutomirski
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=20160121215742.GH1979@malice.jf.intel.com \
--to=dvhart@infradead.org \
--cc=jon@eyl.io \
--cc=linux-acpi@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=mario_limonciello@dell.com \
--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;
as well as URLs for NNTP newsgroup(s).