Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp3322161imm; Mon, 6 Aug 2018 02:40:10 -0700 (PDT) X-Google-Smtp-Source: AAOMgpccwd0uzTmuK6N4Wg5UMaEPVrFbMidjBjjufUbVlE/LcSa/Q3S5T1k2hz6OhFXeU6/XNUuB X-Received: by 2002:a63:e0b:: with SMTP id d11-v6mr13892255pgl.134.1533548410613; Mon, 06 Aug 2018 02:40:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1533548410; cv=none; d=google.com; s=arc-20160816; b=Y6MaLf2wgEzeKxDfbVqimzitTQ5PFUNhN4U1ouGM4xUQZ1v/DtiuxMrZD7VScQ1PAQ j7FiBP72AvU2hfwEBR+hOFflAQALj8n5Rp8oWxmyuEvZWHhpYk6gbi/n4kLUayyEf+VF eR4O+3USbKJpGLVX1DVbMxIaXDBnF3X1wT5Tocvr4jEhhuP8q3nXWr2bsMWUo3mGiaW9 NiTQtMk3Hl8QnPxkn0VVScS3hCDU7aJegNBaEkbaJ1mYTrDk33zFgEHDg4kyQOoxLhJ0 RO1aOJhh45iotIz4g7OrX8hKT0KkzrwkIbqIqiRBRgFY6gF8JC/XaxtN8BZbRfrtS8ct oPKQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :arc-authentication-results; bh=8pgjeXcQSj68rndSfwhtX0x0QsEnQSZxxScVqRPKrDI=; b=Wu9n8NPu8AyWIrqTa8l1CqIFfO52iEi1B7YmKg7Wh1aPq+Tkzs6drzo7HdxzpSZS8q /Xyubc5y+x2eX5EWevheZsxslAuulT+R/8o34SHkq39O7ljJvogE/aNCN5RzasVUyyiF BdbDuOt2J022eIr8WGBOLkpDnGVY2A8KTYXXBPk7nKxTOL2efWhJMZMlGeQBaw4BYlRc ooymiQ42xz7loXQyNxn5ip21xEon43DE2xB5kbvRi8CjTM49azul8LX6s5VwUeOz5Vjj +UFT65I0WyaeZwhZ0JbFnLEM+oG6TMeq6GBWBLgAg/CYhcG0XREf1XJQToTdOal25zCc OB/Q== ARC-Authentication-Results: i=1; mx.google.com; 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 e67-v6si9279037plb.272.2018.08.06.02.39.55; Mon, 06 Aug 2018 02:40:10 -0700 (PDT) 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; 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 S1727009AbeHFLrU (ORCPT + 99 others); Mon, 6 Aug 2018 07:47:20 -0400 Received: from cloudserver094114.home.pl ([79.96.170.134]:48263 "EHLO cloudserver094114.home.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726462AbeHFLrU (ORCPT ); Mon, 6 Aug 2018 07:47:20 -0400 Received: from 79.184.254.16.ipv4.supernova.orange.pl (79.184.254.16) (HELO aspire.rjw.lan) by serwer1319399.home.pl (79.96.170.134) with SMTP (IdeaSmtpServer 0.83) id fbc8bfbe2522fb64; Mon, 6 Aug 2018 11:39:04 +0200 From: "Rafael J. Wysocki" To: Chris Chiu Cc: Dmitry Torokhov , linux-input , linux-pm@vger.kernel.org, Linux Kernel , Linux Upstreaming Team Subject: Re: Built in PS2 keyboard in new ASUS/acer laptops can not wake up system after s2idle Date: Mon, 06 Aug 2018 11:37:05 +0200 Message-ID: <73029405.6ZXyByzer1@aspire.rjw.lan> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Friday, August 3, 2018 10:04:09 AM CEST Chris Chiu wrote: > Hi guys, > We have some new laptops with Intel new Intel WiskyLake CPU come > in and they all have the same problem. They all have the so-called > "Modern Standby" feature which is s2idle in Linux. > > The problem is the built-in keyboard no longer wake up the system > after it goes to s2idle. Only the power button can wake up. It's > different from the other laptops with old Intel CPUs (CoffeeLake, > KaybeLake...etc). We found the difference is that the EC (embedded > controller) no longer signals SCI event when in s2idle. > > Confirmed with ASUS EC engineer, he also admits that the EC code > for signaling SCI event in modern standby has been removed on > WiskyLake models. Because the built-in PS2 keyboard can still wake up > the system on WisksyLake+Windows10 RS4 combination without EC > intervention. > > Based on this information, we suspect that maybe the built-in > keyboard wakeup on Windows 10 RS4 in enabled by default (although we > don't know how to prove that). It's easy to simply do > 'device_set_wakeup_enable' and 'enable_irq_wake' for the i8042 > keyboard port to wake up the system without EC, but it's nasty. > > Any suggestion about how to achieve the keyboard wake up function > on these new laptops in a generic way? Thanks What about echoing "enabled" to the keyboard's power/wakeup file in sysfs?