diff options
| author | Seungwon Jeon <tgih.jun@samsung.com> | 2013-03-14 15:17:13 +0900 |
|---|---|---|
| committer | Chris Ball <cjb@laptop.org> | 2013-03-22 13:29:36 -0400 |
| commit | ef3a69c7a40d5350adeaed7f0f4b4dcf6362dbbd (patch) | |
| tree | cb77517ba212670cb6234624848c4b3afc69eda6 /drivers/block | |
| parent | 3500ed90b26a9935b943b5e2e4cd3226600d6b58 (diff) | |
| download | linux-ef3a69c7a40d5350adeaed7f0f4b4dcf6362dbbd.tar.bz2 | |
mmc: block: fix the host's claim-release in special request
For normal request mmc_blk_issue_rq is called twice with asynchronous
transfer(cur and prev). Host's claim and release can be done in each
mmc_blk_issue_rq. However, Special request is currently excluded in
asynchronous transfer. After special request is finished, if there is
no new request, mmc_release_host won't be called in mmc_blk_issue_rq.
The problem is founded during mmc_suspend.
[<c0541124>] (__schedule+0x0/0x78c) from [<c05419e8>] (schedule+0x38/0x78)
[<c05419b0>] (schedule+0x0/0x78) from [<c03a843c>] (__mmc_claim_host+0xac/0x1b4)
[<c03a8390>] (__mmc_claim_host+0x0/0x1b4) from [<c03ac98c>] (mmc_suspend+0x28/0x9c)
[<c03ac964>] (mmc_suspend+0x0/0x9c) from [<c03aad24>] (mmc_suspend_host+0xb4/0x194)
...
Reported-by: Johan Rudholm <jrudholm@gmail.com>
Signed-off-by: Seungwon Jeon <tgih.jun@samsung.com>
Tested-by: Johan Rudholm <johan.rudholm@stericsson.com>
Signed-off-by: Chris Ball <cjb@laptop.org>
Diffstat (limited to 'drivers/block')
0 files changed, 0 insertions, 0 deletions