Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751584AbdFHHYr (ORCPT ); Thu, 8 Jun 2017 03:24:47 -0400 Received: from mx1.redhat.com ([209.132.183.28]:33352 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750822AbdFHHYm (ORCPT ); Thu, 8 Jun 2017 03:24:42 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com BAB1DC04B936 Authentication-Results: ext-mx07.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx07.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=hdegoede@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com BAB1DC04B936 Subject: Re: [PATCH 0/6] ACPI / PM: Suspend-to-idle rework to deal with spurious ACPI wakeups To: "Rafael J. Wysocki" , Linux ACPI Cc: Linux PCI , Linux PM , Bjorn Helgaas , LKML , Mika Westerberg , Srinivas Pandruvada , Linux USB , Mathias Nyman , Felipe Balbi , Mario Limonciello , Andy Shevchenko , Dominik Brodowski References: <8918199.uo13RZ8hZk@aspire.rjw.lan> From: Hans de Goede Message-ID: <7579a28c-6237-e16a-6eda-9b41cc657ddf@redhat.com> Date: Thu, 8 Jun 2017 09:24:37 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: <8918199.uo13RZ8hZk@aspire.rjw.lan> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Thu, 08 Jun 2017 07:24:42 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1503 Lines: 39 Hi, On 08-06-17 02:00, Rafael J. Wysocki wrote: > Hi All, > > This series is a replacement for commit eed4d47efe95 (ACPI / sleep: Ignore > spurious SCI wakeups from suspend-to-idle) which is still there in 4.12-rc4 but > will be reverted shortly, because it triggered issues on quite a few systems. > > The last patch in the series is a counterpart of the above commit with a few > modifications, mostly to avoid affecting suspend-to-RAM and to reorder messages > printed to kernel logs to make them somewhat less confusing. > > The previous patches are pre-requisite changes plus some cleanups. The major > ones are [1-2/6] and [4/6] that are really needed for things to work as expected > after [6/6]. > > In addition to that, this patch from Hans: https://patchwork.kernel.org/patch/9762815/ > is needed for USB wakeup on Bay Trail and Cherry Trail systems to work in general. Small correction, that patch currently only influences Cherry Trail devices, it has: static const struct x86_cpu_id int0002_cpu_ids[] = { /* * Limit ourselves to Cherry Trail for now, until testing shows we * need to handle the INT0002 device on Baytrail too. * ICPU(INTEL_FAM6_ATOM_SILVERMONT1), * Valleyview, Bay Trail * */ ICPU(INTEL_FAM6_ATOM_AIRMONT), /* Braswell, Cherry Trail */ {} }; If anyone sees any issues where the SCI (typically irq 9) gets a nobody cared message on Bay Trail try the linked patch with the Bay Trail line above uncommented. Regards, Hans