From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754278AbdHDXif (ORCPT ); Fri, 4 Aug 2017 19:38:35 -0400 Received: from cloudserver094114.home.net.pl ([79.96.170.134]:52088 "EHLO cloudserver094114.home.net.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752391AbdHDXid (ORCPT ); Fri, 4 Aug 2017 19:38:33 -0400 From: "Rafael J. Wysocki" To: Darren Hart Cc: Mario Limonciello , AceLan Kao , linux-pm@vger.kernel.org, LKML , platform-driver-x86@vger.kernel.org, Len Brown , Srinivas Pandruvada , Andy Shevchenko Subject: Re: [PATCH] intel-vbtn: match power button on press rather than release Date: Sat, 05 Aug 2017 01:30:20 +0200 Message-ID: <11471111.T3jHVeqpMT@aspire.rjw.lan> In-Reply-To: <20170804172953.GC21169@fury> References: <1501866006-24811-1-git-send-email-mario.limonciello@dell.com> <20170804172953.GC21169@fury> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Friday, August 4, 2017 7:29:53 PM CEST Darren Hart wrote: > On Fri, Aug 04, 2017 at 12:00:06PM -0500, Mario Limonciello wrote: > > This fixes a problem where the system gets stuck in a loop > > unable to wakeup via power button in s2idle. > > > > The problem happens because: > > - press power button: > > - system emits 0xc0 (power press), event ignored > > - system emits 0xc1 (power release), event processed, > > emited as KEY_POWER > > - set wakeup_mode to true > > - system goes to s2idle > > - press power button > > - system emits 0xc0 (power press), wakeup_mode is true, > > system wakes > > - system emits 0xc1 (power release), event processed, > > emited as KEY_POWER > > - system goes to s2idle again > > > > To avoid this situation, process the presses (which matches what > > intel-hid does too). > > > > Verified on an Dell XPS 9365 > > > > Signed-off-by: Mario Limonciello > > This looks good to me - responding to the release is non-intuitive IMHO > anyway. I'd like to see agreement from AceLan, but this should go into > the 4.13 rc cycle (at rc3 currently). Yes, it should, and I'm not sure if the original author's opinion matters here. The patch makes sense to everyone involved and fixes an annoying issue, so I don't see any real arguments against applying it. Please feel free to add my ACK to it if that helps. In any case, it has to go in before https://patchwork.kernel.org/patch/9873163/ does, is if it doesn't go into 4.13-rc after all, please let me know. Thanks, Rafael