On Wednesday, July 20, 2016 09:23:59 AM Lukas Wunner wrote:

On Fri, Jul 08, 2016 at 03:28:12AM +0200, Rafael J. Wysocki wrote:

quoted

On Thu, Jul 7, 2016 at 5:02 PM, Lukas Wunner [off-list ref] wrote:

quoted

(1) Would it be possible to allow dev_pm_domain_set() for already
    bound devices? (It would allow me to simplify this series
    considerably.)

I don't think so, because setting a PM domain generally changes the
set of PM callbacks for the device and it may not be safe to call it
after the driver has been bound.

That sounds more like a locking problem than anything else.

If the system is awake and the device is active, it would seem safe
to change its set of PM callbacks. Am I missing something?

How about checking in dev_pm_domain_set() if pm_runtime_active(dev)

Realistically, you'd need to disable runtime PM too or at least bump up
the usage count.

and calling lock_system_sleep() / unlock_system_sleep() to ensure that?

That might work.

Thanks,
Rafael