Hi Seungwon, 2013/3/14 Seungwon Jeon <[email protected]>: > 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 <[email protected]> > Signed-off-by: Seungwon Jeon <[email protected]>
Thank you for the quick response and fix! This fixes the problem. So please include my Tested-by: Johan Rudholm <[email protected]> Kind regards, Johan -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
