diff options
author | Ohad Ben-Cohen <ohad@wizery.com> | 2011-06-09 23:40:27 (GMT) |
---|---|---|
committer | Chris Ball <cjb@laptop.org> | 2011-06-25 22:49:55 (GMT) |
commit | 297c7f2f158f7dfa9ab5813260ff954f9c2f83d2 (patch) | |
tree | 463c7dbb914337e1c47e1840ea86c29457dbf3bb /drivers/mmc/host | |
parent | be98ca652faa6468916a9b7608befff215a8ca70 (diff) | |
download | linux-fsl-qoriq-297c7f2f158f7dfa9ab5813260ff954f9c2f83d2.tar.xz |
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>
Diffstat (limited to 'drivers/mmc/host')
0 files changed, 0 insertions, 0 deletions