The generic problem this series intends to solve, is that for some PM domains, especially genpd, the current information in the dev->power.wakeup_path, is not sufficient for a PM domain to fully understand how to treat devices in the wakeup path during system suspend. Particularly this applies to resources being consumed by the driver that has configured system wakeup settings for its device. Currently the PM domain lacks information about these consumed resources, which means it may decide to power of their corresponding device and its attached PM domain, while they actually would need to stay powered to allow system wakeup signals to be delivered. Geert Uytterhoeven, has been working on these kind of problems for some Renesas SoCs and there have been lots of discussions around this. After some consideration I have dropped my first attempt [1] on how to address these problems, so here's hopefully a better one. So far I haven't included any patches for dealing with the "OUT_BAND_WAKEUP" thingy, but I suggest we do that in a second separate step, since it's not immediately need to fix the problems for the Renesas SoCs. Geert's Renesas series [2], needs to be re-based on top of this series to make it convert to use the new DPM_FLAG_WAKEUP_PATH flag, which is introduced in this series. That leads to a tree-wise-dependency, so perhaps Rafael can host an immutable branch the Renesas tree can pull in. Let's see. [1] https://www.spinics.net/lists/linux-renesas-soc/msg20122.html [2] https://www.spinics.net/lists/linux-renesas-soc/msg19947.html Ulf Hansson (3): PM / core: Assign the wakeup_path status flag in __device_prepare() PM / core: Add WAKEUP_PATH driver flag PM / Domains: Take WAKEUP_PATH driver flag into account in genpd drivers/base/power/domain.c | 8 ++++++-- drivers/base/power/main.c | 5 ++++- include/linux/pm.h | 7 +++++++ 3 files changed, 17 insertions(+), 3 deletions(-) -- 2.7.4
