From: Darren Hart <dvhart@infradead.org>
To: Andy Lutomirski <luto@kernel.org>
Cc: "Pali Rohár" <pali.rohar@gmail.com>,
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 v3] dell-wmi: Support new hotkeys on the XPS 13 9350 (Skylake)
Date: Tue, 19 Jan 2016 14:50:07 -0800 [thread overview]
Message-ID: <20160119225007.GC3253@malice.jf.intel.com> (raw)
In-Reply-To: <54397d72fbadcc340ca3ef1339c1a62fe0a07ab8.1453151401.git.luto@kernel.org>
On Mon, Jan 18, 2016 at 01:14:58PM -0800, 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>
Hi Andy, what did you apply this against? It doesn't apply to my current
for-next, nor my rebased for-next.
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2016-01-19 22:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 21:14 [PATCH v3] dell-wmi: Support new hotkeys on the XPS 13 9350 (Skylake) Andy Lutomirski
2016-01-19 22:50 ` Darren Hart [this message]
2016-01-19 23:03 ` 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=20160119225007.GC3253@malice.jf.intel.com \
--to=dvhart@infradead.org \
--cc=jon@eyl.io \
--cc=linux-acpi@vger.kernel.org \
--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