RE: BUG/PATCH? mmcblk devices don't suspend properly.

["Hebbar, Gururaja" <gururaja.hebbar@xxxxxx>]

I contacted the original author of the patch (http://comments.gmane.org/gmane.linux.kernel.mmc/9168)
And he has posted the 2nd version of the commit. 

[PATCH V2]mmc: remove MMC bus legacy suspend/resume method

MMC bus is using legacy suspend/resume method, which is not compatible if
runtime pm callbacks are used. In this scenario, MMC bus suspend/resume
callbacks cannot be called when system entering S3. So change to use the new
defined dev_pm_ops for system sleeping mode

Signed-off-by: Chuanxiao Dong <chuanxiao.dong@xxxxxxxxx>
---
Changes in v2:
	use SET_SYSTEM_SLEEP_PM_OPS to define sleep callbacks as Rafael
	suggested


May be you can test your setup with this patch.


On Fri, Mar 30, 2012 at 10:55:45, Sujit Reddy Thumma wrote:
> On 3/30/2012 8:17 AM, NeilBrown wrote:
> >
> > I've been experimenting with removing the call to sys_sync() in
> > enter_state().  For me (with verbose debugging and syslog running)
> > this causes a noticeable delay when entering suspend.
> >
[...snip...]
> >
> > Since removing the sys_sync() call I've notices a number of problems with
> > suspend/resume, the most obvious being that resume blocks in mmc_claim_host:
> >
> > [  263.585754] susman          D c046455c  5604  1086   1084 0x00000000
> > [  263.592498] [<c046455c>] (__schedule+0x584/0x614) from [<c0302630>] (__mmc_claim_host+0xb8/0x154)
> > [  263.601806] [<c0302630>] (__mmc_claim_host+0xb8/0x154) from [<c0308640>] (mmc_sd_resume+0x34/0x5c)
> > [  263.611206] [<c0308640>] (mmc_sd_resume+0x34/0x5c) from [<c0301ce4>] (mmc_resume_host+0xc8/0x15c)

[...snip...]

> This was pointed out earlier and a patch is posted but looks like it 
> never went into mmc tree -- 
> http://comments.gmane.org/gmane.linux.kernel.mmc/9168
> 
> >
> >
> > Thanks for any help you can provide,
> >
> > NeilBrown
> >
> 
> --

Regards, 
Gururaja
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html