On Mon, Nov 6, 2017 at 9:09 AM, Ulf Hansson <ulf.hansson@xxxxxxxxxx> wrote: > On 28 October 2017 at 00:22, Rafael J. Wysocki <rjw@xxxxxxxxxxxxx> wrote: >> From: Rafael J. Wysocki <rafael.j.wysocki@xxxxxxxxx> >> >> Define and document a SMART_SUSPEND flag to instruct bus types and PM >> domains that the system suspend callbacks provided by the driver can >> cope with runtime-suspended devices, so from the driver's perspective >> it should be safe to leave devices in runtime suspend during system >> suspend. >> >> Setting that flag may also cause middle-layer code (bus types, >> PM domains etc.) to skip invocations of the ->suspend_late and >> ->suspend_noirq callbacks provided by the driver if the device >> is in runtime suspend at the beginning of the "late" phase of >> the system-wide suspend transition, in which case the driver's >> system-wide resume callbacks may be invoked back-to-back with >> its ->runtime_suspend callback, so the driver has to be able to >> cope with that too. >> >> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@xxxxxxxxx> >> Acked-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> > > If not too late: > > Reviewed-by: Ulf Hansson <ulf.hansson@xxxxxxxxxx> Not too late, thanks! I'll be sending the next batch of this shortly. :-) -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
