summaryrefslogtreecommitdiffstats
path: root/drivers/pwm
diff options
context:
space:
mode:
authorChristian Lamparter <chunkeey@googlemail.com>2013-02-21 16:42:06 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2013-02-21 17:22:16 -0800
commit42b5dd51930c04dc6fb59c7c7a79354ff91bc9a4 (patch)
treedcda22bae7d2b4550570ce87af1abfdb81069954 /drivers/pwm
parentddfe9b359f8a256e711430c29d7c553b1569faed (diff)
downloadblackbird-op-linux-42b5dd51930c04dc6fb59c7c7a79354ff91bc9a4.tar.gz
blackbird-op-linux-42b5dd51930c04dc6fb59c7c7a79354ff91bc9a4.zip
pcmcia: move unbind/rebind into dev_pm_ops.complete
Move the device rebind procedures for cardbus devices from the pm.resume into the pm.complete callback. The reason for moving the code is: "[...] The PM code needs to send suspend and resume messages to every device in the right order, and it can't do that if new devices are being added at the same time. [...]" However the situation really isn't quite that rigid. In particular, adding new children during a resume callback shouldn't cause much of problem because the children don't need to be resumed anyway (since they were never suspended). On the other hand, if you do it you will get a dev_warn() from the PM core, something like 'parent should not be sleeping'. Still, it is considered bad form and should be avoided if possible." (Alan Stern's full comment about the topic can be found here: <https://lkml.org/lkml/2012/7/10/254>) Signed-off-by: Christian Lamparter <chunkeey@googlemail.com> Cc: Dominik Brodowski <linux@dominikbrodowski.net> Cc: Alan Stern <stern@rowland.harvard.edu> Cc: Greg KH <greg@kroah.com> Acked-by: "Rafael J. Wysocki" <rjw@sisk.pl> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/pwm')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud