From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751781AbdKUAQz (ORCPT ); Mon, 20 Nov 2017 19:16:55 -0500 Received: from mail-ot0-f193.google.com ([74.125.82.193]:36625 "EHLO mail-ot0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751195AbdKUAQw (ORCPT ); Mon, 20 Nov 2017 19:16:52 -0500 X-Google-Smtp-Source: AGs4zMY+Srl1UeIaUI2fWZO3f/5pNXm3/2HcACrzWRqc9GzQSKiK25NQWGy1IGXIrhcsc3UVfx6s2VXKZ7gSKESgXSY= MIME-Version: 1.0 In-Reply-To: References: <3806130.B2KCK0tvef@aspire.rjw.lan> <4184911.zoJM7jZeH4@aspire.rjw.lan> <1917233.X2U0QN21my@aspire.rjw.lan> <13167729.Euq9qh5SXX@aspire.rjw.lan> From: "Rafael J. Wysocki" Date: Tue, 21 Nov 2017 01:16:51 +0100 X-Google-Sender-Auth: D0pd5dS9vM89W_xHo6LiXFpgSx4 Message-ID: Subject: Re: [PATCH v4 1/6] PM / core: Add LEAVE_SUSPENDED driver flag To: Ulf Hansson Cc: "Rafael J. Wysocki" , Linux PM , Bjorn Helgaas , Alan Stern , Greg Kroah-Hartman , LKML , Linux ACPI , Linux PCI , Linux Documentation , Mika Westerberg , Andy Shevchenko , Kevin Hilman Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 20, 2017 at 1:25 PM, Ulf Hansson wrote: > On 18 November 2017 at 15:31, Rafael J. Wysocki wrote: >> From: Rafael J. Wysocki >> >> Define and document a new driver flag, DPM_FLAG_LEAVE_SUSPENDED, to >> instruct the PM core and middle-layer (bus type, PM domain, etc.) >> code that it is desirable to leave the device in runtime suspend >> after system-wide transitions to the working state (for example, >> the device may be slow to resume and it may be better to avoid >> resuming it right away). >> >> Generally, the middle-layer code involved in the handling of the >> device is expected to indicate to the PM core whether or not the >> device may be left in suspend with the help of the device's >> power.may_skip_resume status bit. That has to happen in the "noirq" >> phase of the preceding system suspend (or analogous) transition. >> The middle layer is then responsible for handling the device as >> appropriate in its "noirq" resume callback which is executed >> regardless of whether or not the device may be left suspended, but >> the other resume callbacks (except for ->complete) will be skipped >> automatically by the core if the device really can be left in >> suspend. >> >> The additional power.must_resume status bit introduced for the >> implementation of this mechanisn is used internally by the PM core >> to track the requirement to resume the device (which may depend on >> its children etc). >> >> Signed-off-by: Rafael J. Wysocki >> Acked-by: Greg Kroah-Hartman > > Reviewed-by: Ulf Hansson Thanks!