X86 platform drivers
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Andy Lutomirski <luto@kernel.org>
Cc: 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>,
	Darren Hart <dvhart@infradead.org>, Jon Eyolfson <jon@eyl.io>
Subject: Re: [PATCH v4] dell-wmi: Support new hotkeys on the XPS 13 9350 (Skylake)
Date: Wed, 20 Jan 2016 20:40:50 +0100	[thread overview]
Message-ID: <20160120194050.GL7192@pali> (raw)
In-Reply-To: <a343d7d11816d86d04c51505f6e33c5b99086ff6.1453244706.git.luto@kernel.org>

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>

> ---
> 
> This applies after the dmi-walk fix.
> 
> Notes:
>     Changes from v3:
>      - Rebase in top of interface version stuff.  (This changes context
>        but not any diff lines.)
>     Changes from v2:
>      - Factor check for already-known scancodes into a helper.
>      - Un-abbreviate comments.
>      - Fix off-by-one.
>      - Rebase on top of of dmi_walk fixes.
>     
>     Changes from v1:
>      - The new hotkey code matches reality better.
>      - Don't send key events for the new hotkeys.
> 
> drivers/platform/x86/dell-wmi.c | 71 +++++++++++++++++++++++++++++++++++++----
>  1 file changed, 64 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/platform/x86/dell-wmi.c b/drivers/platform/x86/dell-wmi.c
> index 3e30f77b70e1..afb7150bf2c1 100644
> --- a/drivers/platform/x86/dell-wmi.c
> +++ b/drivers/platform/x86/dell-wmi.c
> @@ -168,6 +168,30 @@ static const u16 bios_to_linux_keycode[256] __initconst = {
>  	[255]	= KEY_PROG3,
>  };
>  
> +/*
> + * These are applied if the 0xB2 DMI hotkey table is present and doesn't
> + * override them.
> + */
> +static const struct key_entry dell_wmi_extra_keymap[] __initconst = {
> +	/* Fn-lock */
> +	{ KE_IGNORE, 0x151, { KEY_RESERVED } },
> +
> +	/* Change keyboard illumination */
> +	{ KE_IGNORE, 0x152, { KEY_KBDILLUMTOGGLE } },
> +
> +	/*
> +	 * Radio disable (notify only -- there is no model for which the
> +	 * WMI event is supposed to trigger an action).
> +	 */
> +	{ KE_IGNORE, 0x153, { KEY_RFKILL } },
> +
> +	/* RGB keyboard backlight control */
> +	{ KE_IGNORE, 0x154, { KEY_RESERVED } },
> +
> +	/* Stealth mode toggle */
> +	{ KE_IGNORE, 0x155, { KEY_RESERVED } },
> +};
> +
>  static struct input_dev *dell_wmi_input_dev;
>  
>  static void dell_wmi_process_key(int reported_key)
> @@ -339,13 +363,27 @@ static void dell_wmi_notify(u32 value, void *context)
>  	kfree(obj);
>  }
>  
> +static bool have_scancode(u32 scancode, const struct key_entry *keymap, int len)
> +{
> +	int i;
> +
> +	for (i = 0; i < len; i++)
> +		if (keymap[i].code == scancode)
> +			return true;
> +
> +	return false;
> +}
> +
>  static void __init handle_dmi_entry(const struct dmi_header *dm,
> +
>  				    void *opaque)
> +
>  {
>  	struct dell_dmi_results *results = opaque;
>  	struct dell_bios_hotkey_table *table;
> +	int hotkey_num, i, pos = 0;
>  	struct key_entry *keymap;
> -	int hotkey_num, i;
> +	int num_bios_keys;
>  
>  	if (results->err || results->keymap)
>  		return;		/* We already found the hotkey table. */
> @@ -369,7 +407,8 @@ static void __init handle_dmi_entry(const struct dmi_header *dm,
>  		return;
>  	}
>  
> -	keymap = kcalloc(hotkey_num + 1, sizeof(struct key_entry), GFP_KERNEL);
> +	keymap = kcalloc(hotkey_num + ARRAY_SIZE(dell_wmi_extra_keymap) + 1,
> +			 sizeof(struct key_entry), GFP_KERNEL);
>  	if (!keymap) {
>  		results->err = -ENOMEM;
>  		return;
> @@ -397,14 +436,32 @@ static void __init handle_dmi_entry(const struct dmi_header *dm,
>  		}
>  
>  		if (keycode == KEY_KBDILLUMTOGGLE)
> -			keymap[i].type = KE_IGNORE;
> +			keymap[pos].type = KE_IGNORE;
>  		else
> -			keymap[i].type = KE_KEY;
> -		keymap[i].code = bios_entry->scancode;
> -		keymap[i].keycode = keycode;
> +			keymap[pos].type = KE_KEY;
> +		keymap[pos].code = bios_entry->scancode;
> +		keymap[pos].keycode = keycode;
> +
> +		pos++;
> +	}
> +
> +	num_bios_keys = pos;
> +
> +	for (i = 0; i < ARRAY_SIZE(dell_wmi_extra_keymap); i++) {
> +		const struct key_entry *entry = &dell_wmi_extra_keymap[i];
> +
> +		/*
> +		 * Check if we've already found this scancode.  This takes
> +		 * quadratic time, but it doesn't matter unless the list
> +		 * of extra keys gets very long.
> +		 */
> +		if (!have_scancode(entry->code, keymap, num_bios_keys)) {
> +			keymap[pos] = *entry;
> +			pos++;
> +		}
>  	}
>  
> -	keymap[hotkey_num].type = KE_END;
> +	keymap[pos].type = KE_END;
>  
>  	results->keymap = keymap;
>  }

-- 
Pali Rohár
pali.rohar@gmail.com

  reply	other threads:[~2016-01-20 19:40 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 [this message]
2016-01-20 20:46   ` Andy Lutomirski
2016-01-21 21:57     ` Darren Hart
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=20160120194050.GL7192@pali \
    --to=pali.rohar@gmail.com \
    --cc=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=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