From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3DDEBC43331 for ; Fri, 27 Mar 2020 13:32:14 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 057BE20838 for ; Fri, 27 Mar 2020 13:32:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1585315934; bh=HNpnIDl0zqSNywSLkkSXxGutEzA7mG44rwD9YIFLqlg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=Tu00r5rIKOM/va1Csug4E2me179+E6oMqnEEFrOpN6CiEki9yIExDqoWaMHBQuVsl TDeXg99e8OC4dUy2X848s/wN/6BCBZzA6CTRl+18h1EQQWgEwTTLEvMKlcf3PURWlo 6B3yLa734YGJCJ9Gv5YHHPqA9cCIWGTwHLREdM+o= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727347AbgC0NcN (ORCPT ); Fri, 27 Mar 2020 09:32:13 -0400 Received: from mail.kernel.org ([198.145.29.99]:46566 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727247AbgC0NcN (ORCPT ); Fri, 27 Mar 2020 09:32:13 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 7F63720838; Fri, 27 Mar 2020 13:32:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1585315933; bh=HNpnIDl0zqSNywSLkkSXxGutEzA7mG44rwD9YIFLqlg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=YL5F8s3x1x7iIln8cyC45KTkV5cKWdpSc1OY/O2wu6/S//wsTuY839eG9pUMWPE70 AtERwdhwXljwc6JjqoFnsPljd6ZDfxcQ/cZks+uMAK5MSRmjj7voQDsfFtJ/tyxY5z Wj/5TY/+SkIUWih+RJrzcO1ApDsfznp/92S8BBrc= Date: Fri, 27 Mar 2020 14:32:10 +0100 From: Greg Kroah-Hartman To: "Rafael J. Wysocki" Cc: Stable Subject: Re: Commit 024aa8732acb for 5.4.y Message-ID: <20200327133210.GA2267097@kroah.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Fri, Mar 27, 2020 at 02:11:46PM +0100, Rafael J. Wysocki wrote: > Hi Greg at al, > > Please the following commit: > > commit 024aa8732acb7d2503eae43c3fe3504d0a8646d0 > Author: Rafael J. Wysocki > Date: Thu Nov 28 23:50:40 2019 +0100 > > ACPI: PM: s2idle: Rework ACPI events synchronization > > Note that the EC GPE processing need not be synchronized in > acpi_s2idle_wake() after invoking acpi_ec_dispatch_gpe(), because > that function checks the GPE status and dispatches its handler if > need be and the SCI action handler is not going to run anyway at > that point. > > Moreover, it is better to drain all of the pending ACPI events > before restoring the working-state configuration of GPEs in > acpi_s2idle_restore(), because those events are likely to be related > to system wakeup, in which case they will not be relevant going > forward. > > Rework the code to take these observations into account. > > Tested-by: Kenneth R. Crudup > Signed-off-by: Rafael J. Wysocki > > > into 5.4.y as it is needed to fix an ACPI wakeup events > synchronization issue in suspend-to-idle. > > Note that this commit was present in 5.5.0, so 5.4.y is the only > -stable series needing this fix. Now queued up, thanks! greg k-h