All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <mario_limonciello@dell.com>
To: "Pali Rohár" <pali.rohar@gmail.com>, "Andy Lutomirski" <luto@kernel.org>
Cc: "platform-driver-x86@vger.kernel.org"
	<platform-driver-x86@vger.kernel.org>,
	Darren Hart <dvhart@infradead.org>, Jon Eyolfson <jon@eyl.io>,
	Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: [PATCH v5 5/5] dell-rbtn: Add a comment about the XPS 13 9350
Date: Wed, 17 Feb 2016 07:07:28 -0600	[thread overview]
Message-ID: <56C47090.1050106@dell.com> (raw)
In-Reply-To: <20160217111634.GQ1476@pali>



On 02/17/2016 05:16 AM, Pali Rohár wrote:
> On Monday 15 February 2016 08:32:37 Andy Lutomirski wrote:
>> On the XPS 13 9350, the dell-rbtn mechanism has a new device id, and
>> the DSDT turns it off if a new enough _OSI is supported.  Add a
>> comment about why we don't bother supporting it.
>>
>> Signed-off-by: Andy Lutomirski <luto@kernel.org>
>> ---
>>  drivers/platform/x86/dell-rbtn.c | 15 +++++++++++++++
>>  1 file changed, 15 insertions(+)
>>
>> diff --git a/drivers/platform/x86/dell-rbtn.c b/drivers/platform/x86/dell-rbtn.c
>> index cd410e392550..b51a2008d782 100644
>> --- a/drivers/platform/x86/dell-rbtn.c
>> +++ b/drivers/platform/x86/dell-rbtn.c
>> @@ -217,6 +217,21 @@ static void rbtn_notify(struct acpi_device *device, u32 event);
>>  static const struct acpi_device_id rbtn_ids[] = {
>>  	{ "DELRBTN", 0 },
>>  	{ "DELLABCE", 0 },
>> +
>> +	/*
>> +	 * This driver can also handle the "DELLABC6" device that
>> +	 * appears on the XPS 13 9350, but that device is disabled
>> +	 * by the DSDT unless booted with acpi_osi="!Windows 2012"
>> +	 * acpi_osi="!Windows 2013".  Even if we boot that and bind
>> +	 * the driver, we seem to have inconsistent behavior in
>> +	 * which NetworkManager can get out of sync with the rfkill
>> +	 * state.
> Do you know reason for such behaviour? It is because event is send
> duplicated (by dell-rbtn and also by intel-hid)?
DELLABC6 is a custom interface that was created solely to have airplane
mode support for Windows 7. 
For Windows 10 the proper interface is to use that which is handled by
intel-hid.  A OEM airplane mode driver is not used.

Since the kernel doesn't identify as Windows 7 it would be incorrect to
do attempt to use that interface.
>> +	 * On the XPS 13 9350 and similar laptops, we're not supposed to
>> +	 * use DELLABC6 at all.  Instead, we handle the rfkill button
>> +	 * via the intel-hid driver.
>> +	 */
>> +
>>  	{ "", 0 },
>>  };
>>  

  reply	other threads:[~2016-02-17 13:11 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-15 16:32 [PATCH v5 0/5] dell fixes and Skylake updates Andy Lutomirski
2016-02-15 16:32 ` [PATCH v5 1/5] dell-wmi: Stop storing pointers to DMI tables Andy Lutomirski
2016-02-17  6:37   ` Darren Hart
2016-02-17  7:04     ` Darren Hart
2016-02-15 16:32 ` [PATCH v5 2/5] dell-wmi, dell-laptop: select DMI Andy Lutomirski
2016-02-17  6:39   ` Darren Hart
2016-02-17 20:32     ` Andy Lutomirski
2016-02-15 16:32 ` [PATCH v5 3/5] dell-wmi: Clean up hotkey table size check Andy Lutomirski
2016-02-17  6:46   ` Darren Hart
2016-02-15 16:32 ` [PATCH v5 4/5] dell-wmi: Support new hotkeys on the XPS 13 9350 (Skylake) Andy Lutomirski
2016-02-15 17:20   ` Pali Rohár
2016-02-15 17:26     ` Mario Limonciello
2016-02-15 17:37       ` Pali Rohár
2016-02-17  7:29         ` Darren Hart
2016-02-17 11:19           ` Pali Rohár
2016-02-15 16:32 ` [PATCH v5 5/5] dell-rbtn: Add a comment about the XPS 13 9350 Andy Lutomirski
2016-02-17 11:16   ` Pali Rohár
2016-02-17 13:07     ` Mario Limonciello [this message]
2016-02-23 12:01       ` Pali Rohár
2016-02-23 17:35         ` Andy Lutomirski
2016-02-23 17:42           ` Mario Limonciello
2016-02-25 10:45           ` Pali Rohár
2016-02-26 20:13             ` Darren Hart
2016-02-17  7:00 ` [PATCH v5 0/5] dell fixes and Skylake updates Darren Hart
2016-02-17 20:33   ` Andy Lutomirski
2016-02-18  5:03     ` Darren Hart

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=56C47090.1050106@dell.com \
    --to=mario_limonciello@dell.com \
    --cc=dvhart@infradead.org \
    --cc=jon@eyl.io \
    --cc=luto@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.