mmc: sdio: fix runtime PM path during driver removal
authorOhad Ben-Cohen <ohad@wizery.com>
Thu, 9 Jun 2011 23:40:27 +0000 (23:40 +0000)
committerChris Ball <cjb@laptop.org>
Sat, 25 Jun 2011 22:49:55 +0000 (18:49 -0400)
commit297c7f2f158f7dfa9ab5813260ff954f9c2f83d2
tree463c7dbb914337e1c47e1840ea86c29457dbf3bb
parentbe98ca652faa6468916a9b7608befff215a8ca70
mmc: sdio: fix runtime PM path during driver removal

After commit e1866b3 "PM / Runtime: Rework runtime PM handling
during driver removal" was introduced, the driver core stopped
incrementing the runtime PM usage counter of the device during
the invocation of the ->remove() callback.

This indirectly broke SDIO's runtime PM path during driver removal,
because no one calls _put_sync() anymore after ->remove() completes.

This means that the power of runtime-PM-managed SDIO cards is kept
high after their driver is removed (even if it was powered down
beforehand).

Fix that by directly calling _put_sync() when the last usage
counter is downref'ed by the SDIO bus.

Reported-and-tested-by: Daniel Drake <dsd@laptop.org>
Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com>
Signed-off-by: Chris Ball <cjb@laptop.org>
drivers/mmc/core/sdio_bus.c