{"head":"ad3c36a534bc7b945d7bffdda1c62e13bf93489a","size":2,"push_id":44185399,"shas":[["30b1a7a32ca48fd8758f8ca44d60deebc0aa3d72","75ea6bb7bfc1186f92d26164de5f9268c9a45b59@rowland.harvard.edu","USB: Add wakeup info to debugging messages\n\nThis patch (as1487) improves the usbcore debugging output for port\nsuspend and bus suspend, by stating whether or not remote wakeup is\nenabled.\n\nSigned-off-by: Alan Stern <stern@rowland.harvard.edu>\nAcked-by: Greg Kroah-Hartman <gregkh@suse.de>\nSigned-off-by: Rafael J. Wysocki <rjw@sisk.pl>","Alan Stern"],["ad3c36a534bc7b945d7bffdda1c62e13bf93489a","a11f87183a953ab11f50fbafff689c5a7fa3506c@sisk.pl","PM / Runtime: Don't run callbacks under lock for power.irq_safe set\n\nThe rpm_suspend() and rpm_resume() routines execute subsystem or PM\ndomain callbacks under power.lock if power.irq_safe is set for the\ngiven device.  This is inconsistent with that rpm_idle() does after\ncommit 02b2677 (PM / Runtime: Allow _put_sync() from\ninterrupts-disabled context) and is problematic for subsystems and PM\ndomains wanting to use power.lock for synchronization in their\nruntime PM callbacks.\n\nThis change requires the code checking if the device's runtime PM\nstatus is RPM_SUSPENDING or RPM_RESUMING to be modified too, to take\nthe power.irq_safe set case into account (that code wasn't reachable\nbefore with power.irq_safe set, because it's executed with the\ndevice's power.lock held).\n\nSigned-off-by: Rafael J. Wysocki <rjw@sisk.pl>\nReviewed-by: Ming Lei <tom.leiming@gmail.com>\nReviewed-by: Kevin Hilman <khilman@ti.com>","Rafael J. Wysocki"]],"ref":"refs/heads/pm-runtime"}