From: Darren Hart <dvhart@infradead.org>
To: Mario.Limonciello@dell.com
Cc: jeremy@jcline.org, notmart@gmail.com, pali.rohar@gmail.com,
andriy.shevchenko@linux.intel.com, mjg59@srcf.ucam.org,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Regression: Dell XPS 13 9360 keyboard no longer works
Date: Thu, 22 Feb 2018 11:50:00 -0800 [thread overview]
Message-ID: <20180222195000.GE19843@fury> (raw)
In-Reply-To: <88473a72368b43bdacebca279092ab0f@ausx13mpc120.AMER.DELL.COM>
On Thu, Feb 22, 2018 at 05:05:39PM +0000, Mario.Limonciello@dell.com wrote:
...
> OK thanks for confirming. Here's what I've concluded:
>
> * So looking through the ACPI tables on the 9360 it initializes that status
> (slate vs laptop mode) bit to "slate" mode. The 9360 isn't a 2-in1- so that
> seems wrong to me, but that's what it does.
> It only gets updated based on dock status.
>
> The 9365 (which is a 2 in 1) however seems to initialize the status properly.
>
> So that's an impasse of what to do.
> It's not clear to me what is really happening:
> a) We're missing something else in this driver (eg something else that
> indicates whether to trust VGBS output)
>
> b) Mis-interpreting the results from it (we shouldn't report the switch for
> tablet mode based on what we do)
>
> c) 9360 has a BIOS bug (seems unlikely since Windows doesn't freak out and
> show virtual keyboard at wrong time)
>
> I'm leaning on it's probably <a>.
> We should check for tablet mode should only be run if chassis type
> matches 2-in-1 (chassis type 0x1F).
This sounds like a good approach to me.
> I believe that should fix the problem on the 9360, let it continue to work on
> the 9365 (and other 2-in-1's).
>
> Can you guys please test this? If that works I'll split up the routine and submit
> it.
Queueing this up as well.
--
Darren Hart
VMware Open Source Technology Center
next prev parent reply other threads:[~2018-02-22 19:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 5:14 Regression: Dell XPS 13 9360 keyboard no longer works Jeremy Cline
2018-02-22 10:21 ` Marco Martin
2018-02-22 14:08 ` Jeremy Cline
2018-02-22 15:15 ` Marco Martin
2018-02-22 15:21 ` Mario.Limonciello
2018-02-22 15:58 ` Jeremy Cline
2018-02-22 16:14 ` Mario.Limonciello
2018-02-22 16:17 ` Jeremy Cline
2018-02-22 16:17 ` Mario.Limonciello
2018-02-22 16:42 ` Jeremy Cline
2018-02-22 17:05 ` Mario.Limonciello
2018-02-22 19:45 ` Jeremy Cline
2018-02-22 20:00 ` Mario.Limonciello
2018-02-22 19:50 ` Darren Hart [this message]
2018-02-22 16:18 ` Darren Hart
2018-02-22 16:28 ` Mario.Limonciello
2018-02-22 16:33 ` 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=20180222195000.GE19843@fury \
--to=dvhart@infradead.org \
--cc=Mario.Limonciello@dell.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jeremy@jcline.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=notmart@gmail.com \
--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