All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@infradead.org>
To: Mario.Limonciello@dell.com
Cc: notmart@gmail.com, jeremy@jcline.org, 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 08:33:35 -0800	[thread overview]
Message-ID: <20180222163335.GD19843@fury> (raw)
In-Reply-To: <d3789bab5f2c49c7966deabdacab38a8@ausx13mpc120.AMER.DELL.COM>

On Thu, Feb 22, 2018 at 04:28:57PM +0000, Mario.Limonciello@dell.com wrote:
> > -----Original Message-----
> > From: platform-driver-x86-owner@vger.kernel.org [mailto:platform-driver-x86-
> > owner@vger.kernel.org] On Behalf Of Darren Hart
> > Sent: Thursday, February 22, 2018 10:19 AM
> > To: Limonciello, Mario <Mario_Limonciello@Dell.com>
> > Cc: notmart@gmail.com; jeremy@jcline.org; 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
> > 
> > On Thu, Feb 22, 2018 at 03:21:45PM +0000, Mario.Limonciello@dell.com wrote:
> > > > -----Original Message-----
> > > > From: Marco Martin [mailto:notmart@gmail.com]
> > > > Sent: Thursday, February 22, 2018 9:16 AM
> > > > To: Jeremy Cline <jeremy@jcline.org>
> > > > Cc: Limonciello, Mario <Mario_Limonciello@Dell.com>; Pali Rohár
> > > > <pali.rohar@gmail.com>; Andy Shevchenko
> > <andriy.shevchenko@linux.intel.com>;
> > > > Matthew Garrett <mjg59@srcf.ucam.org>; Darren Hart
> > <dvhart@infradead.org>;
> > > > Platform Driver <platform-driver-x86@vger.kernel.org>; Linux Kernel Mailing
> > List
> > > > <linux-kernel@vger.kernel.org>
> > > > Subject: Re: Regression: Dell XPS 13 9360 keyboard no longer works
> > > >
> > > > On Thu, Feb 22, 2018 at 3:08 PM, Jeremy Cline <jeremy@jcline.org> wrote:
> > > > > Input driver version is 1.0.1
> > > > > Input device ID: bus 0x19 vendor 0x0 product 0x0 version 0x0
> > > > > Input device name: "Intel Virtual Button driver"
> > > > > Supported events:
> > > > >   Event type 0 (EV_SYN)
> > > > >   Event type 1 (EV_KEY)
> > > > >     Event code 114 (KEY_VOLUMEDOWN)
> > > > >     Event code 115 (KEY_VOLUMEUP)
> > > > >     Event code 116 (KEY_POWER)
> > > > >     Event code 125 (KEY_LEFTMETA)
> > > > >     Event code 240 (KEY_UNKNOWN)
> > > > >     Event code 561 (?)
> > > > >   Event type 4 (EV_MSC)
> > > > >     Event code 4 (MSC_SCAN)
> > > > >   Event type 5 (EV_SW)
> > > > >     Event code 1 (SW_TABLET_MODE) state 1
> > > > > Properties:
> > > > > Testing ... (interrupt to exit)
> > > >
> > > > Indeed, it's thinking a switch exists and that is on, which is wrong,
> > > > then i guess VGBS() reports a wrong status..
> > > > Mario, do you have any ideas about that?
> > > >
> > > > --
> > > > Marco Martin
> > >
> > > I guess that means we got this wrong and the patch should be reverted
> > > until we figure this out.
> > >
> > > Jeremy,
> > >
> > > Can you please confirm what BIOS version you are on?
> > > Also Is this a 9360 with 7th or 8th gen Intel CPU?
> > >
> > > I'll see if I can find out anything more relative to this.
> > 
> > Watching closely.
> > 
> > Mario, do you want me to revert immediately, or wait until you've had a couple
> > rounds of Q&A here?
> > 
> > --
> 
> Darren,
> 
> Let's hold off until we've discussed a little more.  Jeremy is responsive and we might
> get to the bottom quickly.
> 
> Btw you have a 9360 on hand still right?  Can you see if you can reproduce this problem too?
> 

I'm planning on it, yup.

-- 
Darren Hart
VMware Open Source Technology Center

      reply	other threads:[~2018-02-22 16:33 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
2018-02-22 16:18         ` Darren Hart
2018-02-22 16:28           ` Mario.Limonciello
2018-02-22 16:33             ` Darren Hart [this message]

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=20180222163335.GD19843@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 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.