Received: by 10.223.185.116 with SMTP id b49csp2113703wrg; Thu, 22 Feb 2018 08:20:20 -0800 (PST) X-Google-Smtp-Source: AH8x227ZWIgWmyichV4hFYGV46I8MAjsY+GijcekHK7mbu3NOMEAsh6eyQdRRPDdF+i06/OHScMa X-Received: by 10.98.134.10 with SMTP id x10mr5297708pfd.78.1519316420775; Thu, 22 Feb 2018 08:20:20 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519316420; cv=none; d=google.com; s=arc-20160816; b=bvVdJDToAJVQ8ij3AePusHCdiENmB5ykCZyF5zKGX/SNM6JlPYF9vnkmllUBjLWddz Cq7VoAmwYbWxXiTgOYwfXvK/fHaa4q91krLjYX48Zuz2TapYOHA2oEwH3YvzZRsPyq9z /jhPsXp2+LsSQwFLCwq9J69u4PrvsCKs8IeL4j808/bUcNX5TEdDeXq1BwnRezanahCX Zno4ylMuMl+N9yI8usboTJVmwz3Yoma9OldeNXW3W1JhTJzwz4Bt4P4UyBlC9cam1sCQ EU9V+Zp7OV9F/61tbNEcUqTqYqUF/FUIOt60EZsVnbv5gZfTGkOuFw5htQVRgjmV0Rw/ 3I1w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature :arc-authentication-results; bh=iRlU13oJu8xKH4dsu+LqGXVX2QgWxo05TwWMkzxyT9M=; b=VVfjIXxCiR19CvvFkUcB1EkApebw4SqH2eZy0vvXKjLbS4pDof0m0Vk4REWsldU31K QqebT/mrToOu41e8SGoculwggQEfSrY4hckZANdRiboZTDe0FXey+fkQ22Xm/3sO0yw3 TCZ+Yy0TGK8jLIsSoFQYhvZjfo/6hosEkcdJ0+pHrCHxx23Cdj4c49yVBi/WRUMI9tZr MA3hhxUULQTKJHI79rtY7bTSHlVsyLV3icxkYTgc5lBq+Bl5tOGTMSFM/W3pcbE6WFXp 4yPVWEEspNYbeNqu+sugTQ5T8Jcwhsq4/fYounac1XuT6fDlMKsq/BUZyxLm59TBzUYF CtBw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=bombadil.20170209 header.b=BCgjcezs; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u188si204905pgc.785.2018.02.22.08.20.06; Thu, 22 Feb 2018 08:20:20 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@infradead.org header.s=bombadil.20170209 header.b=BCgjcezs; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933218AbeBVQTG (ORCPT + 99 others); Thu, 22 Feb 2018 11:19:06 -0500 Received: from bombadil.infradead.org ([198.137.202.133]:53774 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933108AbeBVQTE (ORCPT ); Thu, 22 Feb 2018 11:19:04 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20170209; h=In-Reply-To:Content-Transfer-Encoding :Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date: Sender:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=iRlU13oJu8xKH4dsu+LqGXVX2QgWxo05TwWMkzxyT9M=; b=BCgjcezsyvM5VNCM5VtjejRCfC BkJcVvUXtpZTNXK1fTVdy5z/XBwmQIsKg4U0kW8SNC5WNyoEFSIp6mW0555ON4KVIDCMuxxMPANIe eJj2A0OqKpPKIFyTHcHdfqthNh2YPBOtJfo3+MzJEfSqNF1AVroAItRDj6QO/+Xvsq8fnEvoqeNv/ qAQYxm3PixGU8oG7C909jSB6+8VjS/5fucZaygTAAoydoGcwVM+Kn/VeOD6wtIYdM+y5nZAAtjgg3 LnS2TJVp9kiMprMMlOeq3qiT/LX0tMelmWqWzFRFm8Xbat9+fuGwnQooMitzSlLaxYP9mUUSbrcmT lSy8GjPw==; Received: from dvhart by bombadil.infradead.org with local (Exim 4.89 #1 (Red Hat Linux)) id 1eotaH-0008N8-Bp; Thu, 22 Feb 2018 16:19:01 +0000 Date: Thu, 22 Feb 2018 08:18:59 -0800 From: Darren Hart 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 Message-ID: <20180222161859.GA19843@fury> References: <01000161bbeed4e3-8160ffbc-0998-453d-9afd-14b7dd80dd53-000000@email.amazonses.com> <1628582.nV6hDClBbL@phobos> <01000161bdd7f206-c8d87cce-1b8c-4888-8d6a-5247198b3ead-000000@email.amazonses.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > > Cc: Limonciello, Mario ; Pali Roh?r > > ; Andy Shevchenko ; > > Matthew Garrett ; Darren Hart ; > > Platform Driver ; Linux Kernel Mailing List > > > > Subject: Re: Regression: Dell XPS 13 9360 keyboard no longer works > > > > On Thu, Feb 22, 2018 at 3:08 PM, Jeremy Cline 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 Hart VMware Open Source Technology Center