On Wed, Nov 8, 2017 at 4:15 PM, Ulf Hansson <[email protected]> wrote: > For some bus types and PM domains, it's not sufficient to only check the > return value from device_may_wakeup(), to fully understand how to treat the > device during system suspend. > > In particular, sometimes the device may need to stay in full power state, > to have wakeup signals enabled for it. Therefore, define and document a > WAKEUP_POWERED flag, to enable drivers to instruct bus types and PM domains > exactly about that. > > During __device_suspend() in the PM core, let's make sure to also propagate > the setting of the flag to the parent device, when wakeup signals are > enabled and unless the parent has the "ignore_children" flag set. This > makes it also consistent with how the existing "wakeup_path" flag is being > assigned. > > Signed-off-by: Ulf Hansson <[email protected]>
Reviewed-by: Geert Uytterhoeven <[email protected]> Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected] In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
