[lkml]   [2017]   [Nov]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v2 3/6] PM / core: Add SMART_SUSPEND driver flag
On Mon, Nov 6, 2017 at 9:09 AM, Ulf Hansson <> wrote:
> On 28 October 2017 at 00:22, Rafael J. Wysocki <> wrote:
>> From: Rafael J. Wysocki <>
>> 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 <>
>> Acked-by: Greg Kroah-Hartman <>
> If not too late:
> Reviewed-by: Ulf Hansson <>

Not too late, thanks!

I'll be sending the next batch of this shortly. :-)

 \ /
  Last update: 2017-11-06 12:24    [W:7.707 / U:0.000 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site