From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754905AbdFXAGj (ORCPT ); Fri, 23 Jun 2017 20:06:39 -0400 Received: from cloudserver094114.home.net.pl ([79.96.170.134]:64210 "EHLO cloudserver094114.home.net.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754748AbdFXAG1 (ORCPT ); Fri, 23 Jun 2017 20:06:27 -0400 From: "Rafael J. Wysocki" To: Linux PM Cc: LKML , Linux PCI , Linux ACPI , Bjorn Helgaas , Mika Westerberg , Greg Kroah-Hartman Subject: [PATCH v2 0/5] PM: Unify the handling of device wakeup settings Date: Sat, 24 Jun 2017 01:50:55 +0200 Message-ID: <2524735.NRzn8A9HAf@aspire.rjw.lan> User-Agent: KMail/4.14.10 (Linux/4.12.0-rc1+; KDE/4.14.9; x86_64; ; ) In-Reply-To: <12296383.UdE5HVtyng@aspire.rjw.lan> References: <12296383.UdE5HVtyng@aspire.rjw.lan> 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 Monday, June 19, 2017 11:31:58 PM Rafael J. Wysocki wrote: > Hi All, > > The handling of device wakeup settings, especially in the ACPI core and the PCI > bus type, depends on whether it is about system wakeup from sleep states or > remote wakeup in the working state (runtime). However, that distinction is > mostly based on the ACPI concept of "wakeup" and "runtime" GPEs, which is > somewhat artificial, because the underlying hardware mechanism is basically > the same in both cases. > > Moreover, suspend-to-idle is now supported as a sleep state and wakeup from it > is based on exactly the same hardware capabilities as the working-state > (runtime) remote wakeup. > > The following patch series removes that distinction and unifies the handling of > device wakeup settings between system sleep and runtime. It also fixes one > issue related to wakeup signaling through PCI bridges. > > [1/6]: Get rid of the "runtime wakeup" concept from the ACPI core. > [2/6]: Unify device wakeup settings code paths in the ACPI core. > [3-4/6]: Unify device wakeup settings code paths in the PCI bus type code. > [5/6]: Fix wakeup-related issue with bridges in the PCI bus type code. > [6/6]: Get rid of the "runtime wakeup" concept from the driver core. > > The series is based on current linux-next and will be made available for > testing in the linux-pm.git tree in a couple of days. Here's a v2 with tentatively added Reviewed-by tags from Mika. I've dropped patch [5/6] from the previous iteration as it didn't really belong here and the issue it attempted to fix is rather theoretical. I'm going to take a different approach there. Apart from this, the function previously called acpi_pm_device_wakeup() has a different name now: acpi_pm_set_device_wakeup(), to possibly avoid confusion about its purpose. Also the changelog of patch [3/5] has been modified slightly. Thanks, Rafael