Re: [PATCH] PM / runtime: print error when activating a child to unactive parent

On Monday, June 20, 2016 11:14:26 AM Linus Walleij wrote:

The code currently silently bails out with -EBUSY if you try to
activate a child to an inactive parent.

This typically happens when you have a runtime suspended parent
and runtime resume your child, but forgot to set .ignore_children
on the parent to true with pm_suspend_ignore_children(dev).

Silently ignoring this error is not good as it gives rise to
other strange behaviour like double-resume of devices after
silently bailing out of the .runtime_resume() callback.

Signed-off-by: Linus Walleij <redacted>

Applied, thanks!