[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD6_Bos5Qrvz=Mr_rYCZXZ1s=5+8rawfZXxzXSvyc-tLBO07fg@mail.gmail.com>
Date: Thu, 22 Feb 2018 16:15:37 +0100
From: Marco Martin <notmart@...il.com>
To: Jeremy Cline <jeremy@...ine.org>
Cc: Mario Limonciello <mario.limonciello@...l.com>,
Pali Rohár <pali.rohar@...il.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Matthew Garrett <mjg59@...f.ucam.org>,
Darren Hart <dvhart@...radead.org>,
Platform Driver <platform-driver-x86@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.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@...ine.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
Powered by blists - more mailing lists